From: Wolfgang Denk <wd@denx.de>
To: Dan Malek <dan@mvista.com>
Cc: jtm@smoothsmoothie.com, linuxppc-embedded@lists.linuxppc.org
Subject: Re: 8260 console problems
Date: Thu, 22 Feb 2001 22:45:56 +0100 [thread overview]
Message-ID: <20010222214601.5A173287E8@denx.denx.de> (raw)
In-Reply-To: Your message of "Thu, 22 Feb 2001 15:36:12 EST." <3A95783C.6618E177@mvista.com>
In message <3A95783C.6618E177@mvista.com> Dan Malek wrote:
>
> > PPCBoot does not use _anything_ from the stuff in arch/ppc/mbxboot/
>
> I'm not sure that is such a good idea.......I'm assuming code from
IMHO the code in that directory is things that shoud be done by
firmware in the frist place. In my experience, a lot significant
amount of work to get Linux running on a new board dealt with that
stuff. This pain is gone since we use PPCBoot on all systems.
Why do I have to add another serial driver for a console interface,
when the firmware already has one? Why add uncompression code (to
each kernel image!) when we can have this in a central location - in
the firmware. Etc. etc.
> that directory is run when I am writing low level kernel code. You
> are going to constantly be updating PPCBoot, and finding that older
Ummm... Why don't _you_ switch to PPCBoot then? I would certainly
appreciate your halp there...
> versions aren't going to support new kernels. That code has to be
> run, makes assumptions about the MMU and cache states upon entry,
Is there a good, urgent reason to _change_ the current state?
> and at most expects a bd_info structure from the boot rom.
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?
Wolfgang Denk
--
Software Engineering: Embedded and Realtime Systems, Embedded Linux
Phone: (+49)-8142-4596-87 Fax: (+49)-8142-4596-88 Email: wd@denx.de
The light at the end of the tunnel is usually a "No Exit" sign.
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next parent reply other threads:[~2001-02-22 21:45 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3A95783C.6618E177@mvista.com>
2001-02-22 21:45 ` Wolfgang Denk [this message]
[not found] <3A95A5F8.DF6FB60B@mvista.com>
2001-02-23 1:18 ` 8260 console problems Wolfgang Denk
2001-02-23 12:10 ` Murray Jensen
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=20010222214601.5A173287E8@denx.denx.de \
--to=wd@denx.de \
--cc=dan@mvista.com \
--cc=jtm@smoothsmoothie.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 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).