From: Stephen Williams <gfi8d1h02@sneakemail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] Updates to u-boot
Date: Wed, 04 Feb 2004 12:21:50 -0800 [thread overview]
Message-ID: <11277-50845@sneakemail.com> (raw)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
What's the best way to get new support added into the u-boot
source tree? I have fat on my SystemACE chip working, and would
like to get it into the main branch. Should I send patches to
the list, or to a specific person?
Also, I'm porting to a new PPC board we're developing. I'm fine
with adding the board support files for that board to the source
tree as well, but we're not talking about a high volume board
here. What's the word on adding vendor/board specific code to
the tree?
- --
Steve Williams "The woods are lovely, dark and deep.
steve at icarus.com But I have promises to keep,
http://www.icarus.com and lines to code before I sleep,
http://www.picturel.com And lines to code before I sleep."
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFAIVRerPt1Sc2b3ikRAlr/AKCx0j5GV9DYMhfh8YSEEYZJaq1XWwCg7WMq
3AMUKmb5uw5aza07HDbT5oY=
=ZSHV
-----END PGP SIGNATURE-----
next reply other threads:[~2004-02-04 20:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-04 20:21 Stephen Williams [this message]
2004-02-04 20:36 ` [U-Boot-Users] Updates to u-boot 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=11277-50845@sneakemail.com \
--to=gfi8d1h02@sneakemail.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 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.