From: Rodolfo Giometti <giometti@enneenne.com>
To: Richard Purdie <rpurdie@rpsys.net>
Cc: linux-arm-kernel@lists.arm.linux.org.uk,
linux-fbdev-devel@lists.sourceforge.net,
linux-kernel@vger.kernel.org, Paul Sokolovsky <pmiscml@gmail.com>
Subject: Re: [PATCH 1/1] PXAFB: Support for backlight control
Date: Thu, 22 Feb 2007 09:28:49 +0100 [thread overview]
Message-ID: <20070222082848.GM4641@enneenne.com> (raw)
In-Reply-To: <1172105946.5790.78.camel@localhost.localdomain>
On Thu, Feb 22, 2007 at 12:59:06AM +0000, Richard Purdie wrote:
>
> Reading through the patch its:
>
> 1) Not against any mainline kernel
> 2) Not against a recent kernel
I'm sorry, but the patch applay against the latest kernel. Please, try
it.
> There were a number of backlight class changes just merged into mainline
> and you need to sync up any patch against them.
My patch uses current backlight class support in the kernel.
> As mentioned by others, there is no need to tie the backlight driver
> into the framebuffer any more. Have a look at
> drivers/video/backlight/corgi_bl.c for an example (its used by PXA
> devices).
That driver uses the backlight class support as my patch does into
pxafb.
> I have said elsewhere I will take patches to make corgi_bl a more
> generic driver (or maybe create a simple generic backlight driver) along
> the lines of what Paul mentioned.
I see.
I suppose you are the backlight support mantainer, so what do you
suggest to do to "make corgi_bl a more generic driver"?
I have to rename and modify it? Or just copy it to have backward
compatibility and the modify the new file?
I should mv backlight directory from the video one?
Thanks for your suggestions,
Rodolfo
--
GNU/Linux Solutions e-mail: giometti@enneenne.com
Linux Device Driver giometti@gnudd.com
Embedded Systems giometti@linux.it
UNIX programming phone: +39 349 2432127
next prev parent reply other threads:[~2007-02-22 8:28 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-21 14:53 [PATCH 1/1] PXAFB: Support for backlight control Rodolfo Giometti
2007-02-21 16:00 ` Paul Sokolovsky
2007-02-21 16:12 ` Rodolfo Giometti
2007-02-21 16:26 ` Paul Sokolovsky
2007-02-22 8:32 ` Rodolfo Giometti
2007-02-22 10:33 ` Paul Sokolovsky
2007-02-22 16:37 ` Rodolfo Giometti
2007-02-22 17:11 ` Richard Purdie
2007-02-28 16:54 ` [Linux-fbdev-devel] " James Simmons
2007-02-22 0:59 ` Richard Purdie
2007-02-22 8:28 ` Rodolfo Giometti [this message]
2007-02-22 9:27 ` Richard Purdie
2007-02-22 9:32 ` Rodolfo Giometti
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=20070222082848.GM4641@enneenne.com \
--to=giometti@enneenne.com \
--cc=linux-arm-kernel@lists.arm.linux.org.uk \
--cc=linux-fbdev-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=pmiscml@gmail.com \
--cc=rpurdie@rpsys.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;
as well as URLs for NNTP newsgroup(s).