From: Adam Belay <ambx1@neo.rr.com>
To: Bjorn Helgaas <bjorn.helgaas@hp.com>
Cc: linux-pcmcia@lists.infradead.org, linux-acpi@vger.kernel.org,
Len Brown <len.brown@intel.com>,
Matthieu Castet <castet.matthieu@free.fr>,
Li Shaohua <shaohua.li@intel.com>
Subject: Re: [RFC] Add lspnp support for sysfs
Date: Thu, 19 Jan 2006 21:47:32 -0500 [thread overview]
Message-ID: <20060120024731.GA27435@neo.rr.com> (raw)
In-Reply-To: <200601191650.59642.bjorn.helgaas@hp.com>
On Thu, Jan 19, 2006 at 04:50:59PM -0700, Bjorn Helgaas wrote:
> On Friday 13 January 2006 10:51, Bjorn Helgaas wrote:
> > Add lspnp support for sysfs. This makes it work with generic PNP
> > (including PNPACPI, PNPBIOS, ISAPNP) instead of just with PNPBIOS.
> > I'm particularly interested in ia64, which never has PNPBIOS, but
> > may have PNPACPI.
>
> Any more feedback on this? I'd like to see lspnp work again
> on modern systems, because it's so much easier to tell a user
> to run lspnp than it is to tell him how to grub around in
> /sys/bus/pnp/devices.
Personally, I think this would be really useful, and I agree asking users
to poke around sysfs can be difficult. I'd like to see it as a
seperate utility from the original lspnp included in pcmcia-cs (which
should actually be called "lspnpbios") as it can be handy for a different
sort of testing.
Thanks,
Adam
next prev parent reply other threads:[~2006-01-20 2:42 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-13 17:51 [RFC] Add lspnp support for sysfs Bjorn Helgaas
[not found] ` <200601131051.36906.bjorn.helgaas-VXdhtT5mjnY@public.gmane.org>
2006-01-13 18:02 ` Dominik Brodowski
[not found] ` <20060113180218.GA14129-JwFqNg2GrOVrgjWwlLH9qw@public.gmane.org>
2006-01-13 21:33 ` Bjorn Helgaas
2006-01-19 23:50 ` Bjorn Helgaas
2006-01-20 2:47 ` Adam Belay [this message]
2006-01-21 10:00 ` Komuro
2006-01-22 19:23 ` David Hinds
2006-01-31 17:07 ` Bjorn Helgaas
2006-01-31 17:46 ` matthieu castet
2006-02-01 5:59 ` David Hinds
2006-02-01 15:53 ` 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=20060120024731.GA27435@neo.rr.com \
--to=ambx1@neo.rr.com \
--cc=bjorn.helgaas@hp.com \
--cc=castet.matthieu@free.fr \
--cc=len.brown@intel.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-pcmcia@lists.infradead.org \
--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.