Gigabyte 8300

Gigabyte 8300

[Dagur Ammendrup]

Hi,

I bought a Gigabyte U8300 today which is a hybrid USB tuner. These are
the specifications according to the manufacturer:

Analog: TVPAL / SECAM / NTSC
Decoder chip: Conexant CX23102
Digital TV: DVB-T
Interface: USB 2.0
Others Support: Microsoft® Windows 2000, XP, MCE and Windows Vista MCE
/ Win 7 32/ 64bits
Remote sensor Interface: IR
Tuner: NXP TDA18271

Now I know that the decoder chip is supported in other USB sticks but
mine is not recognised. Here is my lsusb output:

Bus 001 Device 004: ID 1b80:d416 Afatech

And here is the dmesg info I get when I plug it in:

[ 2981.693805] usb 1-2: USB disconnect, address 2
[ 2991.760091] usb 1-2: new high speed USB device using ehci_hcd and address 4
[ 2991.916044] usb 1-2: configuration #1 chosen from 1 choice


Is there anyone out there who might be interested in adding support
for this (or guide me through it)?


thanks,
Dagur

Re: Gigabyte 8300

[Joel Wiramu Pauling]

What sort of afatech chip?

af9035 are not supported at all. Only af9015's which are in the older devices.

On 3 September 2010 12:55, Dagur Ammendrup <dagurp@gmail.com> wrote:
> Hi,
>
> I bought a Gigabyte U8300 today which is a hybrid USB tuner. These are
> the specifications according to the manufacturer:
>
> Analog: TVPAL / SECAM / NTSC
> Decoder chip: Conexant CX23102
> Digital TV: DVB-T
> Interface: USB 2.0
> Others Support: Microsoft® Windows 2000, XP, MCE and Windows Vista MCE
> / Win 7 32/ 64bits
> Remote sensor Interface: IR
> Tuner: NXP TDA18271
>
> Now I know that the decoder chip is supported in other USB sticks but
> mine is not recognised. Here is my lsusb output:
>
> Bus 001 Device 004: ID 1b80:d416 Afatech
>
> And here is the dmesg info I get when I plug it in:
>
> [ 2981.693805] usb 1-2: USB disconnect, address 2
> [ 2991.760091] usb 1-2: new high speed USB device using ehci_hcd and address 4
> [ 2991.916044] usb 1-2: configuration #1 chosen from 1 choice
>
>
> Is there anyone out there who might be interested in adding support
> for this (or guide me through it)?
>
>
> thanks,
> Dagur
> --
> To unsubscribe from this list: send the line "unsubscribe linux-media" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>

Re: Gigabyte 8300

[Dagur Ammendrup]

I thought "Conexant CX23102" was the chip. How can I find this out? I
have access to a windows machine if that helps.




2010/9/3 Joel Wiramu Pauling <joel@aenertia.net>:
> What sort of afatech chip?
>
> af9035 are not supported at all. Only af9015's which are in the older devices.
>
> On 3 September 2010 12:55, Dagur Ammendrup <dagurp@gmail.com> wrote:
>> Hi,
>>
>> I bought a Gigabyte U8300 today which is a hybrid USB tuner. These are
>> the specifications according to the manufacturer:
>>
>> Analog: TVPAL / SECAM / NTSC
>> Decoder chip: Conexant CX23102
>> Digital TV: DVB-T
>> Interface: USB 2.0
>> Others Support: Microsoft® Windows 2000, XP, MCE and Windows Vista MCE
>> / Win 7 32/ 64bits
>> Remote sensor Interface: IR
>> Tuner: NXP TDA18271
>>
>> Now I know that the decoder chip is supported in other USB sticks but
>> mine is not recognised. Here is my lsusb output:
>>
>> Bus 001 Device 004: ID 1b80:d416 Afatech
>>
>> And here is the dmesg info I get when I plug it in:
>>
>> [ 2981.693805] usb 1-2: USB disconnect, address 2
>> [ 2991.760091] usb 1-2: new high speed USB device using ehci_hcd and address 4
>> [ 2991.916044] usb 1-2: configuration #1 chosen from 1 choice
>>
>>
>> Is there anyone out there who might be interested in adding support
>> for this (or guide me through it)?
>>
>>
>> thanks,
>> Dagur
>> --
>> To unsubscribe from this list: send the line "unsubscribe linux-media" in
>> the body of a message to majordomo@vger.kernel.org
>> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>>
>

Re: Gigabyte 8300

[Dagur Ammendrup]

