public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: Jes Sorensen <jes@wildopensource.com>
To: linux-ia64@vger.kernel.org
Subject: Re: serial legacy ports and ACPI
Date: Thu, 31 Jul 2003 03:54:02 +0000	[thread overview]
Message-ID: <marc-linux-ia64-105962365319200@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105761215001812@msgid-missing>

>>>>> "Bjorn" = Bjorn Helgaas <bjorn.helgaas@hp.com> writes:

Bjorn> I like the idea of this, but 1) You might pass it by the ACPI
Bjorn> folks to make sure this is the intent of the spec (sure looks
Bjorn> reasonable to me, though).  2) I don't really like the
Bjorn> implementation in the sense that a) The spec suggests that
Bjorn> LEGACY_DEVICES might also cover things other than serial ports,
Bjorn> i.e., a legacy LPT port, so: b) I think the check should go in
Bjorn> arch/.../acpi.c.  We did something similar for keyboard
Bjorn> detection (see acpi_kbd_controller_present), and I think it
Bjorn> worked out pretty well.

Hi Bjorn,

I had a chat with Grant and Matthew about is a little while ago (and
possibly a few other people whom I can't remember right now) and we
basically came to a similar conclusion. Once I find a bit more time,
I'd like to introduce an interface along the lines of

        legacy_device_present(LEGACY_{IDE,SERIAL,PARALLEL})

This could be quite useful for other architectures as well I believe.

Cheers,
Jes

  parent reply	other threads:[~2003-07-31  3:54 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-07 21:05 serial legacy ports and ACPI Jes Sorensen
2003-07-30 23:09 ` Bjorn Helgaas
2003-07-31  3:54 ` Jes Sorensen [this message]
2003-08-26 16:24 ` Alex Williamson

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=marc-linux-ia64-105962365319200@msgid-missing \
    --to=jes@wildopensource.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox