public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Jeroen Hofstee <jeroen@myspectrum.nl>
To: u-boot@lists.denx.de
Subject: [U-Boot] [RFC]: always relocate u-boot before the framebuffer
Date: Sat, 05 Jan 2013 11:07:33 +0100	[thread overview]
Message-ID: <50E7FB65.9000709@myspectrum.nl> (raw)
In-Reply-To: <20130103202832.A80862007A4@gemini.denx.de>

Hi,

On 01/03/2013 09:28 PM, Wolfgang Denk wrote:
> Hm... I'm not sure if this is the right approach, then.  If mainline
> Linux insists on such a 2 MB alignment, we shoud  rather teach
> lcd_setmem() to follow tha rule, too.  That should solve the problem
> as well (and probably more efficiently, especially if other features
> like pRAM or shared log buffer reserve high memory as well).
>
I just noticed this is already possible since the recently introduced
dcache for lcd.c also adds a CONFIG_LCD_ALIGNMENT. Since I am at
rc2 I had not seen it yet.

Regards,
Jeroen

  parent reply	other threads:[~2013-01-05 10:07 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-29 19:31 [U-Boot] [RFC]: always relocate u-boot before the framebuffer Jeroen Hofstee
2012-12-29 20:10 ` Jeroen Hofstee
2012-12-29 21:50   ` Wolfgang Denk
2012-12-29 21:47 ` Wolfgang Denk
2012-12-31 14:33 ` Lukasz Majewski
2012-12-31 14:54   ` Wolfgang Denk
2013-01-02 15:48     ` Tom Rini
2013-01-02 20:17       ` Wolfgang Denk
2013-01-03 10:27         ` Jeroen Hofstee
2013-01-03 10:41           ` Wolfgang Denk
2013-01-03 18:10             ` Jeroen Hofstee
2013-01-03 20:28               ` Wolfgang Denk
2013-01-04 20:29                 ` Jeroen Hofstee
2013-01-05 10:07                 ` Jeroen Hofstee [this message]
2013-01-05 19:18                   ` Wolfgang Denk
2013-01-03 10:43         ` [U-Boot] [PATCH v2] VIDEO: better document the correct use of CONFIG_FB_ADDR Wolfgang Denk
2013-01-14 19:29           ` Anatolij Gustschin

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=50E7FB65.9000709@myspectrum.nl \
    --to=jeroen@myspectrum.nl \
    --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