From: Anatolij Gustschin <agust@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 0/2] omap_dss: add optional 32bit XXRRGGBB framebuffer
Date: Fri, 18 May 2012 23:22:34 +0200 [thread overview]
Message-ID: <20120518232234.1a6351b7@wker> (raw)
In-Reply-To: <1337195098-14015-1-git-send-email-jeroen@myspectrum.nl>
Hi,
On Wed, 16 May 2012 21:04:56 +0200
Jeroen Hofstee <jeroen@myspectrum.nl> wrote:
> I could not resist removing some brackets etc while looking at the file..
> These changes are optional and in a seperate patch. I will email a
> seperate patch which I use for testing, but should NOT be in mainline,
> since it assumes which LCD is connected.
>
> Beagle owners, please test that I didn't break your orange background;
> I don't have the board.
I used similar patches on beagleboard when debugging cfb console output
on omap3 and will test your patches soon. You also might need this [1]
patch.
Thanks,
Anatolij
[1] http://patchwork.ozlabs.org/patch/155662/
next prev parent reply other threads:[~2012-05-18 21:22 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-16 19:04 [U-Boot] [PATCH 0/2] omap_dss: add optional 32bit XXRRGGBB framebuffer Jeroen Hofstee
2012-05-16 19:04 ` [U-Boot] [PATCH 1/2] omap3_dss: add optional framebuffer Jeroen Hofstee
2012-05-16 19:04 ` [U-Boot] [PATCH 2/2] omap3_dss: cosmetic changes Jeroen Hofstee
2012-05-16 19:40 ` [U-Boot] [PATCH 0/2] omap_dss: add optional 32bit XXRRGGBB framebuffer Jeroen Hofstee
2012-05-18 10:50 ` [U-Boot] [PATCH v2 " Jeroen Hofstee
2012-05-18 10:51 ` [U-Boot] [PATCH v2 1/2] omap3_dss: add optional framebuffer Jeroen Hofstee
2012-05-25 13:51 ` Anatolij Gustschin
2012-05-18 10:51 ` [U-Boot] [PATCH v2 2/2] omap3_dss: cosmetic changes Jeroen Hofstee
2012-05-25 13:54 ` Anatolij Gustschin
2012-05-25 14:44 ` Tom Rini
2012-05-24 19:17 ` [U-Boot] [PATCH v2 0/2] omap_dss: add optional 32bit XXRRGGBB framebuffer Tom Rini
2012-05-18 21:22 ` Anatolij Gustschin [this message]
2012-05-18 21:47 ` [U-Boot] [PATCH " Jeroen Hofstee
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=20120518232234.1a6351b7@wker \
--to=agust@denx.de \
--cc=u-boot@lists.denx.de \
/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