Devin,
thanks for the support.
In the meanwhile, can I try to force the "new" vendor id?
Since I have another pinnacle USB device, I was thinking about
creating a new vendor (something like USB_VID_PINNACLE2).
Is it enough to add it just after the USB_VID_PINNACLE definition and
change the 57th line to
{ USB_DEVICE(USB_VID_PINNACLE2, USB_PID_PINNACLE_PCTV73ESE) },
or should I do something else?
Thank you again,
Matteo
On Mon, Oct 19, 2009 at 10:41 PM, Devin Heitmueller
<dheitmueller@xxxxxxxxxxxxxx> wrote:
> On Mon, Oct 19, 2009 at 4:28 PM, Matteo Miraz <telegraph.road@xxxxxxxxx> wrote:
>> in the changeset 12886:ba22a9decfab was added a device called
>> USB_PID_PINNACLE_PCTV73ESE, with id 0245
>>
>> However, the vendor is USB_VID_PINNACLE ( 0x2304 ) instead of 0x2013 (
>> as reported for my usb dvb by lsusb )
>>
>> How can I fix it? How can I create a new vendor with the correct ID,
>> and try if the module works? I'm new to the kernel development, so I'm
>> afraid to make mistakes!
>
> I've sent some email to the engineer I know over at PCTV Systems, and
> will report back when I know more. My suspicion is that they changed
> the USB ID and we just need to update the driver to allow for either
> USB ID to be associated with the device.
>
> Devin
>
> --
> Devin J. Heitmueller - Kernel Labs
> http://www.kernellabs.com
>
--
ciao, teo
20 minutes is the average that a Windows based PC lasts
before it's compromised. (Internet Storm Center)
--
To unsubscribe from this list: send the line "unsubscribe linux-media" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
