Re: ACPI DSDT

2004-06-03 Thread Eric W. Biederman
Stefan Reinauer <[EMAIL PROTECTED]> writes: > Standards are a fine thing. Let's have everybody implement it's own. One thing about EFI that really sucks is that it is just absolutely chock full of pointers in it's interfaces. Which makes it extremely ugly to support on platforms with both a 32/6

Re: ACPI DSDT

2004-06-02 Thread Adam Sulmicki
also, one of the huge advantages of the linuxBIOS Is that it allows to workaround bugs in the hardware and firmware. If we decide to go with Tiano's hardware startup code we lose some of this flexibility. something to keep in mind. it reminds me all the nightmare linux has with its binary only mo

Re: ACPI DSDT

2004-06-02 Thread ron minnich
On 1 Jun 2004, Eric W. Biederman wrote: > The alpha port worked but it is not something I savor repeating, > there were too many real limitations. yes, but by golly we sure got some use out of it! We appreciated your work :-) > There are some things that I find strongly architecturally question

Re: ACPI DSDT

2004-06-02 Thread ron minnich
On 1 Jun 2004, Eric W. Biederman wrote: > That Intel will be releasing code is new, although there have been some > sympathies in that direction. I'm really not interested until they actually > release something. Should probably also mention: there's lots of binary in this EFI/Tiano thing. Bina

Re: ACPI DSDT

2004-06-02 Thread Eric W. Biederman
Stefan Reinauer <[EMAIL PROTECTED]> writes: > Hi, > > * Eric W. Biederman <[EMAIL PROTECTED]> [040602 06:33]: > > We certainly need to provide this information, as all motherboard > > specific information is the province of the motherboard firmware. > > However I'm not at all convinced that the A

Re: ACPI DSDT

2004-06-02 Thread Stefan Reinauer
* Steve Gehlbach <[EMAIL PROTECTED]> [040602 00:35]: > > Speaking of ACPI and problems, which are commented on in this article, > is this Intel announcement of open sourcing the BIOS something new? > > http://news.com.com/Intel+to+open+code+for+booting+up+PCs%2C+servers/2100-7337_3-5223860.html?

Re: ACPI DSDT

2004-06-02 Thread Stefan Reinauer
Hi, * Eric W. Biederman <[EMAIL PROTECTED]> [040602 06:33]: > We certainly need to provide this information, as all motherboard > specific information is the province of the motherboard firmware. > However I'm not at all convinced that the ACPI tables are the right > approach. Can you go a bit i

Re: ACPI DSDT

2004-06-01 Thread Eric W. Biederman
ron minnich <[EMAIL PROTECTED]> writes: > Worked fine. The alpha port worked but it is not something I savor repeating, there were too many real limitations. There are some things that I find strongly architecturally questionable about Tiano, in the context of Intel hardware. Unfortunately neit

Re: ACPI DSDT

2004-06-01 Thread Eric W. Biederman
Stefan Reinauer <[EMAIL PROTECTED]> writes: > Hi, > > one thing that is generically missing in LinuxBIOS' ACPI implementation > is the detailed system description table (DSDT The part telling whether > there is a lid and how detect whether it is open or closed) > > The DSDT is written in ASL wh

Re: ACPI DSDT

2004-06-01 Thread Eric W. Biederman
Steve Gehlbach <[EMAIL PROTECTED]> writes: > ron minnich wrote: > > > acpi is a big problem, partly due to the binary nature and partly because it > > is so broken on so many platforms. > > > >ron > > > > Speaking of ACPI and problems, which are commented on in this article, is this > Intel anno

Re: ACPI DSDT

2004-06-01 Thread ron minnich
On Tue, 1 Jun 2004, Bari Ari wrote: > Here's the official Intel statement: > > http://www.intel.com/pressroom/archive/releases/20040601corp_a.htm gee, no mention of linuxbios :-) ron ___ Linuxbios mailing list [EMAIL PROTECTED] http://www.clustermati

Re: ACPI DSDT

2004-06-01 Thread ron minnich
On Tue, 1 Jun 2004, Steve Gehlbach wrote: > Speaking of ACPI and problems, which are commented on in this article, > is this Intel announcement of open sourcing the BIOS something new? > > http://news.com.com/Intel+to+open+code+for+booting+up+PCs%2C+servers/2100-7337_3-5223860.html?tag=nefd.top

Re: ACPI DSDT

2004-06-01 Thread Bari Ari
Here's the official Intel statement: http://www.intel.com/pressroom/archive/releases/20040601corp_a.htm -Bari Steve Gehlbach wrote: ron minnich wrote: acpi is a big problem, partly due to the binary nature and partly because it is so broken on so many platforms. ron Speaking of ACPI and proble

Re: ACPI DSDT

2004-06-01 Thread Steve Gehlbach
ron minnich wrote: acpi is a big problem, partly due to the binary nature and partly because it is so broken on so many platforms. ron Speaking of ACPI and problems, which are commented on in this article, is this Intel announcement of open sourcing the BIOS something new? http://news.com.co

Re: ACPI DSDT

2004-06-01 Thread ron minnich
or you can translate the acpi tables to Something Else (e.g. e-expressions -- it works) and use that instead. acpi is a big problem, partly due to the binary nature and partly because it is so broken on so many platforms. ron ___ Linuxbios mailing l

Re: ACPI DSDT

2004-06-01 Thread Bari Ari
Stefan Reinauer wrote: Hi, one thing that is generically missing in LinuxBIOS' ACPI implementation is the detailed system description table (DSDT The part telling whether there is a lid and how detect whether it is open or closed) The DSDT is written in ASL which is compiled to AML bytecode using

ACPI DSDT

2004-06-01 Thread Stefan Reinauer
Hi, one thing that is generically missing in LinuxBIOS' ACPI implementation is the detailed system description table (DSDT The part telling whether there is a lid and how detect whether it is open or closed) The DSDT is written in ASL which is compiled to AML bytecode using an ASL compiler (ie.