headers
Michael Krufky | 1 Oct 2007 05:00
Gravatar

Re: [PATCH] cx88-blackbird audio improvements (resend)

Ricardo Cerqueira wrote:
> On Sun, 2007-09-30 at 17:39 +0100, Ricardo Cerqueira wrote:
> [...]
>
>   
>> As Michael mentioned, one of the patches
>> causes new trouble (raw and mpeg used to work simultaneously, now they
>> don't; I can confirm that), so this still isn't ready to be merged into
>> the main tree.
>>     
>
> Scratch this; I can get raw and MPEG concurrently, if I start the analog
> first, and then the MPEG. If I do it the other way around, the MPEG
> freezes once the analog begins. It's probably something in the analog
> init...
>
> Michael, is this the behavior you get, or are you completely unable to
> get both working simultaneously?
In the master branch, I would usually first start a raw analog stream, 
then start a blackbird mpeg stream.  This does not work for me with 
Jelle's patches in my blackbird tree.  This seems quite strange -- the 
exact reverse of the problem that you are experiencing.

It's been well over a month or two since I tested that tree, and I am 
moving tomorrow morning...  I won't be able to conduct more blackbird 
tests for a week or two -- will have a LOT of unpacking to do before I 
find all of the relevant components.

You might also be interested in the regression in cx88-blackbird caused 
by Mauro's videobuf refactoring (not yet merged.... if interested, test
(Continue reading)

Permalink | Reply | 0 comments |
headers
Mauro Carvalho Chehab | 1 Oct 2007 02:45
Favicon

Re: MSI TV <at> nyware A/D

Hi Peter,

Em Qui, 2007-09-20 às 23:26 +0200, Peter Missel escreveu: 
> Greetings!
> 
> Am Donnerstag, 20. September 2007 22:58:30 schrieb Mauro Carvalho Chehab:
> > Hi Hermann,
> >
> > It seems that the board I've bought at Conrad.de has a different
> > subsystem than the LifeView FlyDVB-T Hybrid Cardbus (0x5168,0x3306). At
> > ML, somebody reported that it should be the same board.
> >
> > My board reports:
> >
> > saa7130/34: v4l2 driver version 0.2.14 loaded
> > saa7133[0]: found at 0000:03:00.0, rev: 209, irq: 9, latency: 64, mmio:
> > 0x38000000 saa7133[0]: subsystem: 4e42:3502, board: UNKNOWN/GENERIC
> 
> This is an OEM board then, not a LifeView branded one. All LifeView OEMs use 
> vendor ID 4E42h, boards are otherwise identical to the same device ID 
> under "LifeView branded" vendor ID 5168h.

> 3502h is the Cardbus Hybrid, 3306h is the PCI Hybrid. They are very likely to 
> be entirely compatible to each other; I'd simply point these two IDs to the 
> same card structure.

First of all, thanks for your help!

Sorry for the late answer. I'm too busy here trying to finish tm6000.
(Continue reading)

Permalink | Reply | 0 comments |
headers
Mauro Carvalho Chehab | 1 Oct 2007 11:37
Favicon

[GIT PATCHES] V4L/DVB update

Linus,

Please pull from:
        ssh://master.kernel.org/pub/scm/linux/kernel/git/mchehab/v4l-dvb.git master

For one bug fix at ivtv driver.

Cheers,
Mauro.

---

 drivers/media/video/ivtv/ivtv-fileops.c |    6 ++++--
 1 files changed, 4 insertions(+), 2 deletions(-)

Ian Armstrong (1):
      V4L/DVB (6052): ivtv: fix udma yuv bug

---------------------------------------------------
V4L/DVB development is hosted at http://linuxtv.org

--
video4linux-list mailing list
Unsubscribe mailto:video4linux-list-request <at> redhat.com?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/video4linux-list
Permalink | Reply | 0 comments |
headers
Tim Connors | 1 Oct 2007 14:39
Picon
Picon

AVermedia USB2.0 Hybrid+FM Volar (A828)

The AVermedia USB2.0 Hybrid+FM Volar (A828) comes with a dinky little 
proprietry decoder (version 0.07[1]) that doesn't really work with xawtv 
or mplayer or anything else, but does work with their crappy test apps.  
The driver comes with a statement that you shouldn't expect any more 
despite Avermedia's marketing claim that Linux supports the a828 (awfully 
tempted to go to Linus and ask him what he thinks of the trademark 
violation), because they have signed some NDAs.  Alas, their driver 
crashes my machine often enough to make it useless, so the a828 is a 
rather light paperweight that gets *very* hot in the 
tuning-before-crashing process.

