Re: bad ACPL asl's on motherboards

2003-01-18 Thread Gavin Atkinson
On Thu, 16 Jan 2003, David O'Brien wrote: I'm convinced that if we are going to keep insisting that ACPI is enabled by default, we need to gather the various fixed AML's and commit them to the tree. I can't decide if they should be ports, or in /usr/src. What are the copyright issues

Re: bad ACPL asl's on motherboards

2003-01-17 Thread John Baldwin
On 16-Jan-2003 Terry Lambert wrote: Joel M. Baldwin wrote: I gather that there are quite a few Motherboards with bad ACPI asl's on them. I know that my Abit BP6 sure has problems. As a result I can't run ACPI. What are those of us with these motherboards supposed to to? I realize that

Re: bad ACPL asl's on motherboards

2003-01-17 Thread John Baldwin
On 16-Jan-2003 Terry Lambert wrote: Nate Lawson wrote: On Thu, 16 Jan 2003, Terry Lambert wrote: Repeat: These machines work fine under Windows; the problem is not the BIOS, it's the OS's ASL interpreter. There's another wrinkle in that the interpreter is supplied by Intel. Some

Re: bad ACPL asl's on motherboards

2003-01-17 Thread Peter Schultz
John Baldwin wrote: On 16-Jan-2003 Terry Lambert wrote: Joel M. Baldwin wrote: I gather that there are quite a few Motherboards with bad ACPI asl's on them. I know that my Abit BP6 sure has problems. As a result I can't run ACPI. What are those of us with these motherboards supposed to to?

Re: bad ACPL asl's on motherboards

2003-01-17 Thread John Baldwin
On 17-Jan-2003 Peter Schultz wrote: John Baldwin wrote: On 16-Jan-2003 Terry Lambert wrote: Joel M. Baldwin wrote: I gather that there are quite a few Motherboards with bad ACPI asl's on them. I know that my Abit BP6 sure has problems. As a result I can't run ACPI. What are those

Re: bad ACPL asl's on motherboards

2003-01-17 Thread Terry Lambert
John Baldwin wrote: For Intel, this is a win-win. For FreeBSD, unless Windows adopts the same code (which it will not do, since doing so will limit their market, just as using the code is currently limiting FreeBSD's market), it's a lose-lose. Are you offering to write a new ACPI

Re: bad ACPL asl's on motherboards

2003-01-17 Thread John Baldwin
On 17-Jan-2003 Terry Lambert wrote: John Baldwin wrote: For Intel, this is a win-win. For FreeBSD, unless Windows adopts the same code (which it will not do, since doing so will limit their market, just as using the code is currently limiting FreeBSD's market), it's a lose-lose. Are

bad ACPL asl's on motherboards

2003-01-16 Thread Joel M. Baldwin
I gather that there are quite a few Motherboards with bad ACPI asl's on them. I know that my Abit BP6 sure has problems. As a result I can't run ACPI. What are those of us with these motherboards supposed to to? I realize that we can use acpidump to get the asl, correct it, and then recompile

RE: bad ACPL asl's on motherboards

2003-01-16 Thread Cagle, John (ISS-Houston)
- From: Joel M. Baldwin [mailto:[EMAIL PROTECTED]] Sent: Thursday, January 16, 2003 8:08 AM To: [EMAIL PROTECTED] Subject: bad ACPL asl's on motherboards I gather that there are quite a few Motherboards with bad ACPI asl's on them. I know that my Abit BP6 sure has problems

Re: bad ACPL asl's on motherboards

2003-01-16 Thread Ducrot Bruno
On Thu, Jan 16, 2003 at 08:44:20AM -0600, Cagle, John (ISS-Houston) wrote: You might ask that question on the ACPI development list. I think there are several people who have contributed patched ASL's for machines that are broken. Here's a link: Acpi-devel mailing list [EMAIL PROTECTED]

Re: bad ACPL asl's on motherboards

2003-01-16 Thread David O'Brien
[From address modified because I don't want every message in this thread to end up in my personal mailbox. I'll read them in the list, thank you.] On Thu, Jan 16, 2003 at 06:07:45AM -0800, Joel M. Baldwin wrote: I gather that there are quite a few Motherboards with bad ACPI asl's on them. I

Re: bad ACPL asl's on motherboards

2003-01-16 Thread Ducrot Bruno
On Thu, Jan 16, 2003 at 07:35:35AM -0800, David O'Brien wrote: On Thu, Jan 16, 2003 at 06:07:45AM -0800, Joel M. Baldwin wrote: I gather that there are quite a few Motherboards with bad ACPI asl's on them. I know that my Abit BP6 sure has problems. As a result I can't run ACPI. What

Re: bad ACPL asl's on motherboards

2003-01-16 Thread Nate Lawson
On Thu, 16 Jan 2003, Ducrot Bruno wrote: It sound like a good idea. However, there is a lot of isssues evolved. First, a DSDT table can and will be generated autmatically on the POST, because at least the memory controller can have different configurations depending on the total amount of the

Re: bad ACPL asl's on motherboards

2003-01-16 Thread Ducrot Bruno
On Thu, Jan 16, 2003 at 09:46:46AM -0800, Nate Lawson wrote: On Thu, 16 Jan 2003, Ducrot Bruno wrote: It sound like a good idea. However, there is a lot of isssues evolved. First, a DSDT table can and will be generated autmatically on the POST, because at least the memory controller can

Re: bad ACPL asl's on motherboards

2003-01-16 Thread Terry Lambert
Joel M. Baldwin wrote: I gather that there are quite a few Motherboards with bad ACPI asl's on them. I know that my Abit BP6 sure has problems. As a result I can't run ACPI. What are those of us with these motherboards supposed to to? I realize that we can use acpidump to get the asl,

Re: bad ACPL asl's on motherboards

2003-01-16 Thread Terry Lambert
Cagle, John (ISS-Houston) wrote: You might ask that question on the ACPI development list. I think there are several people who have contributed patched ASL's for machines that are broken. Here's a link: Acpi-devel mailing list [EMAIL PROTECTED]

Re: bad ACPL asl's on motherboards

2003-01-16 Thread Nate Lawson
On Thu, 16 Jan 2003, Terry Lambert wrote: Cagle, John (ISS-Houston) wrote: You might ask that question on the ACPI development list. I think there are several people who have contributed patched ASL's for machines that are broken. Here's a link: Acpi-devel mailing list [EMAIL

Re: bad ACPL asl's on motherboards

2003-01-16 Thread Terry Lambert
Nate Lawson wrote: On Thu, 16 Jan 2003, Terry Lambert wrote: Repeat: These machines work fine under Windows; the problem is not the BIOS, it's the OS's ASL interpreter. There's another wrinkle in that the interpreter is supplied by Intel. Some difficulties were _introduced_ by them,