linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Jon Masters <jonathan@jonmasters.org>
To: Peter Vandenabeele <peter.vandenabeele@mind.be>
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: [Fwd: ppc4xx Ports]
Date: Thu, 27 Nov 2003 22:52:41 +0000	[thread overview]
Message-ID: <3FC68039.4080206@jonmasters.org> (raw)
In-Reply-To: <20031126165238.O7373@mind.be>



Peter Vandenabeele wrote:

| On Thu, Nov 13, 2003 at 04:48:05PM -0800, Eugene Surovegin wrote:
| [...]
|
|>I don't have any PTE/TLB related problems on 405GP/405GPr.
|
|
| On the PowerPC 405 in the Virtex-II Pro, we needed to turn off
| half of the TLB entries as per "Solution 12" on
|
http://support.xilinx.com/xlnx/xil_ans_display.jsp?iLanguageID=1&iCountryID=1&getPagePath=14052
|
| "... Limit TLB depth to 32 entries by only using even entries in the
TLB ...."
|
| Peter
|

Hi there,

I think I mentioned before that I already fixed that for the port I am
working on by incrementing next TLB entry by 2 if on Virtex II Pro.
Actually if you check a post I made to comp.arch.fpga over the summer...
I call it CONFIG_BROKEN_XILINX_TLB or something like that (other ports
are now starting to fix that too) - several other errata too.

[ Like I said before we have two similar ports now so once I can release
the modifications then we should look at how this can help us. The stuff
I am working on at the moment is not going out yet and for various
commercial reasons I prefer not to disclose who it is for, etc. ]

The problem I currently have was traced when using the dynamic linker
library from my Powerbook Debian on my test NFS filesystem and then
running up something compiled against the main normal libc with floating
point register save restore context stuff. So this leads me on to...

...there is something wrong with the trapping and handling of stfd and
similar operations on my port when the kernel tries to do the
copy_to_user to actually change the saved floating point register set.
Now that I know where the bug is I can fix it next week[0].

Jon.

[0] I work a 3 day week but take work home with me too much so tracked
this down today when debugging in Starbucks without the hardware but
with my Powerbook and various printouts...using 9600bps dialup proxied
through my Zaurus wifi because no IR on Powerbook revision. ;-).


** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

  reply	other threads:[~2003-11-27 22:52 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 [this message]
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         ` The wonders of 2.4.23 [WAS: Re: [Fwd: ppc4xx Ports]] Jon Masters

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=3FC68039.4080206@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).