From owner-freebsd-mobile Fri May 7 1: 7:32 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from herring.nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (Postfix) with ESMTP id D901B15E96 for ; Fri, 7 May 1999 01:07:25 -0700 (PDT) (envelope-from dfr@nlsystems.com) Received: from localhost (dfr@localhost) by herring.nlsystems.com (8.9.3/8.8.8) with ESMTP id JAA09642; Fri, 7 May 1999 09:07:39 +0100 (BST) (envelope-from dfr@nlsystems.com) Date: Fri, 7 May 1999 09:07:25 +0100 (BST) From: Doug Rabson To: Warner Losh Cc: new-bus-arch@bostonradio.org, mobile@freebsd.org Subject: Re: Pccard rewrite, patch #1 In-Reply-To: <199905070116.TAA20728@harmony.village.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Thu, 6 May 1999, Warner Losh wrote: > In message 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. I saw that too. It really does look quite useful. I have a test program which parses and decompiles all the AML in my laptop. I don't think that an implementation of the interpreter will be too hard. Slightly harder is implementing the ACPI event model and integrating ACPI hooks into the rest of the drivers but its all doable. > > 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... Me too. -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message