From: "Markus Rechberger" <mrechberger@gmail.com>
To: "Another Sillyname" <anothersname@googlemail.com>
Cc: linux-dvb@linuxtv.org
Subject: Re: [linux-dvb] Lifeview DVB-T from v4l-dvb and Pinnacle Hybrid USb from v4l-dvb-kernel......help
Date: Mon, 31 Mar 2008 01:45:59 +0200 [thread overview]
Message-ID: <d9def9db0803301645s17fbb36vbce4c0631ccafa49@mail.gmail.com> (raw)
In-Reply-To: <a413d4880803301640u20b77b9cya5a812efec8ee25c@mail.gmail.com>
On 3/31/08, Another Sillyname <anothersname@googlemail.com> wrote:
> I have a machine that has an internal card that's a Lifeview DVB and
> works fine using the v4l-dvb mercurial sources.
>
> I want to add a Pinnacle USB Hybrid stick (em28xx) that does not work
> using the v4l-dvb sources but does work using the v4l-dvb-kernel
> version.
>
> 1. Will the number of em28xx cards supported by v4l-dvb be increased
> shortly? (My card id was 94 IIRC ).
>
> 2. Can I mix and match from the sources...i.e. can I graft the em28xx
> stuff from v4l-dvb-kernel into the v4l-dvb source and compile
> successfully or has the underlying code changed at a more strategic
> level?
>
> 3. Why did the sources branch? Was there a good technical reason for this?
>
> 4. If I can't use the v4l-dvb sources to get my em28xx working what's
> the chances of getting the v4l-dvb-kernel stuff working for the
> lifeview flydvb card?
>
Hi,
do you have the pinnacle 330e or the 320e?
(following is the 320e)
http://www.compareindia.com/media/images/2007/jul/img_5282_2601_pinnacle.jpg
Markus
_______________________________________________
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-03-30 23:46 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-30 23:40 [linux-dvb] Lifeview DVB-T from v4l-dvb and Pinnacle Hybrid USb from v4l-dvb-kernel......help Another Sillyname
2008-03-30 23:45 ` Markus Rechberger [this message]
2008-03-30 23:57 ` Another Sillyname
2008-03-31 2:20 ` Another Sillyname
2008-03-31 10:03 ` Markus Rechberger
2008-03-31 13:20 ` Another Sillyname
2008-03-31 20:02 ` Aidan Thornton
2008-03-31 20:27 ` Another Sillyname
2008-03-31 22:59 ` Markus Rechberger
2008-03-31 23:27 ` Markus Rechberger
2008-04-01 1:15 ` Another Sillyname
2008-04-01 5:24 ` Markus Rechberger
2008-04-01 21:06 ` Aidan Thornton
2008-04-01 23:41 ` Another Sillyname
2008-04-02 0:08 ` hermann pitton
2008-04-02 16:42 ` Aidan Thornton
2008-04-03 0:04 ` Another Sillyname
2008-04-03 13:11 ` Aidan Thornton
2008-04-03 21:00 ` Another Sillyname
2008-04-04 4:23 ` Another Sillyname
2008-04-04 16:06 ` Aidan Thornton
2008-04-02 0:53 ` hermann pitton
2008-04-04 11:50 ` Simon Kenyon
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=d9def9db0803301645s17fbb36vbce4c0631ccafa49@mail.gmail.com \
--to=mrechberger@gmail.com \
--cc=anothersname@googlemail.com \
--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