public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: "Matthias Weißer" <weisserm@arcor.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 2/3] video: add support for display controller in MB86R0x SoCs
Date: Wed, 28 Apr 2010 10:08:21 +0200	[thread overview]
Message-ID: <4BD7ECF5.7070707@arcor.de> (raw)
In-Reply-To: <20100428064421.C31B5AFC6AC@gemini.denx.de>

Am 28.04.2010 08:44, schrieb Wolfgang Denk:
> Dear Matthias,

>
> in message<4BD7D5DD.6080701@arcor.de>  you wrote:
>>
>>>> +	pGD->memSize = VIDEO_MEM_SIZE;
>>>> +	pGD->frameAdrs = PHYS_SDRAM + PHYS_SDRAM_SIZE - VIDEO_MEM_SIZE;
>>>
>>> Please pay attention to the global memory map requirements. PRAM might
>>> go first.
>>
>> Can you please explain this a bit more in detail? I checked the source
>> and README for CONFIG_PRAM and it seems to be reserving some space at
>> the end of RAM. But I have only found reference to it in ppc and m68k code.
>
> Right. But there is a chance that the ARM implementation might be
> reworked soon, and then it will follow the documented approach as
> well, so better start correctly from the beginning so you don;t run
> into conflicts soon.

I totally agree with you, but...

>> What would be the correct way to reserve some 2MB-4MB at the end of
>> system RAM as a framebuffer for the integrated graphics device?
>
> See the PPC implementation for reference.

I had a look into the PPC code and its clear to me how it is done there. 
But I currently do not see how this can be done on ARM without a couple 
of changes to arch/arm/lib/board.c

Another question regarding the video driver:
I have seen some video drivers in driver/video/... and some are in 
arch/.../cpu/...

What would be the right place for mine? As it is integrated into the SoC 
I tend to put it in arch/arm/cpu/arm/arm926ejs/mb86r0x and not into 
drivers/video. On the other hand there is a imx31 related video driver 
in drivers/video.

Thanks for you patience
Matthias

  reply	other threads:[~2010-04-28  8:08 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-22 10:30 [U-Boot] [PATCH 0/3] Add support for MB86R0x SoCs Matthias Weisser
2010-04-22 10:30 ` [U-Boot] [PATCH 1/3] arm: " Matthias Weisser
2010-04-22 10:30   ` [U-Boot] [PATCH 2/3] video: add support for display controller in " Matthias Weisser
2010-04-22 10:30     ` [U-Boot] [PATCH 3/3] arm: Add support for jadecpu board based on MB86R01 SoC Matthias Weisser
2010-04-22 12:51       ` Wolfgang Denk
2010-04-22 13:17         ` Matthias Weißer
2010-04-22 14:13           ` Wolfgang Denk
2010-05-03 11:38         ` Matthias Weißer
2010-05-03 12:28           ` Wolfgang Denk
2010-04-22 12:41     ` [U-Boot] [PATCH 2/3] video: add support for display controller in MB86R0x SoCs Wolfgang Denk
2010-04-22 13:03       ` Matthias Weißer
2010-05-01 18:51         ` Anatolij Gustschin
2010-05-01 19:05         ` [U-Boot] [PATCH] video: cfb_console: add weak default video_set_lut() Anatolij Gustschin
2010-06-12  8:20           ` [U-Boot] [PATCH v2] " Anatolij Gustschin
2010-06-12  8:35             ` Anatolij Gustschin
2010-04-28  6:29       ` [U-Boot] [PATCH 2/3] video: add support for display controller in MB86R0x SoCs Matthias Weißer
2010-04-28  6:44         ` Wolfgang Denk
2010-04-28  8:08           ` Matthias Weißer [this message]
2010-05-01 18:46     ` Anatolij Gustschin
2010-04-22 12:34   ` [U-Boot] [PATCH 1/3] arm: Add support for " Wolfgang Denk
2010-04-26  6:55     ` Matthias Weißer
2010-05-04 22:18       ` Wolfgang Denk

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=4BD7ECF5.7070707@arcor.de \
    --to=weisserm@arcor.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