On Thu, Mar 22, 2007 at 11:15:32AM -0400, Chuck Ebbert wrote:
Chris Brown wrote:
> Thanks for the invite Chuck. Great to read about your appointment working
> with Dave by the way. I can confirm that this rocks.
> To the matter at hand folks:
> for dirty debugging output but essentially:
> I'm running MythTV and the cx88-dvb driver that loaded with all the
> 2.6.18-2.6.19 kernels fails to do so with 2.6.20. Running modprobe loads
> drivers fine. In the not too distant past there used to be a problem with
> the blackbird drivers grabbing control of the card(s) before the correct
> driver did so. I therefore blacklisted the blackbird driver and the correct
> driver loaded, the clouds cleared and the sun shone once more on green
> fields. Now it looks like something similar has returned and I can only
> force the driver to load by adding it to /etc/rc.modules
What are we supposed to do when this kind of thing happens? It appears that
multiple drivers claim to support the same hardware.
Grr, this happens far too often. We have the same with for eg,
orinoco and hostap right now. The usual deal is that we either
just build the 'best' driver for that hardware, or if there's a case
where both drivers support the same hardware _and_ some hardware unique
to them, we nobble the pci table so that the crappier driver
doesn't load on that hardware.
As to which is the best one in this case.. I really don't know.
Or maybe this is a situation where it's valid to have both drivers loaded?
We don't actually support that right now, but patches went to linux-pci list
last week that should be showing up in GregKHs tree adding an alternative
method for drivers to bind to a device in situations where it's possible
for two drivers to drive different parts of the same chip.
(This case has been showing up more and more recently too..
agp vs edac, matroxfb vs lm_sensors,..)