public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Dmitry Torokhov <dtor_core-yWtbtysYrB+LZ21kGMrzwg@public.gmane.org>
To: "Keshavamurthy,
	Anil S"
	<anil.s.keshavamurthy-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Cc: "Brown, Len" <len.brown-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>,
	ACPI Developers
	<acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>
Subject: Re: [PATCH 1/4] properly create kobjects in acpi/scan.c
Date: Tue, 24 Aug 2004 17:45:38 -0500	[thread overview]
Message-ID: <200408241745.38898.dtor_core@ameritech.net> (raw)
In-Reply-To: <44BDAFB888F59F408FAE3CC35AB47041A3B61B@orsmsx409>

On Tuesday 24 August 2004 04:45 pm, Keshavamurthy, Anil S wrote:
> 
> >> Btw, why don't we just convert ACPI to be standard driver core bus 
> >> with standard drivers and devices? I could cook up something... The 
> >> /sys/firmware/acpi hierarchy is not populated with any 
> >useful data yet 
> >> so there should be no concern of breakign userspace interface (I am 
> >> mot talking about removing /proc/acpi part at the moment).
> >
> >Funny you should mention it.
> >
> >My current opinion is that /sys/firmware/acpi should probably 
> >not exist at all, and that there should be a single 
> >/sys/devices including both ACPI-enumerated and pci-enumerated 
> >devices.  Adam and I have been ganging up on Patrick on this, 
> >but we don't have him convinced yet...
> >
> For my hotplug work I am currently banking on
> /sys/firmware/acpi/namespace/ACPI
>  to find the all the children devices and from there to find the
> corresponding logical
>  devices. Once I find the all child devices then the scripts would turn
> online or offline of all the child devices.
> 
> If we are proposing to eliminate /sys/firmware/acpi can anyone pass a
> pointer to the above discussion.
>

We would not eliminate it, it would naturally move to something like

/sys/bus/acpi/devices/acpi_root/... and  /sys/devices/acpi_root/...

Or something along these lines.

-- 
Dmitry


-------------------------------------------------------
SF.Net email is sponsored by Shop4tech.com-Lowest price on Blank Media
100pk Sonic DVD-R 4x for only $29 -100pk Sonic DVD+R for only $33
Save 50% off Retail on Ink & Toner - Free Shipping and Free Gift.
http://www.shop4tech.com/z/Inkjet_Cartridges/9_108_r285

  reply	other threads:[~2004-08-24 22:45 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-24 21:45 [PATCH 1/4] properly create kobjects in acpi/scan.c Keshavamurthy, Anil S
2004-08-24 22:45 ` Dmitry Torokhov [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-08-24 22:47 Keshavamurthy, Anil S
2004-08-24  6:34 Dmitry Torokhov
     [not found] ` <200408240134.16962.dtor_core-yWtbtysYrB+LZ21kGMrzwg@public.gmane.org>
2004-08-24 15:23   ` Hiroshi Miura
     [not found]     ` <87zn4ky2zr.wl%miura-yiisDzvROlQdnm+yROfE0A@public.gmane.org>
2004-08-24 16:15       ` Mattia Dongili
2004-08-24 17:03       ` Dmitry Torokhov
2004-08-24 19:50   ` 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=200408241745.38898.dtor_core@ameritech.net \
    --to=dtor_core-ywtbtysyrb+lz21kgmrzwg@public.gmane.org \
    --cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
    --cc=anil.s.keshavamurthy-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
    --cc=len.brown-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