All of lore.kernel.org
 help / color / mirror / Atom feed
From: Matt Porter <porter@cox.net>
To: Paul Mackerras <paulus@samba.org>
Cc: Matt Porter <porter@cox.net>, linuxppc-embedded@lists.linuxppc.org
Subject: Re: Ebony bootloader
Date: Wed, 12 Jun 2002 03:51:10 -0700	[thread overview]
Message-ID: <20020612035110.A29183@home.com> (raw)
In-Reply-To: <15622.55222.41836.183547@argo.ozlabs.ibm.com>; from paulus@samba.org on Wed, Jun 12, 2002 at 03:10:14PM +1000


On Wed, Jun 12, 2002 at 03:10:14PM +1000, Paul Mackerras wrote:
> Matt Porter writes:
>
> > Read Understanding Linux, Linux Device Drivers, and the
> > documentation in Documentation/ directory.  ioremap64()
> > is a version of ioremap() for >32-bit physical address
> > systems (440, 745x).
>
> Incidentally, I don't think we should have ioremap64 or
> ioremap_native, instead ioremap should just take a phys_addr_t.  It
> will have to do some handling of truncated addresses from pci drivers

It already does that work.

> but that should be manageable and the interface will be much more
> uniform if we use ioremap everywhere instead of using ioremap,
> ioremap64 and ioremap_native in different places.

Yes, I agree.  At the beginning of this, I was thinking that a
different ioremap prototype was going to get us into to compiler
trouble.

Regards,
--
Matt Porter
porter@cox.net
This is Linux Country. On a quiet night, you can hear Windows reboot.

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

  reply	other threads:[~2002-06-12 10:51 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-11 23:43 Ebony bootloader Khai Trinh
2002-06-12  2:51 ` Matt Porter
2002-06-12  5:10   ` Paul Mackerras
2002-06-12 10:51     ` Matt Porter [this message]
2002-06-12 11:33   ` Khai Trinh
2002-06-15 15:10     ` Matt Porter

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=20020612035110.A29183@home.com \
    --to=porter@cox.net \
    --cc=linuxppc-embedded@lists.linuxppc.org \
    --cc=paulus@samba.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 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.