From: Jan Sundman <jan.sundman@aland.net>
To: linux-media@vger.kernel.org
Subject: Re: af9015: tuner id:179 not supported, please report!
Date: Sat, 05 Dec 2009 11:45:10 +0200 [thread overview]
Message-ID: <1260006310.3702.3.camel@desktop> (raw)
In-Reply-To: <37219a840912041003o4d8ebe27wbe3f1c47f55ba7dc@mail.gmail.com>
Hi,
Thanks for the info, I will have a look and see if it is worth the
trouble.
Br,
// Jan
On Fri, 2009-12-04 at 13:03 -0500, Michael Krufky wrote:
> On Thu, Dec 3, 2009 at 5:03 PM, Devin Heitmueller
> <dheitmueller@kernellabs.com> wrote:
> > On Thu, Dec 3, 2009 at 4:47 PM, Bert Massop <bert.massop@gmail.com> wrote:
> >> Hi Jan,
> >>
> >> The datasheet for the TDA18218 can be obtained from NXP:
> >> http://www.nxp.com/documents/data_sheet/TDA18218HN.pdf
> >>
> >> That's all the information I have at the moment, maybe Mike has some
> >> other information (like the Application Note mentioned in the
> >> datasheet, that claims to contain information on writing drivers, but
> >> cannot be found anywhere).
> >>
> >> Best regards,
> >>
> >> Bert
> >
> > Took a quick look at that datasheet. I would guess between that
> > datasheet and a usbsnoop, there is probably enough there to write a
> > driver that basically works for your particular hardware if you know
> > what you are doing. The register map is abbreviated, but probably
> > good enough...
> >
> > Devin
>
> The datasheet is missing too much important information needed to
> write a fully featured driver for the part, and I wouldn't recommend
> using a usbsnoop for this type of tuner, but be my guest and prove me
> wrong.
>
> You might be able to get it working, but you'll end up with tons of
> binary blobs hardcoded for each frequency, unless you use a
> programming guide. Unfortunately, I don't have one that I can share
> :-/
>
> I think you would be much better off purchasing supported hardware, instead.
>
> Good luck, though...
>
> -Mike
> --
> 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
next prev parent reply other threads:[~2009-12-05 9:45 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-01 19:29 af9015: tuner id:179 not supported, please report! Jan Sundman
2009-12-02 22:06 ` Bert Massop
2009-12-02 23:08 ` Michael Krufky
2009-12-03 21:15 ` Jan Sundman
2009-12-03 21:47 ` Bert Massop
2009-12-03 22:03 ` Devin Heitmueller
2009-12-04 18:03 ` Michael Krufky
2009-12-05 9:45 ` Jan Sundman [this message]
2009-12-20 16:05 ` Bert Massop
-- strict thread matches above, loose matches on Subject: below --
2010-02-24 21:42 Bert Massop
2010-02-26 23:01 ` Bert Massop
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=1260006310.3702.3.camel@desktop \
--to=jan.sundman@aland.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