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 : Wind River going up, up, up! -- Ignore unavailable to you. Want to Upgrade?

To: James Connolly who wrote (6894)	11/28/1999 10:22:00 AM
From: voop	Read Replies (1) \| Respond to of 10309

Can you speculate about the speculation? Disclaimers accepted, of course. Voop

To: James Connolly who wrote (6894)	11/28/1999 6:52:00 PM
From: lkj	Read Replies (2) \| Respond to of 10309

James, I am not too sure what you mean by speculation on QCOM and WIND. Are you talking about a merger or working together? I don't see Q buying WIND. It would suck if it does happen. WIND is riding the embedded wave, the CDMA wave is tiny in comparison. I would not be shocked to see Q is using VxWorks, not on their MSM3000, but on their future chip. I don't think the MSM3100 has 2 processing cores. But Q is working on a new chip with 2 cores, one running PDA functions such as CE or Palm OS, the other does hardcore controlling and communication protocol. I think VxWorks should be well suited for this. (Just a guess.) Khan (from the book store in UCLA) P.S. UCLA has a quite nice campus. I should have visited when I was in high school many years ago!

To: James Connolly who wrote (6894)	11/30/1999 3:16:00 AM
From: lkj	Read Replies (1) \| Respond to of 10309

James, I was thinking when I was going to sleep last night that Q can use VxWorks for its MSM3000. Here is my reasoning. I have been using the Qualcomm Thin Phone for about 3 months. I have to say that the phone sucks in many way. (Sorry to the Qualcomm faithful.) For example, some times the phone responses to key press with a 1/2 second delay. I assume that Qualcomm is doing polling instead of using an interrupt. Wouldn't an OS that can scan the key pad every 50 mili-seconds be better? I think it would. Q's problem with the Thin Phone software goes much further than just slow key response. A major bug is that the code may have gone to a new state, but the LCD update is 1 second behind. Like the key pad problem, this happens only once a while. If implemented correctly, VxWorks can help Q greatly at solving these timing problems. (My personal belief is that even without an OS, such problems should NEVER happen.) If Q wants to be a successful ASIC supplier, its firmware needs to become 1) robust, and 2) customizable. Getting VxWorks on there will not solve the problem, but would be a step to the right direction. There are also other reasons, such as implementing BlueTooth, that may force Q to redo the MSM3000 firmware architecture. If Q doesn't clean up its firmware, it might find itself loosing Japanese customers such as Kyocera in the not so distant future, despite its lead in ASICs. Going off topic, it might be a good business idea to rewrite the MSM3000 firmware, and resell it to OEMs. If the business does take off, Q will buy it. Khan