dave <daf@a64.comcast.net> wrote:
> dave <daf@a64.comcast.net> wrote:
>> I just got a 2nd bktr card and installed it. The 2nd card is
>> not configured. Both cards work when plugged into the first pci
>> slot. Whichever card is plugged into the 2nd pci slot does not
>> work. I used MADEDEV to create bktr1 and that seems to have
>> worked.
>>
>> crw-r--r-- 1 root wheel 49, 0 Jan 14 13:49 /dev/bktr0
>> crw-r--r-- 1 root wheel 49, 1 Jan 30 17:04 /dev/bktr1
>>
>> Any ideas what's wrong?
>>
> Extracted from Dmesg:
>
> bktr0 at pci1 dev 0 function 0 "Brooktree BT878" rev 0x11: irq 11
> bktr0: Hauppauge WinCast/TV, <no> tuner.
> bktr0 at pci1 dev 0 function 0 "Brooktree BT878" rev 0x11: irq 11
> bktr0: Hauppauge WinCast/TV, <no> tuner.
>
> It appears that the two bktr devices are given the same address during
> boot. I don't know if this is because the cards are hardwired to the
> pci address or if this is a bug in bktr. I tried doing an upgrade to
> see if the devices would be made correctly, but only bktr0 was made
> by MAKEDEV.

A quick look at the pci scanning code for bktr reveals that the code
to update the eeprom on the card is not implemented. So it is my guess
that after the pci configuration the two cards are seen as one since
they have not been configured during boot to have different addresses.