public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Ronald S. Bultje" <rbultje@ronald.bitfreak.net>
To: Andrew Morton <akpm@osdl.org>
Cc: linux-kernel@vger.kernel.org, Martin Samuelsson <sam@home.se>
Subject: Re: AverMedia 6 Eyes AVS6EYES driver
Date: Mon, 27 Mar 2006 09:52:28 -0500	[thread overview]
Message-ID: <1143471148.2912.6.camel@localhost.localdomain> (raw)
In-Reply-To: <20060327123757.6e06cf8a.sam@home.se>

Hi Andrew / all,

On Mon, 2006-03-27 at 12:37 +0200, Martin Samuelsson wrote:
> This time, I bring you a somewhat larger patch than the previous one.
> It adds support for the AverMedia AVS6EYES Zoran-based MJPEG card. And
> it's not base64 encoded. Sorry about that one.
[..]
> http://sam.kfib.org/sixeyes/linux-2.6.16-avs6eyes.diff
[..]
> It modifies drivers/media/video/Kconfig,
>             drivers/media/video/Makefile,
>             drivers/media/video/zoran_card.c,
>             drivers/media/video/zoran.h,
>             Documentation/video4linux/Zoran

I've reviewed those modifications, along with the new i2c modules
(ks0127 and bt866), and they're all up-to-standard. I recommend that
those patches be applied to the kernel tree. With those patches, a new
type of card will be supported in the kernel driver.

>         and include/linux/i2c-id.h
> The latter defines two experimental I2C_DRIVERIDs; not suited for real
> usage, but I'm not sure about how to obtain official ones.

(I think people commonly just append their IDs to the list at the bottom
of i2c-id.h, incrementally; at least, that's what I did when I submitted
earlier patches.)

Cheers,
Ronald


      reply	other threads:[~2006-03-27 14:58 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-27 10:37 AverMedia 6 Eyes AVS6EYES driver Martin Samuelsson
2006-03-27 14:52 ` Ronald S. Bultje [this message]

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=1143471148.2912.6.camel@localhost.localdomain \
    --to=rbultje@ronald.bitfreak.net \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sam@home.se \
    /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