From: Ralf Baechle <ralf@linux-mips.org>
To: Yoichi Yuasa <yoichi_yuasa@tripeaks.co.jp>
Cc: linux-mips <linux-mips@linux-mips.org>
Subject: Re: [PATCH 1/5] MIPS: fix cobalt I/O resource range
Date: Mon, 4 Dec 2006 14:10:42 +0000 [thread overview]
Message-ID: <20061204141042.GA7231@linux-mips.org> (raw)
In-Reply-To: <20061201221242.261f57b0.yoichi_yuasa@tripeaks.co.jp>
On Fri, Dec 01, 2006 at 10:12:42PM +0900, Yoichi Yuasa wrote:
> This patch has fixed cobalt I/O reource range.
> The cobalt real I/O resource range from 0x0 to 0xffff.
>
> Yoichi
>
> Signed-off-by: Yoichi Yuasa <yoichi_yuasa@tripeaks.co.jp>
>
> diff -pruN -X mips/Documentation/dontdiff mips-orig/arch/mips/cobalt/setup.c mips/arch/mips/cobalt/setup.c
> --- mips-orig/arch/mips/cobalt/setup.c 2006-10-12 01:03:18.055569000 +0900
> +++ mips/arch/mips/cobalt/setup.c 2006-10-12 01:01:59.973744750 +0900
> @@ -130,8 +130,7 @@ void __init plat_mem_setup(void)
>
> set_io_port_base(CKSEG1ADDR(GT_DEF_PCI0_IO_BASE));
>
> - /* I/O port resource must include UART and LCD/buttons */
> - ioport_resource.end = 0x0fffffff;
> + ioport_resource.end = 0xffff;
This is actually the default, so the code can go and anyway then the
code stops making sense, too.
Ralf
next prev parent reply other threads:[~2006-12-04 14:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-01 13:12 [PATCH 1/5] MIPS: fix cobalt I/O resource range Yoichi Yuasa
2006-12-01 13:16 ` [PATCH 2/5] MIPS: remove unused resources for cobalt Yoichi Yuasa
2006-12-01 13:17 ` [PATCH 3/5] MIPS: separate cobalt PCI codes from setup.c Yoichi Yuasa
2006-12-01 13:19 ` [PATCH 4/5] MIPS: update reset operations for cobalt Yoichi Yuasa
2006-12-01 13:20 ` [PATCH 5/5] MIPS: clean up include files " Yoichi Yuasa
2006-12-04 14:13 ` [PATCH 3/5] MIPS: separate cobalt PCI codes from setup.c Ralf Baechle
2006-12-04 14:12 ` [PATCH 2/5] MIPS: remove unused resources for cobalt Ralf Baechle
2006-12-04 14:10 ` Ralf Baechle [this message]
2006-12-06 0:40 ` [PATCH 1/5] MIPS: fix cobalt I/O resource range Yoichi Yuasa
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=20061204141042.GA7231@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=linux-mips@linux-mips.org \
--cc=yoichi_yuasa@tripeaks.co.jp \
/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