Re: [Madwifi-devel] porting madwifi linux driver to an embedded OS platform
Status: Beta
Brought to you by:
otaku
From: John C. <jc...@me...> - 2006-10-27 22:52:01
|
hong zhang schrieb: > Atheros provides both VxWorks and Linux drivers. But it said that > Green Hill OS will perform better. > Is anyone experienceing it? I personally am prejudiced against vxWorks. There are reasons why I have tended to use one of Linux or NetBSD for wireless solutions. 1) On these platforms there are many people working, or using, and so when problems arrise, they tend to at least be documented far quicker than if these problems arrise in the 'closed OS' systems. This does not mean there are 'fast solutions', just much better communication of problems amongst the users. 2) For many applications that I have, having a fully capable kernel that allows for the large set of applications to be run that is available to the Linux/BSD community, this far outweighs any 'benefit' by having a 'realtime' operating system where even the most 'simple' form of HTTP server is a hassle to get installed, working, and extended in functionality. 3) Based on long standing contact with Wind River in the 90's as a board support developer, the 'free', 'open source' community far out distances the idiot support that one got, at a price, from Wind River. There were many occasions in my dealing with WR where I 'found a bug', only to find that many others had also 'found' the same bug, and it was not fixed in various releases, and BSP developers were almost never notified of such conditions unless they 'called in a support' item. Further, as a BSP creator, often I would find 'problems' at a level that the ordinary 'application' user of vxWorks never came to, and the WR 'support group', never really understood. Anyway... don't get me started on WR and vxWorks... John Clark |