Silicon Investor (SI) -- The First Internet Community

STOCKTALK

We've detected that you're using an ad content blocking browser plug-in or feature. Ads provide a critical source of revenue to the continued operation of Silicon Investor. We ask that you disable ad blocking while on Silicon Investor in the best interests of our community. If you are not using an ad blocker but are still receiving this message, make sure your browser's tracking protection is set to the 'standard' level.

Technology Stocks : Qualcomm Moderated Thread - please read rules before posting -- Ignore unavailable to you. Want to Upgrade?

To: slacker711 who wrote (11018)	5/28/2001 9:35:31 PM
From: Eric L	Read Replies (2) \| Respond to of 196720

Slacker, << Samsung Electronics did not employ this chip ... Other than that....any delay in the MSM5105 would be terrible news for Qualcomm. Ugh.... >> Double Ugh. I am wondering. Could Samsung have there own 1x chip? In the CDG Digevent on Korea Samsung plugged their own chip several times. No indication of whether it was IS-95A/B or 1xRTT, but I wondered. If handset deliveries are delayed because of the MSM5105 maybe a Samsung 1xRTT chip could keep momentum going for 1xRTT deployment. On the other hand, could a Samsung chip be source of problems as reported in the eTimes article? Not good! - Eric -

To: slacker711 who wrote (11018)	5/28/2001 9:46:58 PM
From: mightylakers	Read Replies (2) \| Respond to of 196720

The article I posted, as usual as those out of Korea, is very confusing. For instance it claimed that MSM5105 doesn't support convolution codes, which I believe is totally a BS. It also claimed that is essential for the high speed data rate, which I believe is not the case, in CDMA2000, turbo coding is more useful in high speed data. Well maybe the author just tried to restate but he certainly created a lot of confusions here. We all know that current MSM5105 is for 144kbps, where MSM5100 is for 307 kbps high end users. So if that is the problem then I don't understand why it is a problem?