From: Steven Toth <stoth@kernellabs.com>
To: Michael <auslands-kv@gmx.de>
Cc: linux-media@vger.kernel.org
Subject: Re: cx23885
Date: Mon, 15 Feb 2010 18:00:51 -0500 [thread overview]
Message-ID: <4B79D223.4010909@kernellabs.com> (raw)
In-Reply-To: <hlcjfi$unq$1@ger.gmane.org>
On 2/15/10 5:56 PM, Michael wrote:
> Well, this did not work. The cx23885 driver was not included in kernel
> 2.6.21, so no diff. The diff of the 2.6.21 cx25840 is twice as big as the
> 2.6.31 diff. :-(
>
> If anybody can give me a hint, what to include in a patch and what was old
> stuff that has jsut changed in 2.6.31, I'd be grateful.
>
> Attached is the diff of cx23885, the commell version against kernel
> 2.6.31.4.
>
>>
>> I'm downloading kernel 2.6.21 now and make a diff with these drivers.
>>
Start by patching the current cx23885 driver with all of the switch statements
related to the new board CX23885_BOARD_MPX885.
-cards.c -core.c etc.
I already see some issues in their MPX885 additions, driving wrong gpios and
assuming the encoder is attached - but it's a good start.
--
Steven Toth - Kernel Labs
http://www.kernellabs.com
+1.646.355.8490
next prev parent reply other threads:[~2010-02-15 23:00 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-15 12:20 cx23885 Michael
2010-02-15 12:54 ` cx23885 Andy Walls
2010-02-15 13:15 ` cx23885 Michael
2010-02-15 14:41 ` cx23885 Steven Toth
2010-02-15 15:21 ` cx23885 Michael
2010-02-15 17:11 ` cx23885 Steven Toth
2010-02-15 20:41 ` cx23885 Michael
2010-02-15 20:53 ` cx23885 Steven Toth
2010-02-15 22:17 ` cx23885 Michael
2010-02-15 22:20 ` cx23885 Steven Toth
2010-02-16 11:37 ` cx23885 Michael
2010-02-15 22:47 ` cx23885 Michael
2010-02-15 22:56 ` cx23885 Michael
2010-02-15 23:00 ` Steven Toth [this message]
2010-02-15 23:22 ` cx23885 Ralph Siemsen
2010-02-16 0:36 ` cx23885 Andy Walls
2010-02-15 22:58 ` cx23885 Michael
2010-02-15 17:27 ` cx23885 Devin Heitmueller
2010-02-15 20:29 ` cx23885 Michael
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=4B79D223.4010909@kernellabs.com \
--to=stoth@kernellabs.com \
--cc=auslands-kv@gmx.de \
--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