From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] AT91bootstrap with ptxdist
Date: Fri, 2 Sep 2016 13:53:32 +0200 [thread overview]
Message-ID: <20160902115332.xyw2saksyn6x3ger@pengutronix.de> (raw)
In-Reply-To: <CABDcavbaYU85yNoKMBHEVQO=r+fB6aTQLfEeOWm0-Tfr5sBo2A@mail.gmail.com>
On Tue, Aug 30, 2016 at 09:19:39AM +0200, Guillermo Rodriguez Garcia wrote:
> 2016-08-29 9:26 GMT+02:00 Guillermo Rodriguez Garcia
> <guille.rodriguez@gmail.com>:
> > 2016-08-25 13:15 GMT+02:00 Guillermo Rodriguez Garcia
> > <guille.rodriguez@gmail.com>:
> >> 2016-08-25 12:54 GMT+02:00 Michael Olbrich <m.olbrich@pengutronix.de>:
> >>> On Mon, Aug 22, 2016 at 04:41:52PM +0200, Guillermo Rodriguez Garcia wrote:
> >>>> I am trying to compile AT91bootstrap with ptxdist and I have found the
> >>>> following minor issues:
> >>>>
> >>>> 1. Starting from end of 2014, at91bootstrap releases are no longer
> >>>> published on ftp://www.at91.com/pub/.. The "official" source now seems
> >>>> to be the at91bootstrap repo. The ftp site contains versions up to
> >>>> 3.7.1 (Nov 2014), while the github repo contains versions from 3.7
> >>>> (Sep 2014) onwards.
> >>>>
>
> I have had a closer look at this and found the following:
>
> 1. The original URL used in ptxdist's at91bootstrap2.make
> (ftp://www.at91.com/pub/buildroot/$(AT91BOOTSTRAP2).$(AT91BOOTSTRAP2_SUFFIX))
> does no longer work. The buildroot/ dir in the at91 ftp site does not
> contain at91bootstrap sources anymore.
>
> 2. In the same ftp site there is a directory
> ftp://www.at91.com/pub/at91bootstrap which contains:
> - Some 1.x at91bootstrap releases (not relevant for
> at91bootstrap_2_.make, which is supposed to deal with versions >= 2.x)
> - No 2.x releases at all (neither source code nor binary)
> - Some (but not all) 3.x releases between 3.1 and 3.7.1: Of these,
> only 3.1 and 3.2 have some sort of source code, although judging from
> the file names they does not seem to be the official releases (perhaps
> a dev snapshot).
>
> The above means that ptxdist's at91bootstrap2.make is currently more
> or less broken already in its current state.
>
> 3. Atmel now officially points you to their github repo in order to
> get the source code (see:
> http://www.at91.com/linux4sam/bin/view/Linux4SAM/AT91Bootstrap#Get_AT91Boostrap_Source_Code)
>
> 4. In the github repo you can find full releases including source code
> for all versions since 3.4 (I said 3.7 in my first mail but I was
> wrong).
>
> So if no one objects I will prepare and send a patch
> at91bootstrap2.{in,make} to make it work with the current 3.x series.
Sounds good. I've applied the patch. Thanks.
Michael
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
prev parent reply other threads:[~2016-09-02 11:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-22 14:41 Guillermo Rodriguez Garcia
2016-08-25 10:54 ` Michael Olbrich
2016-08-25 11:15 ` Guillermo Rodriguez Garcia
2016-08-29 7:26 ` Guillermo Rodriguez Garcia
2016-08-30 7:19 ` Guillermo Rodriguez Garcia
2016-08-30 8:34 ` [ptxdist] [PATCH] Update at91bootstrap2 package for compatibility with 3.x series Guillermo Rodriguez
2016-09-02 11:53 ` Michael Olbrich [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=20160902115332.xyw2saksyn6x3ger@pengutronix.de \
--to=m.olbrich@pengutronix.de \
--cc=ptxdist@pengutronix.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