From: Bjorn Helgaas <bjorn.helgaas@hp.com>
To: Len Brown <lenb@kernel.org>
Cc: Zhang Rui <rui.zhang@intel.com>,
"linux-acpi@vger" <linux-acpi@vger.kernel.org>
Subject: Re: [PATCH 0/14] ACPI: make ACPI use driver model
Date: Fri, 8 Dec 2006 09:50:52 -0700 [thread overview]
Message-ID: <200612080950.52390.bjorn.helgaas@hp.com> (raw)
In-Reply-To: <200612080529.56183.len.brown@intel.com>
[Sorry for the duplicate; I fat-fingered my reply and inadvertently
introduced an HTML sub-part, causing linux-acpi to reject it as spam.]
On Friday 08 December 2006 03:29, Len Brown wrote:
> On Thursday 07 December 2006 11:28, Bjorn Helgaas wrote:
> > Is it possible to extend the PNP model to include ACPI, rather
> > than introducing a new ACPI model alongside the PNP model?
>
> Hmmm, well, I thought we were doing well to get ride of ACPI specific
> devices names...
>
> The PNPBIOS + ACPI box will never run both PNPBIOS and ACPI at
> the same time.
Right. But should the fact that we use ACPI instead of PNPBIOS make
a difference to userland? My intuition says "no." Obviously there
might be new devices and new functionality with ACPI, so there might
be new files and knobs in sysfs, but if you don't care about those,
it'd be nice if all the old PNP stuff just worked.
> My question is where the "cut point is". At what point do we start
> pushing this work upstream, and what parts of it?
I don't want to delay pushing Zhang's patches upstream. I think
they are definitely a step in the right direction.
Bjorn
next prev parent reply other threads:[~2006-12-08 16:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-07 12:56 [PATCH 0/14] ACPI: make ACPI use driver model Zhang Rui
2006-12-07 16:28 ` Bjorn Helgaas
2006-12-08 1:34 ` Shaohua Li
2006-12-08 10:29 ` Len Brown
2006-12-08 16:50 ` Bjorn Helgaas [this message]
2006-12-08 10:31 ` Len Brown
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=200612080950.52390.bjorn.helgaas@hp.com \
--to=bjorn.helgaas@hp.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=rui.zhang@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox