linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Adrian Cox <apc@agelectronics.co.uk>
To: linuxppc-embedded@lists.linuxppc.org
Subject: Re: Floating Point problems with Linux on the EST SBC8260
Date: Fri, 26 May 2000 11:01:47 +0100	[thread overview]
Message-ID: <392E4B8B.E3C70B27@agelectronics.co.uk> (raw)
In-Reply-To: Pine.BSF.4.21.0005251319150.9249-100000@invalid.ed.ntnu.no


Geir Frode Raanes wrote:

> BTW, VxWorks can not easily handle more than 32 MBytes of local RAM
> as the eabi specification (as a result of the PowerPC architecure)
> rules for 26 bit (signed) relative addressing. Hence, I will design
> in exactly 32 MBytes of soldered low power SDRAM on UPMA and assign
> UPMB to a DIMM socket. How does PPC/Linux handle this addressing
> problem?

The current release of VxWorks is prepared to use a long jump sequence
to jump to a 32 bit address. Tornado 2 out of the box has worked fine
for me on a 128MByte 7400.

The problem only ever occurs when your code occupies an address range
greater than 32MBytes. VxWorks doesn't support virtual addressing
without some add-ons. It always placed the kernel at the bottom of
memory and dynamically loaded code at the top, so that calls from the
dynamically loaded code into the kernel had offsets that couldn't fit in
a relative branch.

Linux, however, never had this problem. Linux uses virtual memory, which
keeps the application within a smaller address range.

- Adrian Cox, AG Electronics

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

  parent reply	other threads:[~2000-05-26 10:01 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20000524134257.A9100@lx.c-side.com>
     [not found] ` <m12uikI-001SyaC@bucks>
2000-05-24 22:05   ` Floating Point problems with Linux on the EST SBC8260 Neil Russell
2000-05-24 22:26     ` Dan Malek
2000-05-24 23:06       ` Neil Russell
2000-05-25  1:22         ` Dan Malek
2000-05-25  3:17           ` Neil Russell
2000-05-25  3:45             ` Dan Malek
2000-05-25 12:13             ` Geir Frode Raanes
2000-05-25 17:30               ` Dan Malek
2000-05-26 10:01               ` Adrian Cox [this message]
2000-05-26 12:49                 ` Geir Frode Raanes
2000-05-26 13:52                   ` Adrian Cox
2000-05-24 23:33     ` diekema_jon
2000-05-25 14:44 Gessner, Matt
2000-05-25 16:52 ` Dan Malek
  -- strict thread matches above, loose matches on Subject: below --
2000-05-24 19:47 diekema_jon
2000-05-24 20:42 ` Bill Roman
2000-05-30 15:36   ` diekema_jon
2000-05-24 20:43 ` Neil Russell
2000-05-24 20:44 ` Neil Russell
2000-05-24 21:31 ` Dan Malek
2000-05-24 23:41   ` diekema_jon

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=392E4B8B.E3C70B27@agelectronics.co.uk \
    --to=apc@agelectronics.co.uk \
    --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 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).