From: "Walter L. Wimer III" <walt.wimer@timesys.com>
To: linuxppc-embedded@ozlabs.org
Subject: Re: IMAP_ADDR on PPC 8xx
Date: Tue, 09 May 2006 16:46:03 -0400 [thread overview]
Message-ID: <1147207564.3139.20.camel@excalibur.timesys.com> (raw)
In-Reply-To: <20060509202257.551DF352B2A@atlas.denx.de>
On Tue, 2006-05-09 at 22:22 +0200, Wolfgang Denk wrote:
> In message <1147194879.2200.41.camel@excalibur.timesys.com> you wrote:
> >
> > Thanks again for the advice. Interestingly, I gave the wrong
> > address above. It wasn't 0x22000000, it was 0x02200000 (i.e.
> > even lower!). And yet with the "io_remap()'ed global variable"
> > patch, 2.6.11.7 does indeed work on this board with this U-Boot....
> > Perhaps this works because this particular board only has 8MiB of
> > RAM....
>
> It does not work. It will certainly crash as soon as you start a few
> user space applications.
Well, something "interesting" is certainly going on because our 2.6.11.7
kernel *does* work and *does not* crash when running user space
applications. It runs BusyBox quite happily with multiple processes
(e.g. 3 incoming telnet sessions, a console shell, etc.).
I can only conclude that there is something more to our 2.6.11.7-based
patch than I currently understand.
Cheers!
Walt
next prev parent reply other threads:[~2006-05-09 20:46 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-08 17:23 IMAP_ADDR on PPC 8xx Walter L. Wimer III
2006-05-08 22:46 ` Wolfgang Denk
2006-05-09 17:14 ` Walter L. Wimer III
2006-05-09 20:22 ` Wolfgang Denk
2006-05-09 20:46 ` Walter L. Wimer III [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-05-09 18:38 Kenneth Poole
2006-05-09 19:52 ` Walter L. Wimer III
2006-05-09 21:51 ` Dan Malek
2006-05-10 15:23 ` Walter L. Wimer III
2006-05-10 16:49 ` Walter L. Wimer III
2006-05-10 17:45 ` Dan Malek
2006-05-10 19:58 ` John Rigby
2006-05-10 20:19 ` 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=1147207564.3139.20.camel@excalibur.timesys.com \
--to=walt.wimer@timesys.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).