From: Alan <alan@lxorguk.ukuu.org.uk>
To: David Gibson <david@gibson.dropbear.id.au>
Cc: Andrew Morton <akpm@osdl.org>,
linuxppc-dev@ozlabs.org, linux-kernel@vger.kernel.org,
rmk@arm.linux.org.uk
Subject: Re: [PATCH 2/2] Use resource_size_t for serial port IO addresses
Date: Tue, 20 Feb 2007 13:06:34 +0000 [thread overview]
Message-ID: <20070220130634.72b9a02b@localhost.localdomain> (raw)
In-Reply-To: <20070220031951.5D53BDDD0E@ozlabs.org>
On Tue, 20 Feb 2007 14:19:51 +1100 (EST)
David Gibson <david@gibson.dropbear.id.au> wrote:
> 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.
>
> Signed-off-by: David Gibson <dwg@au1.ibm.com>
Acked-by: Alan Cox <alan@redhat.com>
WARNING: multiple messages have this Message-ID (diff)
From: Alan <alan@lxorguk.ukuu.org.uk>
To: David Gibson <david@gibson.dropbear.id.au>
Cc: Andrew Morton <akpm@osdl.org>, <linux-kernel@vger.kernel.org>,
<rmk@arm.linux.org.uk>, <linuxppc-dev@ozlabs.org>
Subject: Re: [PATCH 2/2] Use resource_size_t for serial port IO addresses
Date: Tue, 20 Feb 2007 13:06:34 +0000 [thread overview]
Message-ID: <20070220130634.72b9a02b@localhost.localdomain> (raw)
In-Reply-To: <20070220031951.5D53BDDD0E@ozlabs.org>
On Tue, 20 Feb 2007 14:19:51 +1100 (EST)
David Gibson <david@gibson.dropbear.id.au> wrote:
> 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.
>
> Signed-off-by: David Gibson <dwg@au1.ibm.com>
Acked-by: Alan Cox <alan@redhat.com>
next prev parent reply other threads:[~2007-02-20 12:03 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-20 3:17 Use resource_size_t for serial MMIO addresses David Gibson
2007-02-20 3:17 ` David Gibson
2007-02-20 3:19 ` [PATCH 1/2] Define FIXED_PORT flag for serial_core David Gibson
2007-02-20 3:19 ` David Gibson
2007-02-20 13:07 ` Alan
2007-02-20 13:07 ` Alan
2007-02-28 22:26 ` Russell King
2007-02-28 22:26 ` Russell King
2007-02-28 23:44 ` David Gibson
2007-03-01 10:30 ` Russell King
2007-03-02 1:57 ` David Gibson
2007-02-20 3:19 ` [PATCH 2/2] Use resource_size_t for serial port IO addresses David Gibson
2007-02-20 3:19 ` David Gibson
2007-02-20 13:06 ` Alan [this message]
2007-02-20 13:06 ` Alan
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=20070220130634.72b9a02b@localhost.localdomain \
--to=alan@lxorguk.ukuu.org.uk \
--cc=akpm@osdl.org \
--cc=david@gibson.dropbear.id.au \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.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 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.