From: Tom Rini <trini@kernel.crashing.org>
To: Dan Malek <dan@embeddededge.com>
Cc: Pantelis Antoniou <panto@intracom.gr>,
Kumar Gala <kumar.gala@motorola.com>,
Linuxppc-Embedded <linuxppc-embedded@lists.linuxppc.org>
Subject: Re: 8xx-2.6 | Prolog
Date: Thu, 27 May 2004 15:34:24 -0700 [thread overview]
Message-ID: <20040527223423.GM6763@smtp.west.cox.net> (raw)
In-Reply-To: <B89F9AE2-AFF4-11D8-89B7-003065F9B7DC@embeddededge.com>
On Thu, May 27, 2004 at 11:44:21AM -0400, Dan Malek wrote:
>
> On May 26, 2004, at 8:05 AM, Pantelis Antoniou wrote:
>
> >Awaiting comments.
[snip]
> ... We can't define update_mmu_cache
> as a null function. It performs a necessary function of cache
> management. We may just be lucky because the caches on the 8xx
> are small, but this is a subtle bug waiting to happen.
Are you certain? This is something in 2.4, and while I am having weird
problems locally (that I can't rule out as being hw issues), adding that
change in is what gets me a working init=/bin/bash.
> I did not check these in. Tom can you do so and make sure other
> 8xx boards will at least compile? I'll fix up the stuff I don't like
> later :-)
I'm going to be checking this all in momentarily. On my system right
now, I can get both of my rpxlite's to init=/bin/bash, mostly working,
if and only if I use the new uart driver and if I configure it for SMC1
AND SCC1 (which seems wrong).
--
Tom Rini
http://gate.crashing.org/~trini/
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2004-05-27 22:34 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-26 12:05 8xx-2.6 | Prolog Pantelis Antoniou
2004-05-26 15:36 ` Dan Malek
2004-05-26 15:55 ` Tom Rini
2004-05-26 16:39 ` Dan Malek
2004-05-26 17:40 ` Marcelo Tosatti
2004-05-27 15:44 ` Dan Malek
2004-05-27 16:39 ` Joakim Tjernlund
2004-05-27 22:34 ` Tom Rini [this message]
2004-05-31 9:31 ` Pantelis Antoniou
2004-05-28 6:40 ` Pantelis Antoniou
2004-05-31 1:59 ` Song Sam
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=20040527223423.GM6763@smtp.west.cox.net \
--to=trini@kernel.crashing.org \
--cc=dan@embeddededge.com \
--cc=kumar.gala@motorola.com \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=panto@intracom.gr \
/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).