From: Jon Masters <jonathan@jonmasters.org>
To: Peter Vandenabeele <peter.vandenabeele@mind.be>
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: The wonders of 2.4.23 [WAS: Re: [Fwd: ppc4xx Ports]]
Date: Wed, 03 Dec 2003 03:05:24 +0000 [thread overview]
Message-ID: <3FCD52F4.8040009@jonmasters.org> (raw)
In-Reply-To: <20031126165238.O7373@mind.be>
Hi Peter,
I changed kernel versions on my in house working port to 2.4.23 having
spent too long doing:
* Getting my head around the 405 TLB code in Linux[0].
* Fixing lots of pointless bits in 2.4.21.
[ The kernel was upgraded to 2.4.21 at some point. ]
So having realised the pointlessness of fixing stuff which is now in
2.4.23 I switched over and magically things are improved[1]. This is
fantastic because I no longer need to fix up the system call handler to
save register number 7 or add in tlbia stuff or many other things.
This kernel also adds fixed TLB entries for serial uart and I finally
decided that a lot of old changes to head_4xx.S were now in the true
stock kernel so I could switch to those instead. I still need to do
kludging for the MSR (!ME here) and cacheing weirdness but hey.
I think we can soon start talking about the stuff we are doing and get
some basic support for 405D PVR, xintc and random other bits in the
stock kernel even if there is not full support for Virtex II Pro.
Finally we can probably do with adding the UTLB errata fixes.
Hopefully it will not be long before I am able to do a lot of this stuff
now that the system I am working on is approaching stability with only
busybox init troubles and a custom distribution I am working on left
prior to the holidays. Hmmm... it is 03:00 now so back to bed.
Anyway here is another happy 2.4.23 user.
Jon.
[0] My copy of UTLK and various other documentation is now completely
covered in pen marks, probably coffee stains etc.
[1] I did track down the problem I was having with floating point which
cunningly turned out not to be a problem with that but with the UTLB
faults following a SHARED page not actually being shared correctly,
generating a later instruction fault on the second access.
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
prev parent reply other threads:[~2003-12-03 3:05 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-13 23:42 [Fwd: ppc4xx Ports] Jon Masters
2003-11-13 23:44 ` Dan Kegel
2003-11-13 23:51 ` Jon Masters
2003-11-14 0:20 ` Eugene Surovegin
2003-11-14 0:36 ` Jon Masters
2003-11-14 0:48 ` Eugene Surovegin
2003-11-14 12:51 ` Jon Masters
2003-11-26 15:52 ` Peter Vandenabeele
2003-11-27 22:52 ` Jon Masters
2003-11-27 22:58 ` Jon Masters
2003-12-03 8:16 ` Peter Ryser
2003-11-28 14:16 ` Jon Masters
2003-12-03 3:05 ` Jon Masters [this message]
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=3FCD52F4.8040009@jonmasters.org \
--to=jonathan@jonmasters.org \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=peter.vandenabeele@mind.be \
/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).