public inbox for linux-serial@vger.kernel.org
 help / color / mirror / Atom feed
From: Aristeu Sergio Rozanski Filho <aris@cathedrallabs.org>
To: Adam Belay <ambx1@neo.rr.com>
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 17:48:05 -0300	[thread overview]
Message-ID: <20050511204805.GJ3907@cathedrallabs.org> (raw)
In-Reply-To: <20050511202432.GA2720@neo.rr.com>

> 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.
My idea was just to enforce pnp_reserve_{io,irq} options for serial
ports too (8250_pnp does not check for those options). I was looking for a
way of ignoring a serial port I/O range (before Russell King point me to
setserial).
So, yes, please drop this patch as my problem is already solved in a
different (and much better) way. :)

--
Aristeu


      reply	other threads:[~2005-05-11 21:11 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
2005-05-11 20:48       ` Aristeu Sergio Rozanski Filho [this message]

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=20050511204805.GJ3907@cathedrallabs.org \
    --to=aris@cathedrallabs.org \
    --cc=ambx1@neo.rr.com \
    --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