From: Nick Andrew <nick-linuxtv@nick-andrew.net>
To: ausgnome <ausgnome@optusnet.com.au>
Cc: dvb <linux-dvb@linuxtv.org>
Subject: Re: [linux-dvb] Afatech 9015
Date: Wed, 2 Apr 2008 13:39:12 +1100 [thread overview]
Message-ID: <20080402023911.GA27360@tull.net> (raw)
In-Reply-To: <47EE3C5E.8080001@optusnet.com.au>
G'day ausgnome,
On Sat, Mar 29, 2008 at 11:55:58PM +1100, ausgnome wrote:
> I used this tree
> http://linuxtv.org/hg/~anttip/af9015/
Did you need to modify the code at all?
And what's your "lsusb" output?
Nick.
_______________________________________________
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
next prev parent reply other threads:[~2008-04-02 2:39 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-29 2:41 [linux-dvb] Analog capture (saa7113) not working on KNC1 DVB-C Plus (MK3) L.
2008-03-29 3:26 ` thomas schorpp
2008-03-30 5:39 ` L.
2008-03-30 6:33 ` thomas schorpp
2008-03-30 7:16 ` [linux-dvb] KNC1 DVB-C Plus analog input (was: Re: Analog capture (saa7113) not working on KNC1 DVB-C Plus (MK3)) L.
2008-03-30 10:24 ` [linux-dvb] KNC1 DVB-C Plus analog input thomas schorpp
2008-03-30 21:26 ` L.
2008-03-31 2:32 ` thomas schorpp
2008-03-30 8:00 ` [linux-dvb] CI code in budget_av or videobuf rework break analog input? (was Re: Analog capture (saa7113) not working on KNC1 DVB-C Plus (MK3)) L.
2008-03-30 10:28 ` thomas schorpp
2008-03-29 3:38 ` [linux-dvb] Afatech 9015 ausgnome
2008-03-29 5:05 ` ausgnome
2008-03-29 9:48 ` Antti Palosaari
2008-03-29 12:55 ` ausgnome
2008-04-02 2:39 ` Nick Andrew [this message]
2008-04-02 14:35 ` Antti Palosaari
2008-04-02 22:28 ` ausgnome
2008-05-27 9:48 ` Lauri Tischler
2008-05-27 11:15 ` Antti Palosaari
2008-04-08 13:13 ` [linux-dvb] No av with budget_av (Analog inputs not working on KNC1 DVB-C Plus (MK3)) L.
2008-04-08 23:07 ` Oliver Endriss
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=20080402023911.GA27360@tull.net \
--to=nick-linuxtv@nick-andrew.net \
--cc=ausgnome@optusnet.com.au \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.