Nils Kassube | 1 Jan 08:26 2008
Picon
Picon

Re: New to linux, want to see if linux system is seeing tv card

Muppet Man wrote:
> Here's my results

Well, that was only the beginning of the dmesg output. Due to the less 
command you can now navigate within the text using the up and down arrow 
keys. Sorry, I should have mentioned it in the previous mail. Search for 
something that looks like a driver for your TV card. That would be the 
interesting part to post here.

Nils

--
video4linux-list mailing list
Unsubscribe mailto:video4linux-list-request <at> redhat.com?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/video4linux-list

Mauro Carvalho Chehab | 1 Jan 12:29 2008

Re: Extract tool for xc3028 firmware

On Mon, 31 Dec 2007 14:57:18 +0000
"Aidan Thornton" <makosoft <at> googlemail.com> wrote:

> 
> 
> On 12/31/07, Mauro Carvalho Chehab <mchehab <at> infradead.org> wrote:
> > On Mon, 31 Dec 2007 03:34:56 -0200
> > Mauro Carvalho Chehab <mchehab <at> infradead.org> wrote:
> > 
> > > I've just added an extraction tool to allow retrieving xc2028/3028
> > firmwares
> > > from HVR-12x0 windows file.
> > > 
> > > In order to use, you need to:
> > >       1) Download the windows driver with something like:
> > >               wget
> > http://www.steventoth.net/linux/xc5000/HVR-12x0-14x0-17x0_1_25_25271_WHQL.zip
> > >       2) Extract the file hcw85bda.sys from the zip into the current dir:
> > >               unzip -j HVR-12x0-14x0-17x0_1_25_25271_WHQL.zip
> > Driver85/hcw85bda.sys
> > >       3) run the script:
> > >               ./extract_xc3028.pl
> > >       4) copy the generated file:
> > >               cp xc3028-v27.fw /lib/firmware
> > > 
> > > I've also added the tool at linux/Documentation/video4linux.
> > > 
> > > This firmware is known to work with most xc2028/xc3028 devices. Please
> > test.
> > 
(Continue reading)

Mauro Carvalho Chehab | 1 Jan 12:41 2008

Re: Extract tool for xc3028 firmware

On Mon, 31 Dec 2007 10:03:38 -0500
"Devin Heitmueller" <devin.heitmueller <at> gmail.com> wrote:

> Hello Mauro,
> 
> Figures.  I spent all day yesterday disassembling the embda.sys for
> the hvr-900 trying to accomplish the same task.

It is hard... It took all day long for me to write a seek tool for detecting the
placements for the firmwares.

> Did you generate the offsets in extract_xc3028.pl using a script
> (knowing what the images to looked like based on the output of a usb
> bus capture)?

See --seek option at v4l2-apps/util/xc3028-firmware.

Cheers,
Mauro
Mauro Carvalho Chehab | 1 Jan 12:45 2008

Re: lirc project needs your help!

On Mon, 31 Dec 2007 16:02:43 +0000
Laurence Darby <ldarby <at> tuffmail.com> wrote:

> 
> Hi,
> 
> There's currently an unresolved problem with some TV card remote
> controls under lirc - at least one card, Winfast 2000XP, is not
> supported by the linux input layer and still requires the lirc_gpio
> module:
> 
> http://sourceforge.net/mailarchive/message.php?msg_name=13608717.post%40talk.nabble.com
> 
> alternative mail archive:
> http://www.nabble.com/Re%3A-LIRC-GPIO-Unnecessary-now--p13608717.html
> 
> The problem is lirc_gpio module uses obsolete symbols, which are:
> 
> bttv_get_cardinfo
> bttv_get_gpio_queue
> 
> It also uses these deprecated symbols, which are enabled by
> CONFIG_VIDEO_V4L1:
> 
> bttv_gpio_enable
> bttv_read_gpio
> bttv_write_gpio
> 
> 
> Can someone here please take a look at this and find out what needs to
(Continue reading)

Laurence Darby | 1 Jan 19:09 2008

