Re: Stradis driver conflicts with all other SAA7146 drivers

[Mauro Carvalho Chehab]

Em Dom, 2006-05-28 às 19:58 +0200, Christer Weinigel escreveu:
> Mauro Carvalho Chehab <mchehab@xxxxxxxxxxxxx> writes:

> 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.
Yes. it is this I was trying to say :)
> 
> 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.  How many of the
> boards supported by the generic saa7146 driver are broken the same
> way?
I don't have any saa7146 board, but, on bttv, most boards don't have its
own PCI ID.
> 
> Can't the stradis driver do the same thing as the other drivers and
> explicitly match the broken zero subvendor id and the non-broken
> subvendor IDs?
> 

> That would fix the problem for me and make it SEP. :-)

This seems to be an interesting idea: to make stradis just probe the
recognized IDs and the generic one. It won't solve, however, the probing
intersection for dpc7146f, hexium_orion, mxb, and stradis when no
subvendor ID is specified on the board.
> 
> Can somebody with a SDM2xx stradis board mail me the output from
> "lspci -vn" and I'll cobble together a patch that does this?
> 
> This still needs solving properly, but at least it makes it less of
> a problem for people with non-broken hardware.
> 
>   /Christer
> 
Cheers, 
Mauro.

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/