From: Rick Bilonick <rab@nauticom.net>
To: video4linux-list <video4linux-list@redhat.com>
Subject: Re: Compiling v4l-dvb-kernel for Ubuntu and for F8
Date: Fri, 26 Dec 2008 00:30:43 -0500 [thread overview]
Message-ID: <1230269443.3450.48.camel@localhost.localdomain> (raw)
In-Reply-To: <20081226010307.2c7e3b55@gmail.com>
On Fri, 2008-12-26 at 01:03 -0200, Douglas Schilling Landgraf wrote:
> Hello Rick,
>
> On Thu, 25 Dec 2008 14:36:34 -0500
> Rick Bilonick <rab@nauticom.net> wrote:
>
> > I'm trying to get em28xx working under Ubuntu and F8, but when I
> > "make" I get errors saying that dmxdev.h, dvb_demux.h, dvb_net.h, and
> > dvb_frontend.h cannot be found.
> >
> > I get the same errors in F7 with v4l-dvb-experimental (same with
> > v4l-dvb-kernel):
>
> Please use upstream driver to get support (if needed) from mail-list:
> http://linuxtv.org/v4lwiki/index.php/Em28xx_devices
>
> Cheers,
> Douglas
I don't know what you mean by "upstream" driver. In Ubuntu 8.10, I did
an "lsmod" and both the em28xx and em28xx_dvb modules show up. "modprobe
-l | grep em28" also shows these modules. Does that mean I don't have to
compile them from scratch? If they already exist, what else do I have to
do to get the HD Pro to receive broadcasts?
Rick B.
--
video4linux-list mailing list
Unsubscribe mailto:video4linux-list-request@redhat.com?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/video4linux-list
next prev parent reply other threads:[~2008-12-26 5:31 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-25 19:36 Compiling v4l-dvb-kernel for Ubuntu and for F8 Rick Bilonick
2008-12-25 21:24 ` Markus Rechberger
2008-12-26 3:03 ` Douglas Schilling Landgraf
2008-12-26 5:30 ` Rick Bilonick [this message]
2008-12-26 19:41 ` Douglas Schilling Landgraf
2008-12-27 0:35 ` Rick Bilonick
2008-12-27 4:56 ` Rick Bilonick
2008-12-27 6:23 ` Rick Bilonick
2008-12-27 9:39 ` Rick Bilonick
2008-12-27 16:09 ` Devin Heitmueller
2008-12-28 1:46 ` Douglas Schilling Landgraf
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=1230269443.3450.48.camel@localhost.localdomain \
--to=rab@nauticom.net \
--cc=video4linux-list@redhat.com \
/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.