Search Linux Wireless

Re: [PATCH v5 00/33] wireless: kconfig updates

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Wed, Aug 19, 2009 at 2:50 PM, Luis R.
Rodriguez<lrodriguez@xxxxxxxxxxx> wrote:

> Well so to group all of Intel stuff we do need this, at least I can't
> think of a way to do it. If we don't want to group intel stuff then we
> can remove it. Is there a downside to this grouping, for example?

One (admittedly hand-wavy) argument against vendor grouping is that you
don't always know who made the chip.  So you have CompanyA buying CompanyB's
IP, making a product, and then we write a driver for CompanyA's device
called awifi2000.  Meanwhile CompanyB sells it to CompanyC too so their
"C Wifi Plus" product happens to work with the awifi2000 driver.  Now you
have to reorg the menus to put it under CompanyB.

I imagine this is a lot less likely with wireless, if you know enough to
write a driver, you usually know who made it.  But ISTR it happened a lot
with v4l stuff since there are more commodity parts on those cards.

-- 
Bob Copeland %% www.bobcopeland.com
--
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

[Index of Archives]     [Linux Host AP]     [ATH6KL]     [Linux Bluetooth]     [Linux Netdev]     [Kernel Newbies]     [Linux Kernel]     [IDE]     [Security]     [Git]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux ATA RAID]     [Samba]     [Device Mapper]
  Powered by Linux