[pkg-wpa-devel] Driver autodetection
Kel Modderman
kelrin at tpg.com.au
Wed Apr 5 09:40:18 UTC 2006
Reinhard Tartler wrote:
> On Wed, Apr 05, 2006 at 07:24:43AM +1000, Kel Modderman wrote:
>
>> Let me rephrase; I see how it could work :-) , but think it may pose
>> uneccessary labour and/or problems in the future.
>>
>
> Which problems do you see with this approach? The idea is that we let
> udev provide hints which cards should work with which driver (aka
> 'hardware detection'). The list will be based on PCI-IDs, something
> which is already in udev/the kernel.
>
> Gruesse,
> Reinhard
>
Defaulting to "wext" will prove to be more and more true as time goes
on. This will be true for almost all in-kernel modules in the future.
How can we pretend to guess a driver for a interface created by an
external-to-kernel module, across many different user configurations
(driver version, kernel version etc) with any sort of precision? and
also predict what wpa_supplicant driver backend they can use in the
future, in the case that a user updates to a newer version of some
driver? I'd think this to be a very fragile process until I see some
tried and tested code.
My opinion is; its not too hard to add wpa-driver foo to the
configuration, so long as documentation is good.
Kel.
More information about the Pkg-wpa-devel
mailing list