Date: Fri, 17 Jan 2003 15:36:25 -0800 From: Terry Lambert <tlambert2@mindspring.com> To: John Baldwin <jhb@FreeBSD.org> Cc: freebsd-current@FreeBSD.ORG, Nate Lawson <nate@root.org> Subject: Re: bad ACPL asl's on motherboards Message-ID: <3E289379.6473C66A@mindspring.com> References: <XFMail.20030117134210.jhb@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
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 parser? If not, then put up or > shut up. It's not exactly a trivial task. This was in the context of a discussion about what could be done about the problem. It's really the original poster you should be asking to write code. That's basically what I was doing (asking him to write the code) by posting the list of available options. I was under the impression that the Intel ACPI parser was source code? So what we're really talking about here is taking over the maintenance of, and forking, the Intel code, unless you think Microsoft wrote their code from scratch... In any case, for anything for which there is a specification, was long as the specification is complete, implementation is really pretty trivial. If you're serious about such a project, and you are willing to dual-license the code, and you have access to the specifications without non-disclosure being required, and you will provide them or they are not very expensive, you can count me in on joining your project. -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3E289379.6473C66A>