I tried it on a windows machine where it's identified as "Conextant
Polaris Video Capture"  or
"oem17.inf:Conexant.NTx86:POLARIS.DVBTX.x86:6.113.1125.1210:usb\vid_1b80&pid_d416&mi_01"
if that tells you anything.




2010/9/3 Dagur Ammendrup <dagurp@gmail.com>:
> I thought "Conexant CX23102" was the chip. How can I find this out? I
> have access to a windows machine if that helps.
>
>
>
>
> 2010/9/3 Joel Wiramu Pauling <joel@aenertia.net>:
>> What sort of afatech chip?
>>
>> af9035 are not supported at all. Only af9015's which are in the older devices.
>>
>> On 3 September 2010 12:55, Dagur Ammendrup <dagurp@gmail.com> wrote:
>>> Hi,
>>>
>>> I bought a Gigabyte U8300 today which is a hybrid USB tuner. These are
>>> the specifications according to the manufacturer:
>>>
>>> Analog: TVPAL / SECAM / NTSC
>>> Decoder chip: Conexant CX23102
>>> Digital TV: DVB-T
>>> Interface: USB 2.0
>>> Others Support: Microsoft® Windows 2000, XP, MCE and Windows Vista MCE
>>> / Win 7 32/ 64bits
>>> Remote sensor Interface: IR
>>> Tuner: NXP TDA18271
>>>
>>> Now I know that the decoder chip is supported in other USB sticks but
>>> mine is not recognised. Here is my lsusb output:
>>>
>>> Bus 001 Device 004: ID 1b80:d416 Afatech
>>>
>>> And here is the dmesg info I get when I plug it in:
>>>
>>> [ 2981.693805] usb 1-2: USB disconnect, address 2
>>> [ 2991.760091] usb 1-2: new high speed USB device using ehci_hcd and address 4
>>> [ 2991.916044] usb 1-2: configuration #1 chosen from 1 choice
>>>
>>>
>>> Is there anyone out there who might be interested in adding support
>>> for this (or guide me through it)?
>>>
>>>
>>> thanks,
>>> Dagur
>>> --
>>> To unsubscribe from this list: send the line "unsubscribe linux-media" in
>>> the body of a message to majordomo@vger.kernel.org
>>> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>>>
>>
>

Re: Gigabyte 8300

[Fernando Cassia]

Just FYI there´s two parts on that string, the "vid" (vendor ID) and
the "pid" (product id)

Vendor ID "1b80" is listed at the usb device id database
as "Afatech" although the product ID is not listed (although all the
products on that section seem to be Digital TV tuners).

http://www.linux-usb.org/usb.ids


--------------
1b80  Afatech
	c810  MC810 [af9015]
	d393  DVB-T receiver [RTL2832U]
	d396  UB396-T [RTL2832U]
	d397  DVB-T receiver [RTL2832U]
	d398  DVB-T receiver [RTL2832U]
	d700  FM Radio SnapMusic Mobile 700 (FM700)
	e383  DVB-T UB383-T [af9015]
	e385  DVB-T UB385-T [af9015]
	e386  DVB-T UB385-T [af9015]
	e39a  DVB-T395U [af9015]
	e39b  DVB-T395U [af9015]


Someone please correct me if Im wrong.

FC

On 2010-09-03, Dagur Ammendrup <dagurp@gmail.com> wrote:
> I tried it on a windows machine where it's identified as "Conextant
> Polaris Video Capture"  or
> "oem17.inf:Conexant.NTx86:POLARIS.DVBTX.x86:6.113.1125.1210:usb\vid_1b80&pid_d416&mi_01"
> if that tells you anything.
>
>
>
>
> 2010/9/3 Dagur Ammendrup <dagurp@gmail.com>:
>> I thought "Conexant CX23102" was the chip. How can I find this out? I
>> have access to a windows machine if that helps.
>>
>>
>>
>>
>> 2010/9/3 Joel Wiramu Pauling <joel@aenertia.net>:
>>> What sort of afatech chip?
>>>
>>> af9035 are not supported at all. Only af9015's which are in the older
>>> devices.
>>>
>>> On 3 September 2010 12:55, Dagur Ammendrup <dagurp@gmail.com> wrote:
>>>> Hi,
>>>>
>>>> I bought a Gigabyte U8300 today which is a hybrid USB tuner. These are
>>>> the specifications according to the manufacturer:
>>>>
>>>> Analog: TVPAL / SECAM / NTSC
>>>> Decoder chip: Conexant CX23102
>>>> Digital TV: DVB-T
>>>> Interface: USB 2.0
>>>> Others Support: Microsoft® Windows 2000, XP, MCE and Windows Vista MCE
>>>> / Win 7 32/ 64bits
>>>> Remote sensor Interface: IR
>>>> Tuner: NXP TDA18271
>>>>
>>>> Now I know that the decoder chip is supported in other USB sticks but
>>>> mine is not recognised. Here is my lsusb output:
>>>>
>>>> Bus 001 Device 004: ID 1b80:d416 Afatech
>>>>
>>>> And here is the dmesg info I get when I plug it in:
>>>>
>>>> [ 2981.693805] usb 1-2: USB disconnect, address 2
>>>> [ 2991.760091] usb 1-2: new high speed USB device using ehci_hcd and
>>>> address 4
>>>> [ 2991.916044] usb 1-2: configuration #1 chosen from 1 choice
>>>>
>>>>
>>>> Is there anyone out there who might be interested in adding support
>>>> for this (or guide me through it)?
>>>>
>>>>
>>>> thanks,
>>>> Dagur
>>>> --
>>>> To unsubscribe from this list: send the line "unsubscribe linux-media"
>>>> in
>>>> the body of a message to majordomo@vger.kernel.org
>>>> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>>>>
>>>
>>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-media" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>


