From: Dan Malek <dan@netx4.com>
To: Jason Wohlgemuth <jsw-embedded@mindspring.com>
Cc: Dan Malek <dan@netx4.com>,
mporter@mvista.com, tjroberts@lucent.com,
linuxppc-embedded@lists.linuxppc.org
Subject: Re: QUERY: Embedded PowerPC Linux?
Date: Wed, 24 May 2000 21:54:10 -0400 [thread overview]
Message-ID: <392C87C2.3A2EEA9B@embeddededge.com> (raw)
In-Reply-To: NCBBKJKKGDLPHKDPAFFMAEMCCEAA.jsw-embedded@mindspring.com
Jason Wohlgemuth wrote:
>
> Dan,
>
> I actually modified head.S, not to get linux running, but to reboot the
> system. In our case, the gpio pin tied to the HRESET line actually reset
> several boards, which would be a bad thing in some cases. So I modified the
> m8xx_gorom (I think),
Sure, pick on the one thing I constantly mess up across the various
releases and patches :-). I don't even know why this function is
in this file, as it needs to be different for almost every board.
It is only a couple of lines of code, so have fun.
I am more concerned about messing up the kernel initialization
code. There are many assumptions (valid) that are made here about
the rest of the kernel structure. Similar to having unique processor
and board initialization somewhere, this is unique to the Linux
kernel.
-- Dan
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2000-05-25 1:54 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <39243D0C.68406C9D@lucent.com>
2000-05-21 5:07 ` QUERY: Embedded PowerPC Linux? Matt Porter
[not found] ` <39289187.3AEDEE47@chicago.avenew.com>
2000-05-23 5:10 ` Matt Porter
2000-05-24 17:03 ` Dan Malek
2000-05-24 23:54 ` Jason Wohlgemuth
2000-05-25 1:54 ` Dan Malek [this message]
2000-06-08 6:15 ` Matt Porter
2000-05-24 16:30 ` Dan Malek
2000-06-08 5:56 ` Matt Porter
2000-06-08 5:46 ` Dan Malek
2000-06-08 6:18 ` Murray Jensen
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=392C87C2.3A2EEA9B@embeddededge.com \
--to=dan@netx4.com \
--cc=jsw-embedded@mindspring.com \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=mporter@mvista.com \
--cc=tjroberts@lucent.com \
/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).