All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mauro Carvalho Chehab <mchehab@infradead.org>
To: Jon Smirl <jonsmirl@gmail.com>
Cc: lkml <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Kconfig for radio cards to allow VIDEO_V4L1_COMPAT
Date: Mon, 26 Jun 2006 16:00:03 -0300	[thread overview]
Message-ID: <1151348403.16290.5.camel@praia> (raw)
In-Reply-To: <9e4733910606261015l13399f96hebebeb00b6b01790@mail.gmail.com>

Em Seg, 2006-06-26 às 13:15 -0400, Jon Smirl escreveu:
> On 6/26/06, Mauro Carvalho Chehab <mchehab@infradead.org> wrote:

> I don't have any of the hardware. I was just doing some work on
> Kconfig and noticed that a bunch of drivers had gone missing. I see
> now that a lot of the drivers in media/video have the same problem.
Yes, mostly webcam stuff, where there are active developers. Hopefully
those stuff will be fixed in time to 2.6.19.
> I guess V4L1 is going to be with us for a while longer since all of
> these drivers need to get ported.
Radio devices will be more complicated to test. Those devices emerged a
long time ago, and it seems that nobody is using they, at least with 2.6
series. I'm not sure if it would be valuable to port all those stuff.
Some devices even don't have pnp support (you need to specify IO ports
and IRQ lines).
> 
Cheers, 
Mauro.


  reply	other threads:[~2006-06-26 19:00 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-25 17:40 [PATCH] Kconfig for radio cards to allow VIDEO_V4L1_COMPAT Jon Smirl
2006-06-25 18:21 ` Sam Ravnborg
2006-06-25 19:48   ` Jon Smirl
2006-06-26 13:06 ` Mauro Carvalho Chehab
2006-06-26 15:55   ` Jon Smirl
2006-06-26 16:58     ` Mauro Carvalho Chehab
2006-06-26 17:15       ` Jon Smirl
2006-06-26 19:00         ` Mauro Carvalho Chehab [this message]
2006-07-30 23:40       ` Alan Cox
2006-07-31 21:28         ` Mauro Carvalho Chehab
2006-07-31 23:36           ` Alan Cox
2006-08-01 15:46           ` PATCH: Convert usb fm radio to V4L2 and move to the right directory Alan Cox

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=1151348403.16290.5.camel@praia \
    --to=mchehab@infradead.org \
    --cc=jonsmirl@gmail.com \
    --cc=linux-kernel@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 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.