Date: Sat, 6 Sep 2003 10:51:37 -0700 (PDT) From: Nate Lawson <nate@root.org> To: Peter Jeremy <peterjeremy@optushome.com.au> Cc: freebsd-stable@freebsd.org Subject: Re: ACPI utilities Message-ID: <20030906104948.R78425@root.org> In-Reply-To: <20030905083734.GA2834@server.c20257.belrs2.nsw.optusnet.com.au> References: <20030905083734.GA2834@server.c20257.belrs2.nsw.optusnet.com.au>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, 5 Sep 2003, Peter Jeremy wrote:
> I have an Athlon system which isn't co-operating with the ACPI in
> -stable (I haven't tried -current yet). I notice that the general
> recommendation in -current is to provide the output of acpidump but
> none of the ACPI userland has been MFC'd.
I'm sorry, I can't support acpi on -stable. Someone else may.
> I just had a quick try and building the -current userland on -stable
> and found this is non-trivial because it appears that the APIs are
> different between the two versions - AcpiOs{Read,Write}{Port,Memory}()
> have different prototypes.
>
> Any suggestions on the way forward?
-stable has 0228, -current is 0619. You can manually import the tools by
hacking the header files. A better approach would be to boot the 5.1 live
filesystem image and use acpidump from there.
-Nate
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030906104948.R78425>