From: Marc Singer <elf@buici.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] Preparing a KEV7a400 patch
Date: Wed, 6 Aug 2003 12:16:35 -0700 [thread overview]
Message-ID: <20030806191635.GA2601@buici.com> (raw)
I've successfully ported u-boot to the Sharp KEV7A400 board. It can
program flash, boot from the network, and it runs from flash.
Before I submit a patch, I believe there are a couple of outstanding
issues that you, Wolfgang, want resolved.
1) Dependency on Perl
Are you OK with an initial patch that checks for the presence of a
Perl interpreter? Since this is the only board using the
mkocnfigx script, such a method will be backward compatible. I
agree that a shell script of the Perl script must be written.
2) #undef arm
It looks like the arm macro may be defined by the compiler. The
GCC info pages suggest that this macro may be defined unless
-ansi is passed to the compiler.
There are a few of ways to resolve this problem. I could
change the structure that is broken by the #define. I could leave
the #undef intact. I could find a way to remove the #define by
passing an switch to the compiler. My preference, of course, is
to leave the #undef intact.
3) Trailing whitespace
You found some lines in a previous patch to have trailing
whitespace. What do you use to detect this?
next reply other threads:[~2003-08-06 19:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-06 19:16 Marc Singer [this message]
2003-08-06 22:22 ` [U-Boot-Users] Preparing a KEV7a400 patch Wolfgang Denk
2003-08-06 22:34 ` Marc Singer
2003-08-06 23:30 ` Wolfgang Denk
2003-08-07 0:47 ` Marc Singer
2003-08-07 12:51 ` Wolfgang Denk
2003-08-07 17:54 ` Marc Singer
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=20030806191635.GA2601@buici.com \
--to=elf@buici.com \
--cc=u-boot@lists.denx.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