public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: Simon Farnsworth <simon.farnsworth@onelan.com>
To: Andy Walls <awalls@radix.net>
Cc: Hans de Goede <j.w.r.degoede@hhs.nl>,
	Linux Media Mailing List <linux-media@vger.kernel.org>
Subject: Re: libv4l2 and the Hauppauge HVR1600 (cx18 driver) not	working	well together
Date: Thu, 03 Sep 2009 12:44:21 +0100	[thread overview]
Message-ID: <4A9FAC15.9000002@onelan.com> (raw)
In-Reply-To: <1251977347.22279.21.camel@morgan.walls.org>

Andy Walls wrote:
> On Thu, 2009-09-03 at 12:23 +0100, Simon Farnsworth wrote:
>> Andy Walls wrote:
>>> But I suspect no user pays for the extra cost of the CX2341[568]
>>> hardware MPEG encoder, if the user primarily wants uncompressed YUV
>>> video as their main format.
>> Actually, we're doing exactly that. We want a PCI card from a reputable
>> manufacturer which provides uncompressed YUV and ATSC (both OTA and
>> ClearQAM cable). As we already buy Hauppauge HVR-1110s for DVB-T and
>> uncompressed analogue, a Hauppauge card suits us, and the only thing
>> they have that fits the needs is the HVR-1600; the MPEG encoder is thus
>> left idle.
> 
> Ah. OK, this is more than an academic exercise. :)
> 
> If you can prioritize your needs for the cx18 driver, I can see what I
> can get done.
> 
The video side is now working well for me on the HVR1110 and HVR1600 -
in an ideal world, I'd have an ALSA driver for cx18 audio instead of the
video24 device. The read() bug isn't major for me, as I can just use a
slightly modified libv4l2 to cope.

> If you'd like to submit patches, I'll be happy to review them to make
> sure they don't break anything and then get them integrated.
> 
I'll be discussing this with my management next week, and they'll be
making a judgement call on whether we can cope without analogue audio on
the RF input only. If we can't, I'll be tasked with working on this; I
take it you'd prefer to have ALSA added to the driver than for me to
teach Xine to read from /dev/video24 for PCM audio?

In any case, I have some more work to do on the reworked input_v4l for
Xine, as I need to get it into a state where I can work with the Xine
guys on merging it into their mainline. This will have to be finished
before I can really dive into the cx18 driver.
-- 
Thank you for the offer of help - I'll let you know if I'm going to
start working on ALSA support in cx18,

Simon Farnsworth


  reply	other threads:[~2009-09-03 11:44 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-02 16:32 libv4l2 and the Hauppauge HVR1600 (cx18 driver) not working well together Simon Farnsworth
2009-09-02 17:44 ` Hans de Goede
2009-09-03  9:17   ` Simon Farnsworth
2009-09-03  9:28     ` Hans de Goede
2009-09-03  9:44     ` Hans de Goede
2009-09-03 10:21       ` Simon Farnsworth
2009-09-03 10:37         ` Simon Farnsworth
2009-09-03 10:56           ` Simon Farnsworth
2009-09-03 11:16             ` Andy Walls
2009-09-03 11:20           ` Hans de Goede
2009-09-03 11:23             ` Andy Walls
2009-09-04  3:14             ` Andy Walls
2009-09-04  6:22               ` Hans de Goede
2009-09-03 11:13         ` Hans de Goede
2009-09-03 11:45     ` Hans de Goede
2009-09-03 11:06   ` Andy Walls
2009-09-03 11:23     ` Simon Farnsworth
2009-09-03 11:29       ` Andy Walls
2009-09-03 11:44         ` Simon Farnsworth [this message]
2009-09-03 23:34           ` Andy Walls

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=4A9FAC15.9000002@onelan.com \
    --to=simon.farnsworth@onelan.com \
    --cc=awalls@radix.net \
    --cc=j.w.r.degoede@hhs.nl \
    --cc=linux-media@vger.kernel.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