public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Martin Samuelsson <sam@home.se>
To: linux-kernel@vger.kernel.org
Cc: "Andrew Morton" <akpm@osdl.org>,
	"Ronald S. Bultje" <rbultje@ronald.bitfreak.net>
Subject: AverMedia 6 Eyes AVS6EYES driver
Date: Mon, 27 Mar 2006 12:37:57 +0200	[thread overview]
Message-ID: <20060327123757.6e06cf8a.sam@home.se> (raw)

Hello again!

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.

It can be found at 

http://sam.kfib.org/sixeyes/linux-2.6.16-avs6eyes.diff

and weighs in at a respectable 46 kB.

I've tried to keep it as small as possible, but it does affect quite a number of things:

It adds a whole new driver, for the Conexant bt866 video encoder.
It imports an almost whole new driver, created within the Marvel project, for the Samsung ks0127 video decoder.
It modifies drivers/media/video/Kconfig,
            drivers/media/video/Makefile,
            drivers/media/video/zoran_card.c,
            drivers/media/video/zoran.h,
            Documentation/video4linux/Zoran
        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've stripped the ks0127 driver of all Marvel specific stuff, and reworked a few crucial functions to use stock kernel names for video modes and such things.

The diff is against the 2.6.16 tree, and considering its size and impact, it would probably be wise to let somebody with a little spare time take a look at it before inclusion.

I'd appreciate being kept in the recipient list in case of discussion.

Regards,
/Sam

             reply	other threads:[~2006-03-27 10:38 UTC|newest]

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

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