Michael Krufky wrote:
> Eric,
> You can remove every hunk of your patch except for the one above, but
> instead link that subsystem ID to SAA7134_BOARD_KWORLD_ATSC110 ...
> The two cards are the same, as far as the driver is concerned.
> Will you be able to test ATSC, QAM and NTSC?
> Cheers,
> Mik
Michael Krufky wrote:
> Will you be able to test ATSC, QAM and NTSC?
I've been using the card for QAM in my mythbox without problems.
I did a quick check with xawtv (old school!) of the analog/NTSC side,
and it also seems fine.
This is all with the saa7134 module loaded with "card=90,90" (with
CityK wrote:
> Eric Sandeen wrote:
>> Kworld ATSC-115 card PCI ID
>>
>>
>>
>> + .subvendor= 0x17de,
>> + .subdevice= 0x7352,
>
> I had been wondering about this for a while -- inquiries that I had made
> with other 115 users went unanswered, and, think
Eric Sandeen wrote:
> Kworld ATSC-115 card PCI ID
>
>
>
> + .subvendor= 0x17de,
> + .subdevice= 0x7352,
I had been wondering about this for a while -- inquiries that I had made
with other 115 users went unanswered, and, thinking that I could find
the s
Michael Krufky wrote:
>> @@ -4123,6 +4147,12 @@ struct pci_device_id saa7134_pci_tbl[] =
>> .driver_data = SAA7134_BOARD_KWORLD_ATSC110,
>> },{
>> .vendor = PCI_VENDOR_ID_PHILIPS,
>> + .device = PCI_DEVICE_ID_PHILIPS_SAA7133, /* SAA
On 9/27/07, Eric Sandeen <[EMAIL PROTECTED]> wrote:
> So, just got my shiny new Kworld ATSC-115 card in the mail.
>
> Any desire for a patch to actually detect the new PCI ID, even
> though I guess it's pretty much the same card as the ATSC 110?
>
> Full-on pedantic patch below, I know not all of t
So, just got my shiny new Kworld ATSC-115 card in the mail.
Any desire for a patch to actually detect the new PCI ID, even
though I guess it's pretty much the same card as the ATSC 110?
Full-on pedantic patch below, I know not all of this needs to be
duplicated if it's truly identical hardware...
