From: Geoffrey Espin <espin@idiom.com>
To: Pete Popov <ppopov@mvista.com>
Cc: linux-mips-kernel@lists.sourceforge.net, linux-mips@oss.sgi.com
Subject: Re: [Linux-mips-kernel]PATCH
Date: Fri, 19 Oct 2001 10:27:49 -0700 [thread overview]
Message-ID: <20011019102749.B36916@idiom.com> (raw)
In-Reply-To: <1003471921.1184.4.camel@adsl.pacbell.net>; from Pete Popov on Thu, Oct 18, 2001 at 11:12:01PM -0700
Pete,
> I ported the code from arch/ppc/boot, so if you like that scheme, what
> is it that you don't like about the patch I sent? The directory
> structure is the same as arch/ppc/boot, and the generic code is the same
> as well.
I see that PPC now has some of the silly utils where $(shell
objdump ...) in the Makefile would be a lot tighter. Other
superficial but better ways like subdir-$(CONFIG_<board>) are
not used (instead ifdef CONFIG_NEC_PB100 $MAKE -- ugh!). Not
sure why using CFLAGS/LOADADDR/.. from arch/mips/Makefile is not
done either... dup'ing this is bad. Use "override CFLAGS" if it
needs to be re-constructed from GCCFLAGS,CPPFLAGS...
Apologies for playing "armchair coder". I'll try to create Korva
version... but mine does it without benefit of a separate loader
(standalone vrboot style)... which might be a useful standard
build option.
Seems to me this is way more important than vrxx stuff... which
is already done and over... compression/initrd is in its infancy.
Geoff
--
Geoffrey Espin espin@idiom.com
next prev parent reply other threads:[~2001-10-19 17:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3BC24525.8030201@mvista.com>
2001-10-16 18:50 ` [Linux-mips-kernel]PATCH Geoffrey Espin
2001-10-19 6:12 ` [Linux-mips-kernel]PATCH Pete Popov
2001-10-19 17:27 ` Geoffrey Espin [this message]
2001-10-19 18:13 ` [Linux-mips-kernel]PATCH Pete Popov
2001-10-19 23:58 ` [Linux-mips-kernel]PATCH Keith Owens
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=20011019102749.B36916@idiom.com \
--to=espin@idiom.com \
--cc=linux-mips-kernel@lists.sourceforge.net \
--cc=linux-mips@oss.sgi.com \
--cc=ppopov@mvista.com \
/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