public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Wakko Warner <wakko@animx.eu.org>
To: Ondrej Zary <linux@rainbow-software.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Booting uncompressed kernel image on i386?
Date: Fri, 1 Jul 2005 18:16:17 -0400	[thread overview]
Message-ID: <20050701221617.GA16873@animx.eu.org> (raw)
In-Reply-To: <42C5BB4E.2040000@rainbow-software.org>

Ondrej Zary wrote:
> Nobody answered, time to look at the code :-)
> The attached patch is a quick hack so "make" will create uncompressed 
> kernel that can be booted in regular way.

> --- linux-2.6.12-printserver/arch/i386/boot/compressed/misc.c	2005-06-17 21:48:29.000000000 +0200
> +++ linux-2.6.12-pentium/arch/i386/boot/compressed/misc.c	2005-07-01 23:34:55.000000000 +0200
> @@ -374,7 +374,15 @@
>  
>  	makecrc();
>  	putstr("Uncompressing Linux... ");

Would it not make sense to remove the above line?  You're not actually
uncompressing anything.

> -	gunzip();
> +	int i;
> +	for (i = 0; i < input_len / WSIZE; i++) {
> +		memcpy(window, input_data+i*WSIZE, WSIZE);
> +		outcnt = WSIZE;
> +		flush_window();
> +	}
> +	memcpy(window, input_data+i*WSIZE, input_len % WSIZE);
> +	outcnt = input_len % WSIZE;
> +	flush_window();
>  	putstr("Ok, booting the kernel.\n");
>  	if (high_loaded) close_output_buffer_if_we_run_high(mv);
>  	return high_loaded;

-- 
 Lab tests show that use of micro$oft causes cancer in lab animals

  reply	other threads:[~2005-07-01 22:04 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-28 12:00 Booting uncompressed kernel image on i386? Ondrej Zary
2005-07-01 21:53 ` Ondrej Zary
2005-07-01 22:16   ` Wakko Warner [this message]
2005-07-01 22:18     ` Ondrej Zary

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20050701221617.GA16873@animx.eu.org \
    --to=wakko@animx.eu.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@rainbow-software.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox