public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Stephan Linz <linz@li-pro.net>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 3/4] microblaze: enable LMB support
Date: Tue, 22 Jun 2010 11:46:23 +0200	[thread overview]
Message-ID: <201006221146.23964.linz@li-pro.net> (raw)
In-Reply-To: <4C206538.4060800@monstr.eu>

Am Dienstag, 22. Juni 2010 09:24:40 schrieb Michal Simek:
> Stephan Linz wrote:
> > Foresighted to support flat device tree realocations we need to use
> > the new Logical memory blocks library in a manner as been used by all
> > other architectures.
> >
> > Signed-off-by: Stephan Linz <linz@li-pro.net>
> > ---
> >  arch/microblaze/include/asm/config.h |    2 ++
> >  1 files changed, 2 insertions(+), 0 deletions(-)
> >
> > diff --git a/arch/microblaze/include/asm/config.h
> > b/arch/microblaze/include/asm/config.h index 8a9064b..ec2c316 100644
> > --- a/arch/microblaze/include/asm/config.h
> > +++ b/arch/microblaze/include/asm/config.h
> > @@ -21,6 +21,8 @@
> >  #ifndef _ASM_CONFIG_H_
> >  #define _ASM_CONFIG_H_
> >
> > +#define CONFIG_LMB
> > +
>
> I see what you are trying to do but what
> is your point with enabling LMB support ?

Hm, mainly a clean compilation. Without this define I can not enable the flat 
device tree handling. LMB is quite new in U-Boot (PowerPC) and there are some 
dependencies to the FDT support. That force to enable even this feature on 
MicroBlaze too. I want to avoid a deep intrusion into the code.

>
> I am not sure if this enabling bring us any feature which we need.

Hm, could you pleace consult the PowerPC folks? I think LMB is used to 
transfer system memory map from U-Boot to Linux kernel in a common way 
(similar like on x86 PC from BIOS to kernel), or not? Any comments?

br,
Stephan

>
> Thanks,
> Michal

-- 
Viele Gr??e,
Stephan Linz
______________________________________________________________________________
OpenDCC: http://www.li-pro.net/opendcc.phtml
PC/M: http://www.li-pro.net/pcm.phtml
CDK4AVR: http://cdk4avr.sourceforge.net/
CDK4NIOS: http://cdk4nios.sourceforge.net/
CDK4MSP: http://cdk4msp.sourceforge.net/
CPM4L: http://download.opensuse.org/repositories/home:/rexut:/CPM4L

  reply	other threads:[~2010-06-22  9:46 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-21 20:58 [U-Boot] [PATCH 1/4] microblaze: generic: adding DHCP support Stephan Linz
2010-06-21 20:58 ` [U-Boot] [PATCH 2/4] microblaze: generic: rename MTD partition set to 'flash-0' Stephan Linz
2010-06-21 20:58   ` [U-Boot] [PATCH 3/4] microblaze: enable LMB support Stephan Linz
2010-06-21 20:58     ` [U-Boot] [PATCH 4/4] microblaze: generic: enable FDT support Stephan Linz
2010-06-22  7:25       ` Michal Simek
2010-06-22  9:30         ` Stephan Linz
2010-06-23  6:27           ` Michal Simek
2010-06-24  6:15             ` Stephan Linz
2010-06-22  7:24     ` [U-Boot] [PATCH 3/4] microblaze: enable LMB support Michal Simek
2010-06-22  9:46       ` Stephan Linz [this message]
2010-06-23  6:31         ` Michal Simek
2010-06-25 14:37           ` Stephan Linz
2010-06-22  7:26   ` [U-Boot] [PATCH 2/4] microblaze: generic: rename MTD partition set to 'flash-0' Michal Simek
2010-06-21 21:21 ` [U-Boot] [PATCH 1/4] microblaze: generic: adding DHCP support Mike Frysinger
2010-06-21 21:55   ` Stephan Linz
2010-06-22  7:27 ` Michal Simek

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=201006221146.23964.linz@li-pro.net \
    --to=linz@li-pro.net \
    --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