From: Graeme Russ <graeme.russ@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] U-boot customized
Date: Fri, 13 Apr 2012 22:28:47 +1000 [thread overview]
Message-ID: <4F881BFF.7000302@gmail.com> (raw)
In-Reply-To: <CAKk-iR8BfFGxR8GjTbfM6i0m4SYOdTZgWjB64YVO8Sn0jgcQyw@mail.gmail.com>
Hi Allyson,
A) Please keep the mailing list Cc'd - I don't know much about ARM and
nothing about the at91rm9200 - I'm just trying to be helpful :)
B) Please don't top-post
On 04/13/2012 09:30 PM, Allyson Pereira wrote:
> Hi Graeme,
>
> Well...
>
> I'm running U-Boot 2011.03.
> The compile process it's ok .... but when I put it on my system I get any
> response.
> But the board is mine, this is a old product of my company and this time I
> need put linux run on it.
OK, so what you are saying is u-boot-1.1.6 from git.denx.de without any
additional modifications works fine, but U-Boot 2011.03 from git.denx.de
without any additional patches does not?
If this is the case, then you are likely going to get some pretty good
support from the ML as that would mean there is a regression in mainline
code that needs to be fixed...
Are you familiar with 'git' at all?
git has a very useful tool called 'git bisect' which basically asks for the
ID of a known 'Good commit' (in this case u-boot-1.1.6) and a known 'Bad
Commit' (2011.3). It will then find the commit halfway between and check it
out - You then compile and test and tell git if that commit was 'Good' or 'Bad'
This process will repeat until you find the commit that caused the breakage
- Post that commit ID to the mailing list and somebody should get around to
looking at it
>
> Thanks for your attention.
Your welcome,
Regards,
Graeme
>
> Regards,
> Allyson
>
>
> 2012/4/13 Graeme Russ <graeme.russ at gmail.com <mailto:graeme.russ@gmail.com>>
>
> Hi Allyson,
>
> On Fri, Apr 13, 2012 at 1:57 PM, Allyson <allyson10r@gmail.com
> <mailto:allyson10r@gmail.com>> wrote:
> >
> > Hi folks,
> >
> > My name is Allyson,
> > I need put u-boot on my board with ARM 920t (at91rm9200)
> >
> > When I build u-boot-1.1.6 it is worked ok, but if I build u-boot-2011
> don't
> > work.
> >
> > I need help ... please!
>
> And we will need a lot more detail before we can help...
>
> - Are you running 'mainline' U-Boot (versus some custom version)
> - What does 'don't work' mean - Does it compile? If so, is there any
> output when you try to boot the board
> - If you are using 'mainline' U-Boot with no other patches, you
> should try using 'git bisect' to find out when things stopped working
>
> Please have a look at:
>
> http://catb.org/esr/faqs/smart-questions.html
>
> Regards,
>
> Graeme
>
>
>
>
> --
> Att,
> Eng. Allyson Rosa Pereira
> (35)9209-6137
>
> ??????????
prev parent reply other threads:[~2012-04-13 12:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-13 3:57 [U-Boot] U-boot customized Allyson
2012-04-13 5:44 ` Graeme Russ
[not found] ` <CAKk-iR8BfFGxR8GjTbfM6i0m4SYOdTZgWjB64YVO8Sn0jgcQyw@mail.gmail.com>
2012-04-13 12:28 ` Graeme Russ [this message]
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=4F881BFF.7000302@gmail.com \
--to=graeme.russ@gmail.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