From: Kamil Kaminski <kamil@mrblur.net>
To: linux-media@vger.kernel.org
Subject: Re: Gigabyte 8300
Date: Wed, 13 Jul 2011 19:00:43 +0000 (UTC) [thread overview]
Message-ID: <loom.20110713T195633-611@post.gmane.org> (raw)
In-Reply-To: AANLkTimvC6811Pb-sxTVSod-p2U+Cmy5QUenKRn9ceYX@mail.gmail.com
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
prev parent reply other threads:[~2011-07-13 19:05 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-03 0:55 Gigabyte 8300 Dagur Ammendrup
2010-09-03 1:54 ` Joel Wiramu Pauling
2010-09-03 10:23 ` Dagur Ammendrup
2010-09-03 10:55 ` Dagur Ammendrup
2010-09-03 11:42 ` Fernando Cassia
2010-09-03 13:48 ` Antti Palosaari
2010-09-03 16:01 ` Andy Walls
2010-09-03 16:12 ` Devin Heitmueller
2011-07-13 19:00 ` Kamil Kaminski [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=loom.20110713T195633-611@post.gmane.org \
--to=kamil@mrblur.net \
--cc=linux-media@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).