Dan Williams wrote: >>> we're not being open enough to functionality that might be in hardware. >>> Holding a 100% software line with mac80211 is just IMHO wrong and >>> short-sighted. The stack needs to be flexible WRT to the hardware >> Yeah but this isn't "in hardware" -- it's in firmware: software that > > I know that. But to the driver, it might as well be in hardware. The > driver and stack doesn't care where the functionality lives (silicon or > firmware) as long as the firmware does what's needed. That's right, it "might as well be hardware" because there are no sources for the firmware, despite it is as much software as anything else. But architecturally, when we have the freedom to make a choice where to place our bets, who CHOOSES to place it in closed source firmware out of our control? Did you read the LICENSE file that came with the iwlwifi firmware? ''Redistribution. Redistribution and use in binary form, without modification, are permitted provided that the following conditions are met: * Redistributions must reproduce the above copyright notice and the following disclaimer in the documentation and/or other materials provided with the distribution. * Neither the name of Intel Corporation nor the names of its suppliers may be used to endorse or promote products derived from this software without specific prior written permission. * No reverse engineering, decompilation, or disassembly of this software is permitted.'' Yeah that sounds like why we are all here, doesn't it. >> runs of a different, vendor-specific, CPU. Let's not talk about magic >> and impressive "hardware" when the truth is we only talk about the same >> software action on another CPU. The problems with this particular >> offload to firmware: >> >> - it is vendor-specific > > So is everything a driver does because the vendors make the hardware and > firmware. We never get anywhere by being vendor-hostile. We also never > get anywhere by kissing vendor ass. We need to toe a line in between. Yes, it sounds like Jiri said, there are "opinions", since it is widely known that the validity of all opinions are equal, no need therefore for any actual project management decision based on, well, you know, logic and philosophy. >> - it is not time-critical. In fact it just sits there for tens of ms. >> The extra us lost going through mac80211 when it wants to change the >> frequency should not be measurable. It's not like it is some special >> DSP in there that is computing PI faster than the main CPU in the box >> can. It is just changing the frequency now and then, which can >> perfectly well be done in the stack > > I'm using hw_scan as a vehicle for my larger point. But the point is > still valid even if hw_scan is not time critical. What larger point? We have to kiss vendor ass because you must never be "hostile" towards people even if they are trying to "burn" you? Well never mind. >> - it is not exploitable in other ways. If we want to talk about >> "short-sighted", let's talk about managing what can be very generic RF >> hardware in a way that can never do anything but IEEE802.11a/b/g actions > > We can't and shouldn't try to coerce every piece of hardware into a 100% > userspace-controllable SDR. While that would pretty much solve all > _our_ problems (but not everyone else's), it's a pipe-dream and > unrealistic. Sorry, why is it a "pipe-dream and unrealistic" to support the common denominator of the hardware in a flexible way? mac80211 already has a concept of a bitmap of driver low level features. Well never mind. >>> capabilities of the parts that we expect to use it. Saying no to >>> hardware scanning just because it can also be done in software too is >>> wrong. >> To be clear, this isn't a "hardware" action, just an opaque software API >> specific to that chipset, and that runs on a CPU in the chipset. >> >>> with. It's already in, right? Ripping it out for a 100% software >>> agenda is wrong. Let's take out crypto offload then too if we're going >> The iwlwifi proposal is for an opaque vendor-specific firmware API, that >> is also "100% software". Don't get confused by the bogus magic alleged >> "hardware" nomenclature. > > I've been burned by wifi firmware/hardware a lot in the past. All > firmware is a black box API. But the reality of life is that we're not > going to open all vendor firmware overnight, and I can't actually think > of any vendor that provides the source and build tools for their > firmware. That's a reality we have to deal with. We can and should > encourage openness; but hostility gets us nowhere. "The reality of life" is that Intel's closed firmware does not need to have any special place with the scanning action. At this moment it can safely be denied, repudiated and told to go fsck itself with no functional deficit. > Just because it's a black box _doesn't_ mean we make it impossible to > utilize specific features that some hardware has, like crypto offload or > hwscan. _That's_ the short-sighted part. We need to keep flexibility > in the stack to make this sort of thing possible and let people > experiment with it. Yep *INTEL* will have a lot of fun "experimenting" with their closed-source firmware. Nobody else or you can get sued. We are talking about closed source *FIRMWARE* here, not hardware. mac80211 can be an enabler of moving stuff behind the closed barrier or can discourage it, and that is a philosophical issue controlled by the project leaders. The project is BY NO MEANS A POWERLESS BYSTANDER in this case. -Andy - 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
