From: Matthew Wilcox <willy@debian.org>
To: linux-ia64@vger.kernel.org
Subject: Re: [PATCH] init IO port space, IO accessors earlier
Date: Wed, 17 Mar 2004 20:42:57 +0000 [thread overview]
Message-ID: <20040317204257.GT25059@parcelfarce.linux.theplanet.co.uk> (raw)
In-Reply-To: <200403171306.01728.bjorn.helgaas@hp.com>
On Wed, Mar 17, 2004 at 01:06:01PM -0700, Bjorn Helgaas wrote:
> +io_port_init (void)
> +{
> + extern unsigned long ia64_iobase;
> + unsigned long phys_iobase;
> +
> + /*
> + * Set `iobase' to the appropriate address in region 6 (uncached access range).
> + *
> + * The EFI memory map is the "preferred" location to get the I/O port space base,
> + * rather the relying on AR.KR0. This should become more clear in future SAL
> + * specs. We'll fall back to getting it out of AR.KR0 if no appropriate entry is
> + * found in the memory map.
> + */
I see you're only moving code here, but could you wrap this comment at
80 columns?
/*
* Set `iobase' to the appropriate address in region 6 (uncached
* access range). The EFI memory map is the "preferred" location
* to get the I/O port space base, rather the relying on AR.KR0.
* This should become more clear in future SAL specs. We'll fall
* back to getting it out of AR.KR0 if no appropriate entry is
* found in the memory map.
*/
> + phys_iobase = efi_get_iobase();
> + if (phys_iobase)
> + /* set AR.KR0 since this is all we use it for anyway */
> + ia64_set_kr(IA64_KR_IO_BASE, phys_iobase);
> + else {
> + phys_iobase = ia64_get_kr(IA64_KR_IO_BASE);
> + printk(KERN_INFO "No I/O port range found in EFI memory map, falling back "
> + "to AR.KR0\n");
This printk could also be wrapped:
printk(KERN_INFO "No I/O port range found in EFI memory map, "
"falling back to AR.KR0\n");
--
"Next the statesmen will invent cheap lies, putting the blame upon
the nation that is attacked, and every man will be glad of those
conscience-soothing falsities, and will diligently study them, and refuse
to examine any refutations of them; and thus he will by and by convince
himself that the war is just, and will thank God for the better sleep
he enjoys after this process of grotesque self-deception." -- Mark Twain
next prev parent reply other threads:[~2004-03-17 20:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-17 20:06 [PATCH] init IO port space, IO accessors earlier Bjorn Helgaas
2004-03-17 20:42 ` Matthew Wilcox [this message]
2004-03-17 20:49 ` Bjorn Helgaas
2004-03-17 20:57 ` David Mosberger
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=20040317204257.GT25059@parcelfarce.linux.theplanet.co.uk \
--to=willy@debian.org \
--cc=linux-ia64@vger.kernel.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