From: Tom Rini <trini@kernel.crashing.org>
To: andrew may <acmay@acmay.homeip.net>
Cc: linuxppc-embedded@lists.linuxppc.org, Armin <akuster@pacbell.net>
Subject: Re: [PATCH] another for ibm_ocp_enet gzip'd
Date: Fri, 15 Mar 2002 13:05:58 -0700 [thread overview]
Message-ID: <20020315200558.GG691@opus.bloom.county> (raw)
In-Reply-To: <20020315114137.A26609@ecam.san.rr.com>
On Fri, Mar 15, 2002 at 11:41:37AM -0800, andrew may wrote:
> 3. added mal.sh to generate a new ibm_ocp_mal.c
> mal.sh DCRN_MAL_BASE >ibm_ocp_mal.c
> or mal.sh DCRN_MAL_BASE DCRN_MAL1_BASE >ibm_ocp_mal.c
> will work. It seems that the second on generates a smaller
> object file even though the code is bigger for the 405GP.
> I would think it is because MAL1 is 0.
> This condenses all the get/set mal calls into one for get
> and one for set. I also changed mal_num to mal, just to help
> me find/change things.
>
> I think this is a better approach than what was in the _mal.c,
> but I didn't change the makefile to generate the code on the
> fly yet.
This looks very cool. Can you add in some comments to the shell script,
and I didn't see any bashisms in there, can you verify it works with
pdksh or one of the other script shells which can be /bin/sh ?
--
Tom Rini (TR1265)
http://gate.crashing.org/~trini/
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2002-03-15 20:05 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-15 19:41 [PATCH] another for ibm_ocp_enet gzip'd andrew may
2002-03-15 20:05 ` Tom Rini [this message]
2002-03-15 22:25 ` andrew may
2002-03-15 22:31 ` Tom Rini
2002-03-18 22:25 ` andrew may
2002-03-18 14:53 ` Armin
2002-03-18 22:56 ` andrew may
2002-03-19 0:28 ` Tom Rini
2002-03-19 0:54 ` andrew may
2002-03-19 1:01 ` Tom Rini
2002-03-15 20:06 ` Tom Rini
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=20020315200558.GG691@opus.bloom.county \
--to=trini@kernel.crashing.org \
--cc=acmay@acmay.homeip.net \
--cc=akuster@pacbell.net \
--cc=linuxppc-embedded@lists.linuxppc.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;
as well as URLs for NNTP newsgroup(s).