lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID:  <mj+md-20061113.094333.4571.atrey@ucw.cz>
Date:	Mon, 13 Nov 2006 10:45:22 +0100
From:	Martin Mares <mj@....cz>
To:	Ben Collins <ben.collins@...ntu.com>
Cc:	Nicholas Miell <nmiell@...cast.net>, linux-kernel@...r.kernel.org
Subject: Re: [RFC] Pushing device/driver binding decisions to userspace

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   <mj@....cz>   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 majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