All of lore.kernel.org
 help / color / mirror / Atom feed
From: Corey Minyard <minyard@acm.org>
To: Tom Rini <trini@kernel.crashing.org>
Cc: Keith Owens <kaos@ocs.com.au>, linux-kernel@vger.kernel.org
Subject: Re: Moving zlib so that others may use it
Date: Thu, 10 Jan 2002 10:20:47 -0600	[thread overview]
Message-ID: <3C3DBF5F.4070603@acm.org> (raw)
In-Reply-To: <3C3D1743.40900@acm.org> <24080.1010637887@kao2.melbourne.sgi.com> <20020110153657.GY13931@cpe-24-221-152-185.az.sprintbbd.net>

Tom Rini wrote:

>
>It's possible they can share, but the bootloaders (PPC & MIPS) need a
>slight change to the zlib.c code to to allow using zero as a real
>address to store the uncompressed data.  So we'd want to guard the
>changes with __BOOTER__ or so, and then cp the file or do
>#define __BOOTER__
>#include "zlib.c"
>
>And do -I$(TOPDIR)/lib, or something along those lines.
>

I agree, but I think it would be better to do this one step at a time. 
 Let's get the things in the kernel working first to get rid of the 
namespace crash, then get the bootloaders to share the code.  I can't 
test out a lot of the code, so I can't really do the bootloader changes, 
and the bootloader changes are completely independent, anyway, once zlib 
is moved.

-Corey



  reply	other threads:[~2002-01-10 16:19 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-09 23:32 Moving zlib so that others may use it Corey Minyard
2002-01-09 23:36 ` H. Peter Anvin
2002-01-10  1:52 ` Keith Owens
2002-01-10  4:23   ` Corey Minyard
2002-01-10  4:44     ` Keith Owens
2002-01-10  5:13       ` Corey Minyard
2002-01-10  5:40         ` Keith Owens
2002-01-10 10:55           ` Thomas Capricelli
2002-01-10 14:40             ` Corey Minyard
2002-01-10 15:22             ` Corey Minyard
2002-01-10  9:37         ` Zygo Blaxell
2002-01-10 15:30           ` Tom Rini
2002-01-10 15:36       ` Tom Rini
2002-01-10 16:20         ` Corey Minyard [this message]
2002-01-10 16:35           ` Tom Rini
2002-01-10  4:33   ` Corey Minyard
2002-01-10  6:08     ` H. Peter Anvin
2002-01-10 14:13   ` David Woodhouse

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=3C3DBF5F.4070603@acm.org \
    --to=minyard@acm.org \
    --cc=kaos@ocs.com.au \
    --cc=linux-kernel@vger.kernel.org \
    --cc=trini@kernel.crashing.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.