public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
* [linux-dvb] OnAir creator seems to be recognized, but what device is what?
@ 2009-01-12  3:50 A. F. Cano
  2009-01-14  4:27 ` CityK
  0 siblings, 1 reply; 2+ messages in thread
From: A. F. Cano @ 2009-01-12  3:50 UTC (permalink / raw)
  To: linux-dvb

Hello again,

I've been trying to make the OnAir creator work.  So far it hasn't been
easy but I'm making some progress.  Pvrusb2 told me in the log file that
a firmware file was missing, so I went looking for it by name.  After
a convoluted procedure extracting windows-centric files and renaming the
proper one to v4l-cx2341x-enc.fw I put it in /lib/modules and did away with
the missing firware message.  Dvbusb2 seems to recognize the device ok.
In fact it seems to create

/dev/dvb/adapter0/demux0
/dev/dvb/adapter0/dvr0
/dev/dvb/adapter0/frontend0
/dev/dvb/adapter0/net0

And I also see /dev/video0

But what do those devices represent?  Is /dev/video0 the analog tuner?
is /dev/dvb/adapter0/dvr0 the digital tuner?  What are the others?
I have been trying to configure mythtv but have no idea what to tell it
about this device.  The mythtv docs say that if you  have a card with 2
tuners, define it as a DVB.  But, mythtv-setup identifies it correcly
(by name) as an analog card /dev/video0, if I set it up as a DVB it claims
it is a DVICO or Air2PC or...  It does not seem to know about the /dev/dvb
devices.  Do I need to configure the OnAir Creator as 1 or 2 devices?

Can someone tell me a quick and easy way to test the device? maybe with
mplayer?  I have an analog camera connected to the composite input, so
even if I don't get any channels with the rabbit ears and loop antenna,
that should work as a test.

I have posted the higher level questions to the mythtv mailing list, but
no answers yet.  Any hints would be welcome.

A.


_______________________________________________
linux-dvb users mailing list
For V4L/DVB development, please use instead linux-media@vger.kernel.org
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: [linux-dvb] OnAir creator seems to be recognized, but what device is what?
  2009-01-12  3:50 [linux-dvb] OnAir creator seems to be recognized, but what device is what? A. F. Cano
@ 2009-01-14  4:27 ` CityK
  0 siblings, 0 replies; 2+ messages in thread
From: CityK @ 2009-01-14  4:27 UTC (permalink / raw)
  To: A. F. Cano; +Cc: linux-dvb, Linux-media

A. F. Cano wrote:
> Dvbusb2 seems to recognize the device ok.
> In fact it seems to create
>
> /dev/dvb/adapter0/demux0
> /dev/dvb/adapter0/dvr0
> /dev/dvb/adapter0/frontend0
> /dev/dvb/adapter0/net0
>
> And I also see /dev/video0
>
> But what do those devices represent?  Is /dev/video0 the analog tuner?
> is /dev/dvb/adapter0/dvr0 the digital tuner?  What are the others?
>   

When a driver module loads, the device manager udev will create device
nodes on /dev.

For dvb devices you get the character devices under /dev/dvb/adapterN
(where N = 0 to whatever). The character devices for each adapter N
are enumerated in form of M=0 to whatever. For example:
/dev/dvb/adapter0/frontend0 .... if the same device had a second
frontend, that character device would be enumerated by
/dev/dvb/adapter0/frontend1 ... if you had another dvb adapter in the
system, then you would see /dev/dvb/adapter1/frontend0 and so forth.

* The frontend device controls the tuner and demodulator.
* The demux controls the filters for processing the transport stream (TS).
* the dvr is a logical device that is associated with the demux
character device ... it delivers up the TS for either:
(1) immediate playback --- in which case it has to be decoded either:
a) on the device itself [its rare for PC devices to have hardware
decoding, but not so for STB] or
b) downstream by the system [the usual route for PC devices -- i.e.
software decoding via the host CPU, and possibly assisted by the GPU) ]
or
(2) saving to disk for later playback.
* the net character device controls IP-over-DVB

Similarly, with video capture (or, if you prefer, V4L) devices, you get
the /dev/video device node and the videoN character devices.

For more info, have a look at the DVB and V4L APIs.

> I have been trying to configure mythtv but have no idea what to tell it
> about this device.  The mythtv docs say that if you  have a card with 2
> tuners, define it as a DVB.  But, mythtv-setup identifies it correcly
> (by name) as an analog card /dev/video0, if I set it up as a DVB it claims
> it is a DVICO or Air2PC or...  It does not seem to know about the /dev/dvb
> devices.  Do I need to configure the OnAir Creator as 1 or 2 device 
>
> ... 
>
> I have posted the higher level questions to the mythtv mailing list, but
>
> no answers yet.  Any hints would be welcome.
>   

Sorry, no input on the myth specific questions, though surely someone
else might be able to.

> Can someone tell me a quick and easy way to test the device? maybe with
> mplayer?  I have an analog camera connected to the composite input, so
> even if I don't get any channels with the rabbit ears and loop antenna,
> that should work as a test.
See the wiki -- in particular, in the User Section, see the testing your
DVB device article. Also see the MPlayer article.



^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2009-01-14  4:27 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2009-01-12  3:50 [linux-dvb] OnAir creator seems to be recognized, but what device is what? A. F. Cano
2009-01-14  4:27 ` CityK

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox