All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bjorn Helgaas <bjorn.helgaas@hp.com>
To: Adam Belay <ambx1@neo.rr.com>
Cc: rmk+serial@arm.linux.org.uk, linux-serial@vger.kernel.org,
	shaohua.li@intel.com
Subject: Re: [PATCH] SERIAL: discover PNP ports before PCI, etc
Date: Thu, 10 Feb 2005 09:43:18 -0700	[thread overview]
Message-ID: <1108053798.29578.12.camel@eeyore> (raw)
In-Reply-To: <20050210021652.GA594@neo.rr.com>

On Wed, 2005-02-09 at 21:16 -0500, Adam Belay wrote:
> On Wed, Feb 09, 2005 at 01:12:47PM -0700, Bjorn Helgaas wrote:
> > PNP ports tend to be built-in, and discovering them after
> > PCI ports means the names of the built-in ports can change
> > if you add or remove PCI ports.
> > 
> > (And yes, we should look at getting rid of 8250_acpi.c
> > now that we have PNPACPI, but that's for another patch.)
> > 
> > Signed-off-by: Bjorn Helgaas <bjorn.helgaas@hp.com>>
> 
> I think this used to be the old behavior.  It was changed because some
> of the resources reserved by pnp would also be reserved by pci, causing
> pci to fail.  We should see if this is still the case.

That must be before the 2.5 series ...  Everything in the BK
history (which admittedly only goes back to 7/21/2002) has
PCI before PNP.

Wouldn't it be a bug if PNP described a resource that can be
discovered by standard PCI discovery?

I think we should move PNP before PCI and fix whatever resource
problems crop up.


  reply	other threads:[~2005-02-10 16:43 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-09 20:12 [PATCH] SERIAL: discover PNP ports before PCI, etc Bjorn Helgaas
2005-02-10  2:16 ` Adam Belay
2005-02-10 16:43   ` Bjorn Helgaas [this message]
     [not found]     ` <20050210173725.GA380@neo.rr.com>
2005-02-10 17:49       ` Bjorn Helgaas
2005-02-10 18:39         ` Russell King

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=1108053798.29578.12.camel@eeyore \
    --to=bjorn.helgaas@hp.com \
    --cc=ambx1@neo.rr.com \
    --cc=linux-serial@vger.kernel.org \
    --cc=rmk+serial@arm.linux.org.uk \
    --cc=shaohua.li@intel.com \
    /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.