Re: User asks: can we decouple device vendor IDs from drivers?

[ Available lists | Index of freebsd-hackers | Month of Nov 2003 | Week of 1 Nov 2003 | Raw email | View thread | Wrap long lines | Reply ]
From
Mark Murray <mark@grondar.org>
Date
1 Nov 2003 02:15:41
Subject
Re: User asks: can we decouple device vendor IDs from drivers?
Message-ID
200311011013.hA1ADH4L032554@grimreaper.grondar.org

In reply to
Referenced by

[ Hide this part ]
"M. Warner Losh" writes:
> The problem with decoupling things entirely from the drivers is that
> many drivers will say "if I have this revision of that card, do this
> workaround." or "if I'm this or newer, I have this feature" both of
> which are broken by the kernel forcing the driver to service a given
> hunk of hardware.

Hmm. Careful design may sort this out, methinks. If the file (which
sounds analagous to /boot/device.hints to me) turned devid's into
generic griver requrements (DEVID(0x04589045) == driver(foo) revision(bar)
flags(baz, qux)) would that not be usable? (/me wonders if he has the time
to do this - he's certainly interested)

> The other down side is that when you bork the alias
> file on solaris, you are so hozed.

... like most of the files in /boot/...

> However, it would make the dynamic loading of drivers easier.

I really like to concept of configuring things with vi(1), instead of
with gcc :-)

M
--
Mark Murray
iumop ap!sdn w,I idlaH


Elapsed time: 0.103 seconds