All of lore.kernel.org
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Matt Sealey <matt@genesi-usa.com>
Cc: linuxppc-dev@ozlabs.org, "Régis Odeyé" <regis.odeye@kontron.com>
Subject: Re: Extended Addressing Mode
Date: Thu, 23 Oct 2008 09:48:35 +1100	[thread overview]
Message-ID: <1224715715.7654.355.camel@pasglop> (raw)
In-Reply-To: <48FFA755.5050808@genesi-usa.com>

On Wed, 2008-10-22 at 17:21 -0500, Matt Sealey wrote:
> 
> Because we're Genesi! And we have a firmware solution that 
> kind of has to keep 32-bit pointers in the unlikely event that 
> someone actually uses the client interface (besides yaboot!).
> 
> Having I/O in the 36-bit range could cause all sorts of 
> explosions, and we're running real-mode so trapping and faking 
> I/O accesses is REALLy difficult :}

how so ? we have plethora of 32-bit firmwares including OF
implementations that can perfectly address 36 bit physical address
space. Nothing to do with having 32-bit pointers.

Cheers,
Ben.

      reply	other threads:[~2008-10-22 22:49 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-22  8:59 Extended Addressing Mode Régis Odeyé
2008-10-22 12:31 ` Kumar Gala
2008-10-22 12:59   ` Régis Odeyé
2008-10-22 13:08     ` Kumar Gala
2008-10-22 13:40       ` Régis Odeyé
2008-10-22 13:42       ` Matt Sealey
2008-10-22 14:06         ` Kumar Gala
2008-10-22 14:19           ` Matt Sealey
2008-10-22 14:58             ` Kumar Gala
2008-10-22 18:11               ` Matt Sealey
2008-10-22 19:59                 ` Becky Bruce
2008-10-22 22:18                   ` Matt Sealey
2008-10-22 14:22           ` Matt Sealey
2008-10-22 14:59             ` Kumar Gala
2008-10-22 18:25               ` Matt Sealey
2008-10-22 14:18         ` Régis Odeyé
2008-10-22 22:11       ` Benjamin Herrenschmidt
2008-10-22 22:21         ` Matt Sealey
2008-10-22 22:48           ` Benjamin Herrenschmidt [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=1224715715.7654.355.camel@pasglop \
    --to=benh@kernel.crashing.org \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=matt@genesi-usa.com \
    --cc=regis.odeye@kontron.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 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.