From: Anatolij Gustschin <agust@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] video: cfb_console: flush dcache for frame buffer in DRAM
Date: Mon, 30 Apr 2012 18:26:57 +0200 [thread overview]
Message-ID: <20120430182657.1dbf61a7@wker> (raw)
In-Reply-To: <CAPnjgZ2RgOj7BL49-k-k=KVNcONDdmKEZ=ZA-ALcqf04o39HyQ@mail.gmail.com>
Hi Simon,
On Sun, 29 Apr 2012 22:56:01 -0700
Simon Glass <sjg@chromium.org> wrote:
...
> Regarding this patch, can I suggest also looking at this possibly more
> generic patch that I originally did for Tegra? The series is here:
>
> http://patchwork.ozlabs.org/user/bundle/2869/
>
> and in particular these patches from the series:
>
> arm: Add control over cachability of memory regions
> lcd: Add CONFIG_ALIGN_LCD_TO_SECTION to align lcd for MMU
> lcd: Add support for flushing LCD fb from dcache after update
> tegra: Align LCD frame buffer to section boundary
> tegra: Support control of cache settings for LCD
> tegra: fdt: Add LCD definitions for Seaboard
> lcd: Add CONSOLE_SCROLL_LINES option to speed console
Thanks for the reminder, I completely forgot about these LCD patches.
I'll look at them soon.
Thanks,
Anatolij
next prev parent reply other threads:[~2012-04-30 16:26 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-28 15:04 [U-Boot] [PATCH] video: cfb_console: flush dcache for frame buffer in DRAM Anatolij Gustschin
2012-04-28 15:58 ` Pali Rohár
2012-04-28 18:16 ` Mike Frysinger
2012-04-30 15:32 ` Anatolij Gustschin
2012-05-01 4:14 ` Mike Frysinger
2012-04-30 2:25 ` Marek Vasut
2012-04-30 5:56 ` Simon Glass
2012-04-30 16:26 ` Anatolij Gustschin [this message]
2012-04-30 15:19 ` Anatolij Gustschin
2012-04-30 15:21 ` Marek Vasut
2012-04-30 15:27 ` Anatolij Gustschin
2012-04-30 15:57 ` Marek Vasut
2012-06-05 7:28 ` Anatolij Gustschin
2012-07-19 13:26 ` Mike Frysinger
2012-07-19 15:49 ` Marek Vasut
2012-07-19 16:51 ` Mike Frysinger
-- strict thread matches above, loose matches on Subject: below --
2012-09-18 2:49 Eric Nelson
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=20120430182657.1dbf61a7@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