-- 
"It begins with a blessing
And it ends with a curse;
Making life easy,
By making it worse;"

-- Kevin Ayers

Re: Gigabyte 8300

[Antti Palosaari]

On 09/03/2010 02:42 PM, Fernando Cassia wrote:
> Just FYI there´s two parts on that string, the "vid" (vendor ID) and
> the "pid" (product id)
>
> Vendor ID "1b80" is listed at the usb device id database
> as "Afatech" although the product ID is not listed (although all the
> products on that section seem to be Digital TV tuners).
>
> http://www.linux-usb.org/usb.ids
>
>
> --------------
> 1b80  Afatech
> 	c810  MC810 [af9015]
> 	d393  DVB-T receiver [RTL2832U]
> 	d396  UB396-T [RTL2832U]
> 	d397  DVB-T receiver [RTL2832U]
> 	d398  DVB-T receiver [RTL2832U]
> 	d700  FM Radio SnapMusic Mobile 700 (FM700)
> 	e383  DVB-T UB383-T [af9015]
> 	e385  DVB-T UB385-T [af9015]
> 	e386  DVB-T UB385-T [af9015]
> 	e39a  DVB-T395U [af9015]
> 	e39b  DVB-T395U [af9015]
>
>
> Someone please correct me if Im wrong.

You are correct. Someone added this wrong name about year back. In my 
understanding it should be KWorld instead of Afatech. I am not even 100% 
if it is KWorld since that VID is seen very many designs...

IIRC it was me who added this to the dvb-usb-ids.h:
#define USB_VID_KWORLD_2			0x1b80


Antti
-- 
http://palosaari.fi/

Re: Gigabyte 8300

[Andy Walls]

On Fri, 2010-09-03 at 10:55 +0000, Dagur Ammendrup wrote:
> I tried it on a windows machine where it's identified as "Conextant
> Polaris Video Capture"  or
> "oem17.inf:Conexant.NTx86:POLARIS.DVBTX.x86:6.113.1125.1210:usb\vid_1b80&pid_d416&mi_01"
> if that tells you anything.


Polaris refers to the series of CX2310[012] chips IIRC.

Support would need changes to the cx231xx driver, and possibly changes
to the cx25480 module, depending on how far the board differs from
Conexant reference designs.

Regards,
Andy

> 
> 
> 
> 2010/9/3 Dagur Ammendrup <dagurp@gmail.com>:
> > I thought "Conexant CX23102" was the chip. How can I find this out? I
> > have access to a windows machine if that helps.
> >
> >
> >
> >
> > 2010/9/3 Joel Wiramu Pauling <joel@aenertia.net>:
> >> What sort of afatech chip?
> >>
> >> af9035 are not supported at all. Only af9015's which are in the older devices.
> >>
> >> On 3 September 2010 12:55, Dagur Ammendrup <dagurp@gmail.com> wrote:
> >>> Hi,
> >>>
> >>> I bought a Gigabyte U8300 today which is a hybrid USB tuner. These are
> >>> the specifications according to the manufacturer:
> >>>
> >>> Analog: TVPAL / SECAM / NTSC
> >>> Decoder chip: Conexant CX23102
> >>> Digital TV: DVB-T
> >>> Interface: USB 2.0
> >>> Others Support: Microsoft® Windows 2000, XP, MCE and Windows Vista MCE
> >>> / Win 7 32/ 64bits
> >>> Remote sensor Interface: IR
> >>> Tuner: NXP TDA18271
> >>>
> >>> Now I know that the decoder chip is supported in other USB sticks but
> >>> mine is not recognised. Here is my lsusb output:
> >>>
> >>> Bus 001 Device 004: ID 1b80:d416 Afatech
> >>>
> >>> And here is the dmesg info I get when I plug it in:
> >>>
> >>> [ 2981.693805] usb 1-2: USB disconnect, address 2
> >>> [ 2991.760091] usb 1-2: new high speed USB device using ehci_hcd and address 4
> >>> [ 2991.916044] usb 1-2: configuration #1 chosen from 1 choice
> >>>
> >>>
> >>> Is there anyone out there who might be interested in adding support
> >>> for this (or guide me through it)?
> >>>
> >>>
> >>> thanks,
> >>> Dagur
> >>> --
> >>> To unsubscribe from this list: send the line "unsubscribe linux-media" in
> >>> the body of a message to majordomo@vger.kernel.org
> >>> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> >>>
> >>
> >
> --
> To unsubscribe from this list: send the line "unsubscribe linux-media" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: Gigabyte 8300

