Subject: Re: npx0 not attaching with ACPI
To: Takayoshi Kochi <>
From: Quentin Garnier <>
List: current-users
Date: 02/01/2006 06:11:12
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Wed, Feb 01, 2006 at 02:00:20PM +0900, Takayoshi Kochi wrote:
> > > > Our current ACPI implementation consider the ACPI namespace flat, i=
t has
> > > > no knowledge of the ACPI device tree (*sigh*).
> > >=20
> > > I think we should have a new acpi bus driver which can be attached
> > > to its parent recursively.  When I have spare time, I'll look into
> > > it but anyone who can write such a driver is welcome ;)
> >=20
> > As I said, we currently consider the ACPI namespace flat, so it is not
> > needed.  We don't really have the autoconf(9) machinery ready for making
> > it useful to do it another way.
> Do you think the 'flat model' is ok in the long run?
> I don't, and probably you don't.

Indeed I don't.  I've made a few tries at it in the past;  I'm getting
close to the Right Way to Do It, but I'm still not there.  See for
example the post I made back in November about autoconf environment.

Quentin Garnier - -
"When I find the controls, I'll go where I like, I'll know where I want
to be, but maybe for now I'll stay right here on a silent sea."
KT Tunstall, Silent Sea, Eye to the Telescope, 2004.

Content-Type: application/pgp-signature
Content-Disposition: inline

Version: GnuPG v1.2.6 (NetBSD)