All of lore.kernel.org
 help / color / mirror / Atom feed
From: Wolfgang Denk <wd@denx.de>
To: Dan Malek <dan@mvista.com>
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: 8260 console problems
Date: Fri, 23 Feb 2001 02:18:16 +0100	[thread overview]
Message-ID: <20010223011822.EBA86287E8@denx.denx.de> (raw)
In-Reply-To: Your message of "Thu, 22 Feb 2001 18:51:20 EST." <3A95A5F8.DF6FB60B@mvista.com>


In message <3A95A5F8.DF6FB60B@mvista.com> you wrote:
>
> The code in the mbxboot directory is also used by (many) people
> that flash the kernel and initrd into rom.  One of the nice things
> about this code is you can boot an image over a network for testing,
> and then flash the identical compressed bits when you get it working.

Yes, that's what we do with PPCBoot, too. You don't need the  mbxboot
stuff for this.

> > Is there a good, urgent reason to _change_ the current state?
>
> When I get a chance to step back and take a breath from the recent
> set of merges (yours are in the pipeline now :-), the bd_info stuff
> is going to disappear and follow the new boot record method used by
> other PPC booters.  That is the first major step to removing the whole
> variety of different boot loaders.

Seems I'm missing a bit of information here. Which "new  boot  record
method"  are you talking about? Where are things like this discussed?
Is there any documentation available?


> > Right now the "kernel interface" is pretty well  defined  (starts  at
> > address  0,  r3: ptr to bd_info, r4: start of initrd or 0, r5: end of
> > initrd, r6: start of command line, r7: end of command line). What are
> > you going to change, and why?
>
> No one but 8xx uses that calling convention anymore.  To standardize

Really? Isn't this still in use on 4xx, 8xx, and  PREP?  Ummm...  I'm
talking about 2.4.0 here; has this been changed sice?

> new boot record method.  Regardless of how a board and boot rom store
> and provide information, the code in the "boot" directory collects
> this into a standard format and presents it to the kernel.

That's OK for all those boards that come with  any  usable  firmware;
some  others  will be using PPCBoot, and it is our intention that you
don't need any additional "glue" layer when booting with PPCBoot.

Wolfgang Denk

--
Software Engineering:  Embedded and Realtime Systems,  Embedded Linux
Phone: (+49)-8142-4596-87  Fax: (+49)-8142-4596-88  Email: wd@denx.de
Remember that Beethoven wrote his first symphony in C ...

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

       reply	other threads:[~2001-02-23  1:18 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <3A95A5F8.DF6FB60B@mvista.com>
2001-02-23  1:18 ` Wolfgang Denk [this message]
2001-02-23 12:10 ` 8260 console problems Murray Jensen
     [not found] <3A95783C.6618E177@mvista.com>
2001-02-22 21:45 ` Wolfgang Denk
2001-02-22  5:18 jtm
2001-02-22  8:23 ` Wolfgang Denk
2001-02-22 12:38   ` jtm
2001-02-22 14:34   ` jtm
2001-02-22 15:02     ` Wolfgang Denk
2001-02-22 19:13   ` Dan Malek
2001-02-22 19:24     ` Wolfgang Denk
2001-02-22 20:42     ` jtm

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=20010223011822.EBA86287E8@denx.denx.de \
    --to=wd@denx.de \
    --cc=dan@mvista.com \
    --cc=linuxppc-embedded@lists.linuxppc.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.