From: Bjorn Helgaas <bjorn.helgaas@hp.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [PATCH 2.6.12 1/1] pcdp: add PCDP pci interface support
Date: Thu, 21 Apr 2005 21:41:50 +0000 [thread overview]
Message-ID: <1114119711.2784.72.camel@eeyore> (raw)
In-Reply-To: <20050421202619.31042.93421.39277@attica.americas.sgi.com>
On Thu, 2005-04-21 at 15:26 -0500, Mark Maule wrote:
> #ifdef CONFIG_SERIAL_SGI_L1_CONSOLE
> {
> extern int sn_serial_console_early_setup(void);
> if (!sn_serial_console_early_setup())
> - return 0;
> + earlycons++;
> }
If SGI is going to support the PCDP, why don't you add a new
PCDP device type for the L1 console? It feels like a nuisance
to have two places to look for console device info. How do
you say "use VGA but not the L1 console"?
> +unsigned long pcdp_vga_io_base;
> +unsigned long pcdp_vga_mem_base;
Apart from the extra space that snuck into the definitions, I
don't really like these being associated with the PCDP. Isn't
this the sort of thing that Ben H's VGA arbitrator[1] would
also change?
So I vote for something with a more neutral name, possibly in
arch/ia64/kernel/setup.c.
And pcdp_vga_io_base isn't used anywhere, so I'd remove it.
> +setup_vga_console(struct pcdp_device *dev)
> {
> +
> #if defined(CONFIG_VT) && defined(CONFIG_VGA_CONSOLE)
> - if (efi_mem_type(0xA0000) = EFI_CONVENTIONAL_MEMORY) {
> + u8 *if_ptr;
This isn't ACPI, so we don't need extra tabs in the middle
of variable declarations (or blank lines after the beginning
of the function). :-)
> + memcpy(&if_pci, if_ptr, sizeof(struct pcdp_if_pci));
The above is correct, but it's easier to verify this:
memcpy(&if_pci, if_ptr, sizeof(if_pci));
[1] http://lkml.org/lkml/2005/3/9/42
next prev parent reply other threads:[~2005-04-21 21:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-21 20:26 [PATCH 2.6.12 1/1] pcdp: add PCDP pci interface support Mark Maule
2005-04-21 21:41 ` Bjorn Helgaas [this message]
2005-04-21 22:05 ` Mark Maule
2005-04-23 18:00 ` Mark Maule
2005-04-25 15:26 ` Bjorn Helgaas
2005-04-25 15:34 ` Mark Maule
2005-04-25 16:01 ` Bjorn Helgaas
2005-04-25 20:51 ` Mark Maule
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=1114119711.2784.72.camel@eeyore \
--to=bjorn.helgaas@hp.com \
--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 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.