<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
On 12.03.2009 18:41 Uhr, Peter Stuge wrote:
<blockquote cite="mid:20090312174126.31038.qmail@stuge.se" type="cite">
<pre wrap="">Stefan Reinauer wrote:
</pre>
<blockquote type="cite">
<blockquote type="cite">
<pre wrap="">Maybe would be better to have ACPI minimalistic, but usable.
</pre>
</blockquote>
<pre wrap="">Which parts are not usable?
</pre>
</blockquote>
<pre wrap=""><!---->
I think the intention was "the bare minimum" - as it stands that ACPI
implementation is a bit, eh, fat.
</pre>
</blockquote>
Again. Which parts? What's fat? How would you solve things differently?
Without wiping features that upcoming ports _are_ going to use?<br>
<br>
Some analysis shows:<br>
- AMD serengeti cheetah has 1500 lines of mainboard specific code and
330 lines of chipset specific code.<br>
- Kontron 986LCD-M has 1800 lines of southbridge specific code, 400
lines of northbridge specific code and 500 lines of mainboard specific
code.<br>
<br>
So the mainboard specific stuff is 1/3 of that of a typical K8/K10
mainboard. Is that really too fat?<br>
The whole implementation is 50% bigger than the one on K8/K10 in lines
of code. <br>
<br>
It does a lot more, too. The final thing is going to do PCIe hotplug,
laptop brightness control, vga output switching, etc.<br>
<br>
I'm very willing to work with you guys on making this appealing to
everyone. But your comments have not been extraordinarily helpful so
far, I'm very sorry to say that.<br>
<br>
<blockquote cite="mid:20090312174126.31038.qmail@stuge.se" type="cite">
<pre wrap="">I have to say it's the most readable ASL I've seen though.
Some of the fat could go into mainboard specific ASL rather than have
everything in the chipset dirs. But maybe that's a bad idea?</pre>
</blockquote>
<br>
The opposite. Some of the mainboard stuff actually needs to go to the
component directories (like superio)<br>
<br>
I don't think it makes much sense to go from a nice and modular
implementation to a spaghetti code all duplicate mainboard centered one
to safe 20 bytes of asl on a platform that might not necessarily need
it.<br>
<br>
<blockquote cite="mid:20090312174126.31038.qmail@stuge.se" type="cite">
<pre wrap="">It does
go against my idea of keeping code out of the mainboard dir..
</pre>
</blockquote>
Absolutely. The mainboard directory should be selecting and configuring
components and be otherwise empty.<br>
<br>
<br>
<br>
<pre class="moz-signature" cols="72">--
coresystems GmbH • Brahmsstr. 16 • D-79104 Freiburg i. Br.
Tel.: +49 761 7668825 • Fax: +49 761 7664613
Email: <a class="moz-txt-link-abbreviated" href="mailto:info@coresystems.de">info@coresystems.de</a> • <a class="moz-txt-link-freetext" href="http://www.coresystems.de/">http://www.coresystems.de/</a>
Registergericht: Amtsgericht Freiburg • HRB 7656
Geschäftsführer: Stefan Reinauer • Ust-IdNr.: DE245674866
</pre>
</body>
</html>