From: Bjorn Helgaas <bjorn.helgaas@hp.com>
To: Russell King <rmk+serial-lFZ/pmaqli7XmaaqVzeoHQ@public.gmane.org>
Cc: linux-serial-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
Len Brown <len.brown-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>,
acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org,
linux-ia64-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
Mattieu Castet <castet.matthieu-GANU6spQydw@public.gmane.org>,
Li Shaohua <shaohua.li-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Subject: Re: [PATCH] serial: remove 8250_acpi (subsumed by 8250_pnp and PNPACPI)
Date: Tue, 20 Sep 2005 16:04:31 +0000 [thread overview]
Message-ID: <200509201004.31224.bjorn.helgaas@hp.com> (raw)
In-Reply-To: <200509161142.33723.bjorn.helgaas-VXdhtT5mjnY@public.gmane.org>
On Friday 16 September 2005 11:42 am, Bjorn Helgaas wrote:
> With the combination of PNPACPI and 8250_pnp, we no longer need
> 8250_acpi.
>
> The only in-tree configs that contain CONFIG_SERIAL_8250_ACPI are ia64.
> ia64 users should make sure CONFIG_PNP and CONFIG_PNPACPI are set so
> 8250_pnp.c can discover built-in serial ports. Tony has already
> accepted a patch to turn them on in the default configs.
Please don't apply this just yet. Tony Luck tried it and tripped
over a deficiency in PNPACPI that I'll have to fix first.
(HP rx1620 has an ACPI_RSTYPE_ADDRESS32 item in its _PRS, and
PNPACPI doesn't know what to do with it.)
next prev parent reply other threads:[~2005-09-20 16:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-16 17:42 [PATCH] serial: remove 8250_acpi (subsumed by 8250_pnp and PNPACPI) Bjorn Helgaas
[not found] ` <200509161142.33723.bjorn.helgaas-VXdhtT5mjnY@public.gmane.org>
2005-09-20 16:04 ` Bjorn Helgaas [this message]
2005-11-07 21:59 ` Bjorn Helgaas
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=200509201004.31224.bjorn.helgaas@hp.com \
--to=bjorn.helgaas@hp.com \
--cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=castet.matthieu-GANU6spQydw@public.gmane.org \
--cc=len.brown-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
--cc=linux-ia64-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-serial-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=rmk+serial-lFZ/pmaqli7XmaaqVzeoHQ@public.gmane.org \
--cc=shaohua.li-ral2JQCrhuEAvxtiuMwx3w@public.gmane.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