From: Albert ARIBAUD <albert.aribaud@free.fr>
To: u-boot@lists.denx.de
Subject: [U-Boot] Trouble with U-Boot on our EVM-based hardware
Date: Thu, 17 Feb 2011 13:35:51 +0100 [thread overview]
Message-ID: <4D5D1627.8050209@free.fr> (raw)
In-Reply-To: <DB561678F08F554EB0D9F21B70E268A54B0777@exchange.intern.dresearch.de>
Hi David,
Le 16/02/2011 16:15, Schade, David a ?crit :
> Hi Albert,
>
> Thank you for your reply.
>
> I also tried the U-Boot version for beagleboard, which comdes from
> git://www.denx.de/git/u-boot.git;protocol=git with revision
> ca6e1c136ddb720c3bb2cc043b99f7f06bc46c55 and a lot of patch files.
Hmmm.
ca6e1c13... is quite away from the current master branch tip. I suggest
you use the master branch (of the most appropriate git repo for your
board, mainline, ARM or OMAP).
Also, where does this "lot of patch files" come from? All the official
code is in the u-boot git repositories, and nowhere else.
> Is this not the mainline? With this source (and my changes, but
> the problem is in common code) I also get my problem, and the data
> stored to gd/bd_t is lost unless it is volatile.
Just because the issue appears in common code does not mean the cause is
there too.
> Who is responsible for this part of code, who can help me with this
> problem in the common code? Maybe this maintainer:
> Manikandan Pillai<mani.pillai@ti.com>
> omap3_evm ARM CORTEX-A8 (OMAP3xx SoC)
> (file MAINTAINERS)
This is the board maintainer. If you suspect common code, there is no
reason to involve a specific board maintainer.
The best course of action is to send your patches to the list just like
any others but with an added "[RFC]" tag in the subject lines.
> Best regards,
> David.
Amicalement,
--
Albert.
next prev parent reply other threads:[~2011-02-17 12:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-16 15:15 [U-Boot] Trouble with U-Boot on our EVM-based hardware Schade, David
2011-02-17 12:35 ` Albert ARIBAUD [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-02-14 10:59 Schade, David
2011-02-14 11:49 ` Albert ARIBAUD
2011-02-11 10:35 Schade, David
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=4D5D1627.8050209@free.fr \
--to=albert.aribaud@free.fr \
--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