public inbox for linux-serial@vger.kernel.org
 help / color / mirror / Atom feed
From: Adam Belay <ambx1@neo.rr.com>
To: Aristeu Sergio Rozanski Filho <aris@cathedrallabs.org>
Cc: Russell King <rmk@arm.linux.org.uk>, linux-serial@vger.kernel.org
Subject: Re: [PATCH] make 8250_pnp use pnp_manual_config_dev()
Date: Wed, 11 May 2005 16:24:32 -0400	[thread overview]
Message-ID: <20050511202432.GA2720@neo.rr.com> (raw)
In-Reply-To: <20050510130715.GF3907@cathedrallabs.org>

On Tue, May 10, 2005 at 10:07:15AM -0300, Aristeu Sergio Rozanski Filho wrote:
> > > Hi,
> > > 	this patch makes 8250_pnp use pnp_manual_config_dev() so
> > > 	pnp_reserve_{io,irq} option will be valid for serial ports too.
> > > 	Please consider applying

pnp_manual_config_dev is intented for drivers that use different
resource assignments than those automatically set by PnP.  It looks
like you're passing the same config back.

Could you please explain your rational here further.

Values already assigned by the BIOS are not checked against reserved
regions.  Is this what you're getting it?  If so, we could have double
detection issues between the PnP protocol and the legacy detection
mechanism.


> > 
> > Please copy this to Adam Belay.  There are some problems with PNP
> > serial ports because they can clash with with standard addresses
> > for x86 ports.

Ideally, I think we should avoid legacy probing if PnPBIOS or ACPI is
available.  When serial console is enabled we could have an exception.
What do you think?

> > 
> > We don't particularly want to reconfigure the standard x86 ports
> > to some other addresses just because we've already detected them
> > and claimed their resources external to PNP.
> OK, adding Adam Belay to CC and attaching the patch again.
> 
> --
> Aristeu

Thanks,
Adam


  reply	other threads:[~2005-05-11 20:30 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-10 12:15 [PATCH] make 8250_pnp use pnp_manual_config_dev() Aristeu Sergio Rozanski Filho
2005-05-10 12:51 ` Russell King
2005-05-10 13:07   ` Aristeu Sergio Rozanski Filho
2005-05-11 20:24     ` Adam Belay [this message]
2005-05-11 20:48       ` Aristeu Sergio Rozanski Filho

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=20050511202432.GA2720@neo.rr.com \
    --to=ambx1@neo.rr.com \
    --cc=aris@cathedrallabs.org \
    --cc=linux-serial@vger.kernel.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