From: Andrew Morton <akpm@linux-foundation.org>
To: Josh Boyer <jwboyer@linux.vnet.ibm.com>
Cc: linuxppc-dev@ozlabs.org, paulus@samba.org, rmk@arm.linux.org.uk,
david@gibson.dropbear.id.au
Subject: Re: [PATCH] Use resource_size_t for serial port IO addresses
Date: Fri, 13 Jul 2007 12:02:26 -0700 [thread overview]
Message-ID: <20070713120226.797117e2.akpm@linux-foundation.org> (raw)
In-Reply-To: <1184335336.6456.17.camel@weaponx.rchland.ibm.com>
On Fri, 13 Jul 2007 09:02:16 -0500
Josh Boyer <jwboyer@linux.vnet.ibm.com> wrote:
> This is a resend of a patch David sent out on May 7. Without it, the
> PowerPC 44x port in 2.6.22 and on is broken. I've rebased it off of
> Linus' current tree. Please consider pushing this soon.
>
> josh
>
>
> At present, various parts of the serial code use unsigned long to
> define resource addresses. This is a problem, because some 32-bit
> platforms have physical addresses larger than 32-bits, and have mmio
> serial uarts located above the 4GB point.
>
> This patch changes the type of mapbase in both struct uart_port and
> struct plat_serial8250_port to resource_size_t, which can be
> configured to be 64 bits on such platforms. The mapbase in
> serial_struct can't safely be changed, because that structure is user
> visible.
This is something we should do, but I have recollections of Russell
identifying problems with this patch, or at least an earlier version of it?
> Signed-off-by: David Gibson <dwg@au1.ibm.com>
This should have had Signed-off-by:you as well.
next prev parent reply other threads:[~2007-07-13 19:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-13 14:02 [PATCH] Use resource_size_t for serial port IO addresses Josh Boyer
2007-07-13 19:02 ` Andrew Morton [this message]
2007-07-13 19:24 ` Josh Boyer
2007-07-15 11:06 ` Russell King
2007-07-23 14:08 ` Josh Boyer
2007-07-23 19:34 ` Andrew Morton
2007-07-24 1:57 ` David Gibson
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=20070713120226.797117e2.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=david@gibson.dropbear.id.au \
--cc=jwboyer@linux.vnet.ibm.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=paulus@samba.org \
--cc=rmk@arm.linux.org.uk \
/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).