From: "Antonino A. Daplas" <adaplas@gmail.com>
To: Krzysztof Helt <krzysztof.h1@gmail.com>
Cc: linux-fbdev-devel@lists.sourceforge.net
Subject: Re: [PATCH] s3c2410fb: byte ordering fixes
Date: Sat, 15 Sep 2007 08:17:30 +0800 [thread overview]
Message-ID: <1189815450.8660.4.camel@daplas> (raw)
In-Reply-To: <20070909112828.0bd6427a.krzysztof.h1@gmail.com>
On Sun, 2007-09-09 at 11:28 +0200, Krzysztof Helt wrote:
> On Tue, 14 Aug 2007 18:26:38 +0200
> "Krzysztof Helt" <krzysztof.h1@wp.pl> wrote:
>
> > From: Krzysztof Helt <krzysztof.h1@wp.pl>
> >
> > This patch sets correct bits related to the byte ordering
> > of the framebuffer. This was tested on little endian kernel
> > only. The big endian kernel may require different settings.
> >
> > The patch also adds 32 bpp mode which is called 24 bpp by
> > Samsung. One pixel takes 32 bits but only 24 bits are used
> > in this mode.
> >
>
> Tony,
>
> This patch didn't make into the -mm tree with other s3c2410fb patches.
> Please look into it.
Sorry, I was a bit busy for the last couple of weeks so I wasn't able to
send your patches until now.
Anyway, what s3c2410fb patches did not make it to the -mm tree?
Tony
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
next prev parent reply other threads:[~2007-09-15 0:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-14 16:26 [PATCH] s3c2410fb: byte ordering fixes Krzysztof Helt
2007-09-09 9:28 ` Krzysztof Helt
2007-09-15 0:17 ` Antonino A. Daplas [this message]
2007-09-15 5:52 ` Krzysztof Helt
2007-09-15 23:17 ` Antonino A. Daplas
-- strict thread matches above, loose matches on Subject: below --
2007-09-15 23:22 Antonino A. Daplas
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=1189815450.8660.4.camel@daplas \
--to=adaplas@gmail.com \
--cc=krzysztof.h1@gmail.com \
--cc=linux-fbdev-devel@lists.sourceforge.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).