From: Michael Roth <mroth@nessie.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] Patches for new at91 board / lowlevel_init.S
Date: Sat, 24 Jan 2009 23:57:05 +0100 [thread overview]
Message-ID: <497B9CC1.9060409@nessie.de> (raw)
Hello,
I'm having patches for a new at91sam9261 based board in my queue I would
like to publish for the current merge window.
However, this patch needs a way to supply its own lowlevel_init.S
instead the at91 default.
A week ago I asked a question about that topic and there was a hint to
look for the ronetix patches and a note that the next U-Boot release
will contain a solution.
However, the mentioned ronetix patch followed a discussion about
possible ways to address this topic but as far I can see, no solution
was selected.
Additionally, in the current git tree there is still no solution for
this topic, too (or I'm missing something).
So my question is:
How should I proceed? Should I post my solution? Or should I wait a
couple of more days for an "official" solution?
Michael Roth
next reply other threads:[~2009-01-24 22:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-24 22:57 Michael Roth [this message]
2009-01-25 0:57 ` [U-Boot] Cloning, Maybe silly question Pink Boy
2009-01-25 8:35 ` Wolfgang Denk
2009-01-25 9:00 ` [U-Boot] Patches for new at91 board / lowlevel_init.S Jean-Christophe PLAGNIOL-VILLARD
2009-01-25 14:01 ` Michael Roth
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=497B9CC1.9060409@nessie.de \
--to=mroth@nessie.de \
--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