Re: lirc project needs your help!

Mauro Carvalho Chehab wrote:

> IMO, the better approach would be to add support for those missing IR
> devices inside bttv driver, and let lirc to use the event handler for
> those.

Yes, that's sensible.  It looks like the info from lirc's gpio driver
would need to be merged into bttv-input.c, here's a relevant comment
from lirc_gpio.c:

	/* The Leadtek WinFast TV 2000 XP card (id 0x6606107d) uses an
	 * extra gpio bit compared to the original TV 2000 card (id
	 * 0x217d6606); as the bttv-0.7.100 driver does not
	 * distinguish between the two cards, we enable the extra bit
	 * based on the card id: */

If I've understood the code correctly, the XP cards use a mask of
0x8f8 (0x9f8 with the enable bit), the non XP cards use 0xf8, or 0x1f8
with enable bit, which is what's used in bttv-input.c.

Do you, or someone else, have the hardware to test if bit 0x800 is all
that's needed?  Is so, there are many more masks defined in lirc_gpio.c,
I guess they'll all need to be checked against the ones in bttv-input.c
and check none are missing before lirc_gpio can be officially deprecated

Thanks,
Laurence

--
video4linux-list mailing list
(Continue reading)

CityK | 1 Jan 21:37 2008

Re: Driver for Acorp DS110/120 DVBWorld PCI2002/USB2102

Igor M. Liplianin wrote:
> Working well for me.
> I plan add support for others DVB cards from DVBWorld (especially DVB-S2 ones)
> How to create my repository in Linuxtv hg tree for that matter?
> Please do not ignore this message!
>
> Patch with drivers for Acorp DS110/120 (DVBWorld PCI2002/USB2102).
> Signed-off-by: Igor M. Liplianin <liplianin <at> me.by>

Igor, did you ever get a response on this?  I have a feeling it slipped
by...

--
video4linux-list mailing list
Unsubscribe mailto:video4linux-list-request <at> redhat.com?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/video4linux-list

CityK | 1 Jan 21:54 2008

Re: New to linux, want to see if linux system is seeing tv card

Muppet Man wrote:
> Greetings all,
> I am relatively new to linux, and I received a tv tuner card.  My question is how do I tell if my system sees the
card?  I am running kubuntu 7.10.  What I am trying to do is get mythtv up and running, and I think I am really
close to getting the card recongized.
> Thanks for your help.
>   

