linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Eugene Surovegin <ebs@ebshome.net>
To: Li Yang-r58472 <LeoLi@freescale.com>
Cc: Linux PPC Embedded list <linuxppc-embedded@ozlabs.org>
Subject: Re: Problem running Linux 2.6.11 on MPC8272ADS
Date: Thu, 31 Mar 2005 03:17:19 -0800	[thread overview]
Message-ID: <20050331111718.GA31467@gate.ebshome.net> (raw)
In-Reply-To: <9FCDBA58F226D911B202000BDBAD46730117355F@zch01exm40.ap.freescale.net>

On Thu, Mar 31, 2005 at 04:22:26PM +0800, Li Yang-r58472 wrote:
> Good point.
> There is also IMMR need to be passed from bootloader to kernel.  We 
> can make more use of the u-boot bd_info mechanism.  But it binds ppc 
> linux to u-boot boot loader.  I don't know if we should make it a 
> porting convention.

Well, immr is _already_ part of bd_t passed from U-Boot! I was 
surprised that none of board ports (some of which are made for U-Boot 
only) use this. 

In 8248 based board port I'm working on right now, I already defined 
CPM_MAP_ADDR as follows:

#define CPM_MAP_ADDR            (((bd_t*)__res)->bi_immr_base)

--
Eugene

  reply	other threads:[~2005-03-31 11:17 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-31  8:22 Problem running Linux 2.6.11 on MPC8272ADS Li Yang-r58472
2005-03-31 11:17 ` Eugene Surovegin [this message]
2005-03-31 15:36 ` Jon Loeliger
  -- strict thread matches above, loose matches on Subject: below --
2005-03-31  3:03 Li Yang-r58472
2005-03-31  3:26 ` Eugene Surovegin
2005-03-29  6:29 Bastos Fernandez Alexandre
2005-03-29 15:44 ` Walter L. Wimer III
     [not found]   ` <424A60E1.4080802@compulab.co.il>
2005-03-30 16:00     ` Walter L. Wimer III
2005-03-30 17:42       ` Kumar Gala
2005-03-27  9:31 Mike Rapoport
2005-03-28 16:06 ` Walter L. Wimer III
2005-03-28 16:21   ` Kumar Gala
2005-03-28 16:24     ` Walter L. Wimer III

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=20050331111718.GA31467@gate.ebshome.net \
    --to=ebs@ebshome.net \
    --cc=LeoLi@freescale.com \
    --cc=linuxppc-embedded@ozlabs.org \
    /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;
as well as URLs for NNTP newsgroup(s).