From: Steve Tarr <tarr@lucent.com>
To: "Dan A. Dickey" <ddickey@charter.net>
Cc: Murray Jensen <Murray.Jensen@cmst.csiro.au>,
Dan Malek <dan@netx4.com>,
linuxppc-embedded@lists.linuxppc.org
Subject: Re: 8xx MMU Table Walk Base (was Re: kernel crashes at InstructionTLBMiss )
Date: Tue, 06 Jun 2000 15:37:32 -0600 [thread overview]
Message-ID: <393D6F1C.27C9A48E@lucent.com> (raw)
In-Reply-To: 393DBB5F.DB509DA@charter.net
"Dan A. Dickey" wrote:
Clip, clip, clip....
> > discussion groups).
>
> Murray,
> as far as I know - you are maybe the only one running 2.3.x on
> a powerpc. Most of the kernels that one can find lying about
> are 2.2.x (13/14? Can't remember at the moment).
>
> I, as well as others, definitely want to see 2.3.x or 2.4.0 running
> on an embedded powerpc.
>
Hey, it does. I have 2.3.99-pre7 hacked and running on a MPC8260.
Actually,
a pretty clean port with the exception of handling the SCC as the
console.
> ...
>
> > Again, apologies for not providing enough information in my message - I made
> > assumptions I shouldn't have. Obviously, on my first post I should have been
> > completely anal, because no-one knows me from a bar of soap. I can then start
> > to be less exacting after I have been around for a while.
>
> Everyone enjoys sarcasm... :) (Don't they?)
>
> > >Where did you get the sources? What
> > >patches did you apply? What are your hardware details? What
> > >modifications did you make?
> >
> > See above.
> >
> > >As for 2.4.xx, the 8xx still doesn't work correctly. However, I
> > >discovered it failed to work after the 403 additions, so I am now
> > >learning about the 403 in an effort to make everything live happily
> > >together again.
> >
> > It was my feeling that the problems were to do with the new memory allocation
> > stuff introduced a couple of months ago.
> >
> > >Note, this has nothing to do with M_TWB......
> >
> > I know. Now that we have gotten past treating me like a dill, please can you
> > re-read my original message and see if I am making any sense at all? I would
> > very much appreciate some insights and even constructive criticism. Cheers!
> > Murray...
> >
> > PS: I haven't contributed the Cogent platform changes yet, because I wasn't
> > happy that I had done everything properly. This was really my first foray
> > into taking part in the Linux/PPC embedded development community - I can't
> > say it has been particularly successful (despite my good feelings about
> > contributing a small fix a couple of days ago). I will try not to be too
> > discouraged.
>
> That's the spirit!
>
I get more done asking stupid questions than I do pondering the
elusive answer. Elephant hide and a resonable reputation of getting
things
done helps. Hang tough and have fun.......
Cheers --
tarr
> -Dan (A different one).
>
--
Steven Tarr
Lucent Technologies - Bell Labs
303-538-4056
tarr@lucent.com
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2000-06-06 21:37 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-06-04 4:40 kernel crashes at InstructionTLBMiss Daniel Wu
2000-06-05 2:32 ` Dan A. Dickey
2000-06-05 8:19 ` 8xx MMU Table Walk Base (was Re: kernel crashes at InstructionTLBMiss ) Murray Jensen
2000-06-05 20:37 ` Dan Malek
2000-06-06 6:31 ` Murray Jensen
2000-06-06 20:05 ` Dan Malek
2000-06-07 3:05 ` Dan A. Dickey
2000-06-07 9:17 ` Murray Jensen
2000-06-07 3:02 ` Dan A. Dickey
2000-06-06 21:37 ` Steve Tarr [this message]
2000-06-06 17:03 ` net driver receive problems Tom Roberts
2000-06-05 14:51 ` kernel crashes at InstructionTLBMiss Dan Malek
2000-06-05 15:55 ` Dan Malek
2000-06-05 16:19 ` Dan Malek
2000-06-06 3:59 ` Graham Stoney
2000-06-06 3:56 ` Daniel Wu
2000-06-06 20:18 ` Dan Malek
2000-08-10 12:05 ` too few RAM? Wojciech Kromer
2000-08-10 14:49 ` Dan Malek
2000-08-17 11:49 ` Wojciech Kromer
2000-06-30 6:17 ` Debug information for elf format Kwansuk Kim
2000-06-30 6:46 ` sungyeon
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=393D6F1C.27C9A48E@lucent.com \
--to=tarr@lucent.com \
--cc=Murray.Jensen@cmst.csiro.au \
--cc=dan@netx4.com \
--cc=ddickey@charter.net \
--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.