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 : Nokia (NOK) -- Ignore unavailable to you. Want to Upgrade?

To: samim anbarcioglu who wrote (5341)	6/8/2000 6:17:00 PM
From: w molloy	Respond to of 34857

>> you know all about Q's chipset API? You worked with it, understood all the entry points, facilities, transactions, and realized it is too much for you? Uh yes, yes, yes, yes, yes and no. Resorting to an ad homonim attack is a rather weak response, isn't it? The QCOM API was (is) an afterthought, not that the AMPS based protocol stack was that hard to understand, but the channel management, call handling etc was not dealt with in a sufficiently abstract way. In a nutshell, the MMI was left with a lot of work to do. My point is that by signing up 9 OEM's, QCOM had better have an excellent software delivery and support model. This is one area they have been consistently bad in. To be fair, other companies have run into similar issues (assuming their OEM customers are as smart as they are). Some, like DSPC continue to have a bad rep. Others, like LSI have made huge improvements. w.