Hi,
attached patch makes coreboot_ram compression depending on CONFIG_COMPRESS again, instead of looking at the compression configuration for the payload
Build-tested (some coreboot_ram files were too large without compression for a full build, and now fit again)
Signed-off-by: Patrick Georgi patrick.georgi@coresystems.de
On Wed, Sep 30, 2009 at 1:41 PM, Patrick Georgi patrick@georgi-clan.de wrote:
Hi,
attached patch makes coreboot_ram compression depending on CONFIG_COMPRESS again, instead of looking at the compression configuration for the payload
Makes sense.
Build-tested (some coreboot_ram files were too large without compression for a full build, and now fit again)
Signed-off-by: Patrick Georgi patrick.georgi@coresystems.de
Acked-by: Myles Watson mylesgw@gmail.com
Thanks, Myles
Myles Watson wrote:
attached patch makes coreboot_ram compression depending on CONFIG_COMPRESS again, instead of looking at the compression configuration for the payload
Makes sense.
Is the uncompressor always available?
//Peter
Am Mittwoch, den 30.09.2009, 22:23 +0200 schrieb Peter Stuge:
Myles Watson wrote:
attached patch makes coreboot_ram compression depending on CONFIG_COMPRESS again, instead of looking at the compression configuration for the payload
Makes sense.
Is the uncompressor always available?
Yes, and even if not, that's what's CONFIG_COMPRESS is for, right? (otherwise: what would be the point of that variable?)
Patrick
Patrick Georgi wrote:
attached patch makes coreboot_ram compression depending on CONFIG_COMPRESS again, instead of looking at the compression configuration for the payload
Makes sense.
Is the uncompressor always available?
Yes, and even if not, that's what's CONFIG_COMPRESS is for, right?
Completely right. Great!
//Peter