From: David Hawkins <dwh@ovro.caltech.edu>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] Proposal for a make option to include an additional stand alone program directory
Date: Thu, 26 Apr 2007 13:43:39 -0700 [thread overview]
Message-ID: <46310EFB.3020503@ovro.caltech.edu> (raw)
In-Reply-To: <20070426200258.465C5353414@atlas.denx.de>
Hi Wolfgang,
>> This sounds like a good idea. I am developing a custom MPC8349E
>> board that I'll submit a U-Boot patch for when its done.
>> I also plan to build a test-suite that executes as a u-boot
>> stand-alone application. Its not clear to me that such a test
>> suite should also be added into the U-Boot source, since its
>> board-specific; more so than whatever changes to the current
>
> If you are willing to release your code under GPL, it is definitely
> welcome to be added to the U-Boot source tree. In cases whwere this
> code is board-specific it makes sense to add it to the specfic board
> directory. Thi shas been done before in similar cases.
>
>> I figured I'd submit the board support patch, and then just
>> maintain the test-suite locally, with an email reference in a
>> u-boot README to anyone who wanted to get access to the
>> test-suite code. Of course, if lots of people build test
>> suites using U-Boot, and there is common code, I'd be happy
>> to use it. I just haven't looked for it in the source yet.
>
> There are several test utilities, but no general infrastructure yet.
Ok, good to know. That is the direction I will go once I get
back to the software design. I need to get the hardware done
first :)
Dave
next prev parent reply other threads:[~2007-04-26 20:43 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-26 17:15 [U-Boot-Users] Proposal for a make option to include an additional stand alone program directory Jeff Mann
2007-04-26 18:37 ` David Hawkins
2007-04-26 19:33 ` Jeff Mann
2007-04-26 20:02 ` Wolfgang Denk
2007-04-26 20:43 ` David Hawkins [this message]
2007-04-26 18:44 ` Timur Tabi
2007-04-26 19:13 ` Jeff Mann
2007-04-26 19:24 ` Timur Tabi
2007-04-26 20:10 ` Wolfgang Denk
2007-04-26 20:16 ` Timur Tabi
2007-04-26 20:31 ` Wolfgang Denk
2007-04-26 20:05 ` Wolfgang Denk
2007-04-26 20:09 ` Timur Tabi
2007-04-26 20:15 ` Wolfgang Denk
2007-04-26 20:19 ` Timur Tabi
2007-04-26 20:41 ` Wolfgang Denk
2007-04-26 20:53 ` Jerry Van Baren
2007-04-26 20:59 ` Timur Tabi
2007-04-27 9:38 ` Wolfgang Denk
2007-04-27 19:00 ` Timur Tabi
2007-04-27 19:32 ` Ulf Samuelsson
2007-04-27 20:13 ` Jerry Van Baren
2007-04-30 19:51 ` Wolfgang Denk
2007-04-30 19:45 ` Wolfgang Denk
2007-04-26 20:52 ` Ulf Samuelsson
2007-04-26 21:04 ` Timur Tabi
2007-04-27 7:45 ` Stefan Roese
2007-04-27 9:40 ` Wolfgang Denk
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=46310EFB.3020503@ovro.caltech.edu \
--to=dwh@ovro.caltech.edu \
--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 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.