From: Tom Rini <trini@kernel.crashing.org>
To: Arjan van de Ven <arjanv@redhat.com>
Cc: Olaf Hering <olh@suse.de>, Andrew Morton <akpm@osdl.org>,
linux-kernel@vger.kernel.org, linuxppc-dev@lists.linuxppc.org
Subject: Re: [PATCH] fix zlib debug in ppc boot header
Date: Wed, 28 Jul 2004 08:01:45 -0700 [thread overview]
Message-ID: <20040728150145.GK10891@smtp.west.cox.net> (raw)
In-Reply-To: <1091014495.2795.25.camel@laptop.fenrus.com>
[-- Attachment #1: Type: text/plain, Size: 892 bytes --]
On Wed, Jul 28, 2004 at 01:34:55PM +0200, Arjan van de Ven wrote:
> On Wed, 2004-07-28 at 13:22, Olaf Hering wrote:
> > The ppc bootloader code will not compile with zlib debug enabled.
> > printf was not defined. Tested with vmlinux.coff
> > This patch was sent out earlier. Appearently it is not possible
> > to use the generic zlib copy in linux/lib
>
> actually it should be possible. Ok so it needs to be compiled as 32 bit,
> but surely just #include-ing the /linux/lib version, or even better, a
> few Makefile tricks should allow that, right ?
Arjan is correct, it should be very possible to use the copy in
lib/zlib_deflate as mpm had patches at one point to do just this.
Further, I'd rather leave the zlib debug stuff as is in arch/ppc/boot.
Olaf, has having this code work for you ever been useful? Thanks.
--
Tom Rini
http://gate.crashing.org/~trini/
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2004-07-28 15:02 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-28 11:22 Olaf Hering
2004-07-28 11:34 ` Arjan van de Ven
2004-07-28 15:01 ` Tom Rini [this message]
2004-07-28 15:36 ` Olaf Hering
2004-07-28 23:06 ` Tom Rini
2004-07-29 6:48 ` Olaf Hering
2004-07-28 15:18 ` Geert Uytterhoeven
2004-07-28 15:29 ` Tom Rini
2004-07-28 17:42 ` Sam Ravnborg
2004-07-28 15:56 ` Tom Rini
2004-07-28 18:18 ` Sam Ravnborg
2004-07-28 16:39 ` Tom Rini
2004-07-28 16:47 ` Jörn Engel
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=20040728150145.GK10891@smtp.west.cox.net \
--to=trini@kernel.crashing.org \
--cc=akpm@osdl.org \
--cc=arjanv@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=olh@suse.de \
/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
all inboxes | Powered by JetHome®