public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Jonathan Larmour <jlarmour@redhat.com>
To: Chris Morrow <cmorrow@YottaYotta.com>
Cc: ecos-discuss@sourceware.cygnus.com
Subject: Re: [ECOS] mips mmu setup
Date: Mon, 26 Feb 2001 12:39:00 -0000	[thread overview]
Message-ID: <3A9ABEEE.6E164D1@redhat.com> (raw)
In-Reply-To: <3A99BC17.7EB5AA48@YottaYotta.com>

Chris Morrow wrote:
> 
> For the vrc4373 port, the hal_mips_setup routine
> use add instructions for the following sequence.
> 
>         li      tmp,PADDR_INC
>         add     vaddr,vaddr,tmp
>         add     paddr0,paddr0,tmp
> 
> Which is okay until you try to map in 2 gig of
> address space at which point the vaddr calculate
> will result in 0x80000000 during the last interation
> of the loop. This will cause an interger overflow
> exception.
> 
> All the add's in that function should probably be addu's.

Thanks for the report. Assuming you have hardware that barfs on this, in
the next anonymous CVS update, can you check that I've got all the ones
that need doing? Also if there are any in the arch HAL please pipe up,
preferably with a patch of course :-).

Jifl
-- 
Red Hat, Rustat House, Clifton Road, Cambridge, UK. Tel: +44 (1223) 271062
Maybe this world is another planet's Hell -Aldous Huxley || Opinions==mine

  reply	other threads:[~2001-02-26 12:39 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-01-15 12:26 [ECOS] Header files in platform port Paul Pham
2001-01-15 13:22 ` [ECOS] hal_copy_data and hal_zero_bss Chris Morrow
2001-01-15 18:30   ` Jonathan Larmour
2001-02-25 18:05     ` Chris Morrow
2001-02-25 18:15       ` [ECOS] mips mmu setup Chris Morrow
2001-02-26 12:39         ` Jonathan Larmour [this message]
2001-02-26 15:22       ` [ECOS] hal_copy_data and hal_zero_bss Jonathan Larmour
2001-02-27  1:54         ` Chris Morrow
2001-02-27 10:25           ` Jonathan Larmour
2001-01-15 18:44 ` [ECOS] Header files in platform port Jonathan Larmour

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=3A9ABEEE.6E164D1@redhat.com \
    --to=jlarmour@redhat.com \
    --cc=cmorrow@YottaYotta.com \
    --cc=ecos-discuss@sourceware.cygnus.com \
    /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 read-only IMAP folder(s) and NNTP newsgroup(s).