All in all, not a great experience, but does anyone see any chance that 
this usb dongle can redeem itself and be made to work with a proper linux 
v4l driver to at least do the analogue TV and FM radio functions of its 
job?

Surely it can't be too different from any of the other Aver USB2.0 
products that apparently Just Work[TM].  There was some info on the chips 
in the device in this unanswered post: 
http://www.linuxtv.org/pipermail/linux-dvb/2007-January/015195.html

[1] 
http://www.avermedia.com/EN/default.aspx?TYPE=test.htm&PT=downloadD1&tv_TCAT_POS=0&CATNO0=D&IDX=2.1&CNT=1&CATNO1=D2&PID=471071067-1556&UCN=BAB4C

--

-- 
Tim Connors

--
video4linux-list mailing list
Unsubscribe mailto:video4linux-list-request <at> redhat.com?subject=unsubscribe
(Continue reading)

Permalink | Reply | 0 comments |
headers
Mauro Carvalho Chehab | 1 Oct 2007 15:04
Favicon

Re: [v4l-dvb-maintainer] [PATCH] V4L/DVB: Add support for Pinnacle Dazzle DVC 100

Hi Aurelien,

Since DVC90 and DVC100 have the same configurations, I would just add
the usb_device stuff and rename the board description, like:

	[EM2820_BOARD_PINNACLE_DVC_90] = {
		.name         = "Pinnacle Dazzle DVC 90/100",

and
 	{ USB_DEVICE(0x2304, 0x0208), .driver_info = EM2820_BOARD_PINNACLE_USB_2 },
 	{ USB_DEVICE(0x2040, 0x4200), .driver_info = EM2820_BOARD_HAUPPAUGE_WINTV_USB_2 },
 	{ USB_DEVICE(0x2304, 0x0207), .driver_info = EM2820_BOARD_PINNACLE_DVC_90 },
+	{ USB_DEVICE(0x2304, 0x021a), .driver_info = EM2820_BOARD_PINNACLE_DVC_90 },
 	{ },
 };
If later we discover some differences (like IR, for example), then we
can split it into two different entries.

Please, re-generate the patch for me to commit it.

Cheers,
Mauro

--
video4linux-list mailing list
Unsubscribe mailto:video4linux-list-request <at> redhat.com?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/video4linux-list
Permalink | Reply | 2 comments |
headers
Markus Rechberger | 1 Oct 2007 15:22
Picon

Re: [v4l-dvb-maintainer] [PATCH] V4L/DVB: Add support for Pinnacle Dazzle DVC 100

No need to regerenate the patch.
This patch has been added a long time ago to the driver which is still
beeing developed.

http://mcentral.de/hg/~mrec/em28xx-userspace2/file/5b9ef4278e69/em28xx-cards.c

     1939       { USB_DEVICE(0x2304, 0x0207), .driver_info =
EM2820_BOARD_PINNACLE_DVC_90 },

     1940       { USB_DEVICE(0x2304, 0x021a), .driver_info =
EM2820_BOARD_PINNACLE_DVC_100 },

http://mcentral.de/wiki/index.php/Em2880

So far I'm back from Copenhagen, and continuing the integration of
that driver :-)

Markus

