From: Ralf Baechle <ralf@linux-mips.org>
To: pascal@pabr.org
Cc: Manuel Lauss <manuel.lauss@googlemail.com>, linux-mips@linux-mips.org
Subject: Re: [RFC] Support 36-bit iomem on 32-bit Au1x00
Date: Thu, 28 Jan 2010 14:18:58 +0100 [thread overview]
Message-ID: <20100128131858.GA13807@linux-mips.org> (raw)
In-Reply-To: <i8xpr4wftsy.fsf@pabr.org>
On Tue, Jan 26, 2010 at 10:19:22PM +0100, pascal@pabr.org wrote:
The whole fixing up of I/O addresses was necessary because the generic
code was written to assume that sizeof(unsigned long) == sizeof(void *)
and that mostly because it was handy for Linus' i386 world.
Today I think it would be preferable to get rid of the the fixups, pay the
small price for the larger resources and get sanity in exchange. My gut
feeling is that the bloat factor should be small. Either way, I'll let
you two sort this out for Alchemy and mark this patch as defered.
Ralf
next prev parent reply other threads:[~2010-01-28 13:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-03 12:39 [RFC] Support 36-bit iomem on 32-bit Au1x00 pascal
2010-01-26 20:46 ` Manuel Lauss
2010-01-26 21:19 ` pascal
2010-01-28 13:18 ` Ralf Baechle [this message]
2010-01-28 13:22 ` Manuel Lauss
2010-01-28 13:53 ` Ralf Baechle
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=20100128131858.GA13807@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=linux-mips@linux-mips.org \
--cc=manuel.lauss@googlemail.com \
--cc=pascal@pabr.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).