[Devin Heitmueller]

On Fri, Sep 3, 2010 at 12:01 PM, Andy Walls <awalls@md.metrocast.net> wrote:
> On Fri, 2010-09-03 at 10:55 +0000, Dagur Ammendrup wrote:
>> I tried it on a windows machine where it's identified as "Conextant
>> Polaris Video Capture"  or
>> "oem17.inf:Conexant.NTx86:POLARIS.DVBTX.x86:6.113.1125.1210:usb\vid_1b80&pid_d416&mi_01"
>> if that tells you anything.
>
>
> Polaris refers to the series of CX2310[012] chips IIRC.
>
> Support would need changes to the cx231xx driver, and possibly changes
> to the cx25480 module, depending on how far the board differs from
> Conexant reference designs.

I've been working with Conexant on this, and have their current tree here:

https://www.kernellabs.com/hg/~dheitmueller/polaris4/

So if you feel the urge to do any new device support, I would suggest
using this as a starting point.

Devin

-- 
Devin J. Heitmueller - Kernel Labs
http://www.kernellabs.com

Re: Gigabyte 8300

[Kamil Kaminski]

Devin Heitmueller <dheitmueller <at> kernellabs.com> writes:

> 
> On Fri, Sep 3, 2010 at 12:01 PM, Andy Walls <awalls <at> md.metrocast.net> 
wrote:
> > On Fri, 2010-09-03 at 10:55 +0000, Dagur Ammendrup wrote:
> >> I tried it on a windows machine where it's identified as "Conextant
> >> Polaris Video Capture"  or
> >> 
"oem17.inf:Conexant.NTx86:POLARIS.DVBTX.x86:6.113.1125.1210:usb\vid_1b80&pid_d41
6&mi_01"
> >> if that tells you anything.
> >
> >
> > Polaris refers to the series of CX2310[012] chips IIRC.
> >
> > Support would need changes to the cx231xx driver, and possibly changes
> > to the cx25480 module, depending on how far the board differs from
> > Conexant reference designs.
> 
> I've been working with Conexant on this, and have their current tree here:
> 
> https://www.kernellabs.com/hg/~dheitmueller/polaris4/
> 
> So if you feel the urge to do any new device support, I would suggest
> using this as a starting point.
> 
> Devin
> 


Hello everyone,

I'd like to refresh a little this thread as I have also bought this device and 
I'm willing to donate my time to make it working with Linux.

The bad news is that I am not familiar with Linux API (and device programming at 
all), so I can only offer myself for testing and gathering informations.

I have taken two high resolution pictures of this board.
As you (propably) know, it has 3 chips:
- Conexant 23102-11Z
- Conexant 24232-11Z
- NXP TDA18271 HDC2

The board is labeled UD412 if it makes any sense.

Pictures are on Picasa account: 
https://picasaweb.google.com/kamilkaminski000/GigabyteU8300?
authuser=0&authkey=Gv1sRgCID_5oOcsdXRpwE&feat=directlink
Both are 10MPix, you can zoom-in.

Device is still not recognized on Gentoo with 2.6.39-r3 (2.6.39.3) kernel.
It has same vendor id and device id (1b80:d416).

I have seen that there are drivers ready for tuner and for conexant chip. Is it 
really a problem to put them together?

I do not know where to start, and this thread is the only one Google shows.

I do not understand also the last message on thread, I have checked kernellabs 
code, but haven't seen my device in USB devices table for cx231xx. No cx2432 
also.

Best regards,
Kamil Kaminski