While it previously seemed that you had clearly understood C.Z's message
(http://marc.info/?l=linux-video&m=119897502021351&w=2), I'm now left
wondering if that truly was the case. So, the better question might be
-- what is it exactly that you are attempting to accomplish? Is it
you're belief that you are going to be able to get your card working
from your efforts? If that is the impression that you are operating
under, then you should stop now as you're wasting your time. Please
refer to Chaogui's message again -- the card will not work yet. Be
patient, support is coming.

--
video4linux-list mailing list
Unsubscribe mailto:video4linux-list-request <at> redhat.com?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/video4linux-list

Mauro Carvalho Chehab | 2 Jan 03:08 2008

Re: lirc project needs your help!

On Tue, 1 Jan 2008 18:09:54 +0000
Laurence Darby <ldarby <at> tuffmail.com> wrote:

> Mauro Carvalho Chehab wrote:
> 
> > IMO, the better approach would be to add support for those missing IR
> > devices inside bttv driver, and let lirc to use the event handler for
> > those.
> 
> 
> Yes, that's sensible.  It looks like the info from lirc's gpio driver
> would need to be merged into bttv-input.c, here's a relevant comment
> from lirc_gpio.c:
> 
> 	/* The Leadtek WinFast TV 2000 XP card (id 0x6606107d) uses an
> 	 * extra gpio bit compared to the original TV 2000 card (id
> 	 * 0x217d6606); as the bttv-0.7.100 driver does not
> 	 * distinguish between the two cards, we enable the extra bit
> 	 * based on the card id: */
> 
> If I've understood the code correctly, the XP cards use a mask of
> 0x8f8 (0x9f8 with the enable bit), the non XP cards use 0xf8, or 0x1f8
> with enable bit, which is what's used in bttv-input.c.
> 
> Do you, or someone else, have the hardware to test if bit 0x800 is all
> that's needed?  Is so, there are many more masks defined in lirc_gpio.c,
> I guess they'll all need to be checked against the ones in bttv-input.c
> and check none are missing before lirc_gpio can be officially deprecated

Unfortunately, I don't have. We may assume that lirc_gpio is correct, and write
(Continue reading)

Sean Pi | 2 Jan 09:24 2008
Picon

RE: mplayer's data decoder.


If not change the mplayer configuration file, How can I use command line to run mplayer
when my /dev/video0 have MJPEG data ? If I simply type "mplayer /dev/video0"
it is failure like this:

MPlayer 1.0rc2-4.1.3 (C) 2000-2007 MPlayer Team
CPU: Intel(R) Pentium(R) M processor 1300MHz (Family: 6, Model: 9, Stepping: 5)
CPUflags:  MMX: 1 MMX2: 1 3DNow: 0 3DNow2: 0 SSE: 1 SSE2: 1
Compiled with runtime CPU detection.
mplayer: could not connect to socket
mplayer: No such file or directory
Failed to open LIRC support. You will not be able to use your remote control.

Playing /dev/video0.

MPlayer interrupted by signal 11 in module: demux_open
- MPlayer crashed by bad usage of CPU/FPU/RAM.
  Recompile MPlayer with --enable-debug and make a 'gdb' backtrace and
  disassembly. Details in DOCS/HTML/en/bugreports_what.html#bugreports_crash.
- MPlayer crashed. This shouldn't happen.
  It can be a bug in the MPlayer code _or_ in your drivers _or_ in your
  gcc version. If you think it's MPlayer's fault, please read
  DOCS/HTML/en/bugreports.html and follow the instructions there. We can't and
  won't help unless you provide this information when reporting a possible bug.
*** glibc detected *** mplayer: double free or corruption (out): 0x08aec4a0 ***
======= Backtrace: =========
/lib/tls/i686/cmov/libc.so.6[0xb69fdd65]
/lib/tls/i686/cmov/libc.so.6(cfree+0x90)[0xb6a01800]
mplayer(uninit_player+0x12d)[0x80aaf4d]
[0x0]
(Continue reading)

Hans Verkuil | 2 Jan 10:00 2008
Picon
Picon

Re: How the V4L2 support H.264 encode usb camera ?

On Wednesday 02 January 2008 09:35, Sean Pi wrote:
> >> 2. I check Mplayer lastest release code 1.0rc2, it only support
> >> MJPEG (V4L2_PIX_FMT_MJPEG), no MPEG. so I warry about others. 
> >> shall I know which one you usually use ?
> >
> > MPEG is definitely supported, but not through the v4l API, you just
> > give it the video0 device: mplayer /dev/video0. mplayer will read
> > from that device and recognize an MPEG Program Stream.
> >
> > Also useful apps are v4l2-ctl as a command line app to control most
> > v4l2 settings/controls and qv4l2 which provides a graphical
> > 'control panel' for the MPEG controls. Both are in the
> > v4l2-apps/util directory of the v4l-dvb repository.
>
> If just use "mplayer /dev/video0", do we still need v4l/v4l2 API for
> MPEG streaming device ?

Of course: you need it for the mpeg controls, for the 
brightness/contrast/etc stuff, and whatever else the device supports.

VIDIOC_ENCODER_CMD and VIDIOC_TRY_ENCODER_CMD can also be useful (it 
allows for more precise control over the mpeg stream).

You might also want to take a look at the VIDIOC_G_ENC_INDEX ioctl. This 
might not be supported by the device, but if it is then this is a nice 
one to have as well.

For debugging VIDIOC_LOG_STATUS has been very useful for me.

Regards,
(Continue reading)


Gmane