On 10/1/07, Mauro Carvalho Chehab <mchehab <at> infradead.org> wrote:
> Hi Aurelien,
>
> Since DVC90 and DVC100 have the same configurations, I would just add
> the usb_device stuff and rename the board description, like:
>
> 	[EM2820_BOARD_PINNACLE_DVC_90] = {
> 		.name         = "Pinnacle Dazzle DVC 90/100",
>
> and
>  	{ USB_DEVICE(0x2304, 0x0208), .driver_info = EM2820_BOARD_PINNACLE_USB_2
(Continue reading)

Permalink | Reply | 1 comment |
headers
Mauro Carvalho Chehab | 1 Oct 2007 15:27
Favicon

Re: [v4l-dvb-maintainer] [PATCH] V4L/DVB: Add support for Pinnacle Dazzle DVC 100

Aurelien patch is for the in-kernel driver, not to an userspace one. I'm
willing to accept any patches for the in-kernel em28xx driver.

Cheers,
Mauro

--
video4linux-list mailing list
Unsubscribe mailto:video4linux-list-request <at> redhat.com?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/video4linux-list
Permalink | Reply | 0 comments |
headers
Chris Boyle | 1 Oct 2007 15:28

Conexant CX2388x Line In support?

I have a Hauppauge WinTV-PCI-FM with PCI IDs 14f1:8800 (rev 05) and
14f1:8811 (rev 05). I've been able to capture audio from it using
cx88-alsa, but it's just static, and I'm assuming it's from the analog
TV tuner of the device, which I'm not using (I'm using S-Video). The
device has a line in port, and I'm hoping I'm somehow able to capture
audio from that, but can't see any other ALSA source, nor module
parameter, nor any kind of audio source selection in the cx88 drivers.
Various searches have come up empty.

I did find linux/Documentation/video4linux/cx88/hauppauge-wintv-cx88-ir.txt
which seems to suggest Line-in is usable somehow:

> The controls for the mux are GPIO [0,1] for source, and GPIO 2 for muting.
>
> GPIO0  GPIO1
>   0        0    TV Audio
>   1        0    FM radio
>   0        1    Line-In
>   1        1    Mono tuner bypass or CD passthru (tuner specific)
>
> GPIO 16(i believe) is tied to the IR port (if present).

Unfortunately I don't know what's meant by GPIO here.

I'd appreciate a few pointers on what to look at to make this happen, as it
looks like it ought to be possible. I'm comfortable in C++ and have done a
little kernel work before, but don't know much about this level of
hardware.

Thanks,
(Continue reading)

Permalink | Reply | 501 comments |
headers
Trent Piepho | 1 Oct 2007 21:14
Picon

Re: Conexant CX2388x Line In support?

On Mon, 1 Oct 2007, Chris Boyle wrote:
> I have a Hauppauge WinTV-PCI-FM with PCI IDs 14f1:8800 (rev 05) and
> 14f1:8811 (rev 05). I've been able to capture audio from it using
> cx88-alsa, but it's just static, and I'm assuming it's from the analog
> TV tuner of the device, which I'm not using (I'm using S-Video). The
> device has a line in port, and I'm hoping I'm somehow able to capture
> audio from that, but can't see any other ALSA source, nor module
> parameter, nor any kind of audio source selection in the cx88 drivers.
> Various searches have come up empty.
>
> I did find linux/Documentation/video4linux/cx88/hauppauge-wintv-cx88-ir.txt
> which seems to suggest Line-in is usable somehow:

It could be the case that the line is is just a pass-through connection to
the line out.  The cx88 chip can't capture line level audio, only IF
signals from a tv or radio tuner.  So to capture from the line in, the card
would need an external ADC chip.  If your card has one, you should be able
to see it.

> > The controls for the mux are GPIO [0,1] for source, and GPIO 2 for muting.
> >
> > GPIO0  GPIO1
> >   0        0    TV Audio
> >   1        0    FM radio
> >   0        1    Line-In
> >   1        1    Mono tuner bypass or CD passthru (tuner specific)

This is probably a mux that controls the source connected to the line out.

--
(Continue reading)

Permalink | Reply | 501 comments |
headers
Markus Rechberger | 2 Oct 2007 00:26
Picon

Re: [v4l-dvb-maintainer] [PATCH] V4L/DVB: Add support for Pinnacle Dazzle DVC 100

Hi Aurelien,

well I still maintain that driver and continue development, I don't
want the inkernel driver having code which is not merged with the
other work anymore.
The reason is if this async way would continue I don't want to drag
code from one repository to another one.
I gave the possibility to merge the drivers, although I'm not looking
at solutions which will decrease the features of the driver, and those
comments that I should remove just a little to get the driver in as it
is is not right because some fundamental things are not solved and
some more specific details are not going to be implemented any time
soon into the inkernel driver or even API there.
Beside that I don't want to spend any further time in discussions,
interested people are welcome to get more information about some parts
by directly contacting me (contributions are welcome and discussions
which bring things forward too)

Markus

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

Gmane