Re: [RFC] Pushing device/driver binding decisions to userspace

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

 



Hello!

> No, in a lot of cases, it's not a deficiency. Take the entire
> drivers/ata/pata_*.ko list. All of them match an IDE driver, however the
> pata driver most times does not support all the same PCI id's for the
> matching ide driver.
> 
> Also the other case I gave where there is an alsa driver and a media
> driver for the same chipset, is by design. It can't be helped. There
> actually is a case for wanting one driver or the other in the case of
> the exact same hardware, depending on the users desire.

If you have two drivers for the same device, there is no problem --
just insmod one of the drivers. The ugly cases are the "a b / b c"
described in the first mail of this thread -- however, are these really
sane? Shouldn't they be split to multiple drivers?

				Have a nice fortnight
-- 
Martin `MJ' Mares   <[email protected]>   http://atrey.karlin.mff.cuni.cz/~mj/
Faculty of Math and Physics, Charles University, Prague, Czech Rep., Earth
A bug in the code is worth two in the documentation.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]
  Powered by Linux