From: Joe Julian <joe@julianfamily.org>
To: linux-dvb@linuxtv.org
Subject: Re: [linux-dvb] HVR2250 / HVR2200 / SAA7164 status
Date: Thu, 02 Oct 2008 07:57:57 -0700 [thread overview]
Message-ID: <48E4E175.90403@julianfamily.org> (raw)
Steven Toth wrote:
As you know, I'm writing a driver for the SAA7164 chipset, for the
HVR2200 DVB-T and HVR2250 ATSC/QAM products.
People have been asking for status, here's where I am.
Do I have anything to share with people yet? Not yet.
The basic driver framework is done. Firmware is loading, I can
talking to the silicon through the proprietary PCIe ring buffer
interface. I2C is working, eeprom and tuner/demod access is done.
The HVR2250 is responding to azap commands, the tuners and demods
are locking, snr looks pretty good... it's going to be a popular
board for people. The HVR2200 (DVB-T Version) should also worked
with tzap, it's untested and I can't comment on SNR at this stage. I
need to add the DMA/buffering code, this is the missing pieces
before a first public release. When I have anything to share I'll
put up a tree and post a 'testers required' message here.
We're a couple episodes into this fall television season and I'm missing
my shows. ;)
Having another month down, I wanted to send a friendly nudge your
direction, Steve, to see how this is progressing.
_______________________________________________
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
next reply other threads:[~2008-10-02 14:58 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-02 14:57 Joe Julian [this message]
2008-10-02 18:19 ` [linux-dvb] HVR2250 / HVR2200 / SAA7164 status Steven Toth
2008-11-07 13:15 ` Markus Ingalsuo
-- strict thread matches above, loose matches on Subject: below --
2009-02-04 7:34 Davin McCall
2009-02-04 16:55 ` Steven Toth
2009-02-08 1:21 ` David Gundersen
2009-02-08 1:25 ` David Gundersen
2009-02-09 16:04 ` Steven Toth
2009-02-04 21:10 Patrick Allemann
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=48E4E175.90403@julianfamily.org \
--to=joe@julianfamily.org \
--cc=linux-dvb@linuxtv.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