Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 06 May 1999 19:16:51 -0600
From:      Warner Losh <imp@harmony.village.org>
To:        Doug Rabson <dfr@nlsystems.com>
Cc:        new-bus-arch@bostonradio.org, mobile@freebsd.org
Subject:   Re: Pccard rewrite, patch #1 
Message-ID:  <199905070116.TAA20728@harmony.village.org>
In-Reply-To: Your message of "Thu, 06 May 1999 21:37:16 BST." <Pine.BSF.4.05.9905062135550.411-100000@herring.nlsystems.com> 
References:  <Pine.BSF.4.05.9905062135550.411-100000@herring.nlsystems.com>  

next in thread | previous in thread | raw e-mail | index | archive | help
In message <Pine.BSF.4.05.9905062135550.411-100000@herring.nlsystems.com> Doug Rabson writes:
: This should be doable - the newconfig folks have code to talk to the PCI
: BIOS. In the long term, ACPI will also provide this kind of access without
: having to call any bios functions.

ACPI looks very promising.  Looks like it attempts to move the
management of many things into a p-code like machine.  The machine
appears to be relatively simple.  I'm not aware of any good (or bad
for that matter) AML implementations that are freely available.

If you read the spec carefully, you'll note that they leave the door
open for ACPI impelementations on non-x86 architectures.

The newconfig code has support for cardbus bridges.  I've not looked
closely at what they offer, however.

I know that on my laptop it makes a difference between having PnP OS
set to Y and N.  With it set to 'Y,' almost nothing is configured (which
is correct, per the pnp spec) and it is hard to get things working.
When it is set to 'N,' then it appears to assign all the chips on the
PCI bus to the int-a irq 9.  But then again, PCI interrupt routing has
always been a confusing thing to me...

Warner


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-mobile" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199905070116.TAA20728>