On 2/4/07, Jon Smirl <jonsmirl@xxxxxxxxx> wrote:
On 2/4/07, Michael Buesch <mb@xxxxxxxxx> wrote: > I don't really see your point. > We can't change hardware. We have to implement the software around existing > hardware. And that's currently softmac _and_ fullmac devices. > So we have to create hooks and so on in our software to support > the fullmac devices. What happened at Microsoft in the Ethernet case is that MS stopped supporting FullMAC and told the vendors to come up with SoftMAC type drivers. For some cards the vendors wrote the software drivers and for others MS did. Not all of the vendors agreed to this and most of those companies are no longer around. The point is that Linux could simply design out the FullMAC hardware that didn't also make a basic SoftMAC interface available. The primary wireless implementation for Linux would be a fully software based implementation that all hardware would be required to minimally work with. The main kernel wireless developers would then focus their attention on the software stack implementation instead of dealing with all of the various firmware messes and uncooperative vendors. This model is pretty close to happening with the Dscape stack. Once Dscape goes in, notice could be given that the other implementations will be removed in a year. Of course Linux doesn't have the same kind of power over the vendors like MS does. But it doesn't mean that this model wouldn't work for Linux. The concept of a single top to bottom software based reference implementation with hooks for hardware acceleration is a sound design.
Current wireless cognitive radio research is ambitiously trying to to come up with a framework where certain functions can exist in either hardware and/or software; but it is very important to note that, mainly due to timing differences, it is by no means trivial to come up with proper encapsulation of hardware implemented blocks so that they are easily blended in a full software framework. Additionally, since FullMAC solutions may currently provide the best solutions for certain situations (power requirements for embedded devices being the most common I've heard) and since we do want to take part in projects which make use of these solutions (OLPC being one) we cannot, and I think should not, try to mandate vendors to adopt SoftMAC solutions only just because it makes our lives easier. MS may have done what they did to help with their development efforts but it doesn't mean it was necessarily good for technology. We want to work with vendors to support their devices regardless of how stupid their design is -- ultimately our job is to support hardware for our users and not take on political quests to dictate the path of technology. Luis - To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
