From: Justin Waters <justin.waters@timesys.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] Help on getting the AT91 u-boot patch
Date: Fri, 6 Mar 2009 09:42:01 -0500 [thread overview]
Message-ID: <1236350521.7797.44.camel@jjw-linux> (raw)
In-Reply-To: <5A49B5FB10454B92AE892C6DF7050410@JohnBoyDell>
On Thu, 2009-03-05 at 12:40 -0500, John Parten wrote:
> Hello Mailling List,
>
> I am trying to build U-Boot 1.3.4 from source, for the AT91SAM9260EK development board.
>
> I am following the instructions at http://www.linux4sam.org/twiki/bin/view/Linux4SAM/U-Boot
> I get to the point where it says take the AT91 u-boot patch set
>
> However, when I try to use ...
>
> wget http://www.linux4sam.org/twiki/pub/Linux4SAM/U-Boot/u-boot-1.3.4-exp.diff
>
> I get error "404 file not found"
>
> Also I tried ...
>
> wget http://www.linux4sam.org/pub/uboot/u-boot-1.3.4-exp/u-boot-1.3.4-exp.diff as per the table a bit further down on the page - this does not work either.
>
> Can anyone tell me how to get the AT91 u-boot patch file please ?
>
> ... many thanks
> ... kind regards
> ... John Parten
John,
You are much better off using the mainline U-Boot at this point. It is
far more stable and it's been getting better with each release. I
looked at the 1.3.4 patch, and nearly all of those features are in
2009.01, plus more. The only major difference is that upstream does not
support the AT91SAM9G20-EK.
With that being said, this link seems to work:
ftp://www.linux4sam.org/pub/uboot/u-boot-1.3.4-exp/u-boot-1.3.4-exp.diff
You should probably contact the folks at Linux4Sam to tell them that
their instructions are incorrect.
-Justin Waters
next prev parent reply other threads:[~2009-03-06 14:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-05 17:40 [U-Boot] Help on getting the AT91 u-boot patch John Parten
2009-03-06 14:37 ` Detlef Vollmann
2009-03-06 16:13 ` Jean-Christophe PLAGNIOL-VILLARD
2009-03-06 16:46 ` Detlef Vollmann
2009-03-06 14:42 ` Justin Waters [this message]
2009-03-09 14:22 ` Nicolas Ferre
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=1236350521.7797.44.camel@jjw-linux \
--to=justin.waters@timesys.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.