Re: [v4l-dvb-maintainer] Re: Stradis driver conflicts with all other SAA7146 drivers

Michael Hunold
2006-05-29T12:45:17Z

Hello,

sorry for jumping into this thread so late.

on 28.05.2006 19:58 Christer Weinigel said the following:
> Mauro Carvalho Chehab <mchehab@infradead.org> writes:
>>Em Dom, 2006-05-28 às 09:01 -0700, Nathan Laredo escreveu:

> dpc7146, hexium_orion and mxb don't match all PCI IDs, they only match
> boards with zero as a board ID. So they won't conflict with
> non-broken boards that have valid subvendor IDs. But they will
> conflict with each other.

That's unfortunately right.

> How may of these boards are broken and have zeroes in the
> subvendor/subdevice fields? Apparently some of the dpc7146f,
> hexium_orion, mxb, and stradis boards are broken.

I would not call them broken.

They simply don't have subvendor/subdevice informations, but when these
informations are requested, the card gives back zeroes.

> How many of the
> boards supported by the generic saa7146 driver are broken the same
> way?

I can confirm this for the dpc7146, the mxb and the hexium_orion.

> This still needs solving properly, but at least it makes it less of
> a problem for people with non-broken hardware.

Up to now, this problem did not show up so drastically. On the one hand,
just a few dozen people use the MXB, a handful use the hexium_orion and
the dpc7146 is really rare. All these users then simply tweaked their
environment so that it works for the next boot.

In order to fix this, these drivers should not be autoloaded because
there is no sane way to autodetect these cards. In theory, you could do
an i2c bus scan and check if all devices are there. But since MXB and
dpc7146 both use the saa7111 video decoder on address 0x11 IIRC, the
dpc7146 will grab any MXB device if loaded before.

Distributions probably should keep these drivers from being autoloaded.

> /Christer

Best regards
Michael.