Re: [ACPI] Re: [ACPI-sppt] supported machines

hi karol..

* Karol Kozimor <[email protected]> [2003-06-16 09:06 +0200]:
> Thus wrote Sebastian Henschel:
> > well, if any manufacturer reads this, please raise your voice. :)
> > only including patches whould also have a technical benefit: the file
> > sizes would become smaller.
> > so if you found some more supporters, i would update the pages, files and
> > database as good as i can. the downside is that i cannot generate a diff
> > from the DSTDs where there is no "original" table provided.
> 
> On the other hand, having the DSDT's in one place is very handy and helps
> in driver development. At least, we used the database frequently with
> Julien, and handling the development without it would be much less
> convenient.

you mean you looked into the DSDTs of machines you did not have at hand?
valid point, i think.

another problem i found with diffs is the following:
we have no "real" source code of the table. what we have is some binary
file where we run a tool for disassembly on. _most_ people use iasl, but
do they all do? and apart from that, perhaps different versions of the same
tool produce different ASL code. so it is quite possible that a patch
can fail, which can be a trivial... or something more sophisticated.

> Does file size (we're talking kilobytes of gzipped data) really
> matter anyway?

well, one archive of DSDTS is about 590k (40k DB) at the moment. this
surely does not matter. but due to constraints of sf.net i had to
install a little backup scheme which accumulates that amount of data for
each day. i usually download the backups once or twice a week and delete
them on sf.net afterwards. since we have 100MB available on sf.net, it
should not be a problem for now. but the backup scheme must be slowed
down when i am away from internet for a couple of weeks. so no, it does
not matter that much, just a little.

ok, i suggest to put the discussion back on acpi-support only, since no
big discussion has arisen on acpi-devel, but they know about it. :)

cheers,
 sebastian
-- 
::: sebastian henschel
::: kodeaffe
::: lynx -source http://www.kodeaffe.de/shensche.pub | gpg --import

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)

iD8DBQE+7XXwreHfL3pi+bQRArjMAKCE9ithy7besktob9n/kvDnX+Rc2QCgkq6B
VAfGBw8fo57uDdtHgddLtbU=
=x8Ax
-----END PGP SIGNATURE-----