From: Alvaro G. M <alvaro.gamez@hazent.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 0/2] Downloading from esoteric URIs, such as Xilinx toolchain
Date: Sun, 19 Feb 2012 13:14:47 +0100 [thread overview]
Message-ID: <cover.1329651936.git.alvaro.gamez@hazent.com> (raw)
From: "Alvaro G. M" <alvaro.gamez@hazent.com>
On the last days some of us have been trying to add Microblaze architecture to
buildroot and specifically LX9 board support.
The second patch adds the toolchain from Xilinx, but in order to download it,
it was needed to modify the DOWNLOAD_WGET routine. This is what the first
patch is for. At the same time, the API was somewhat simplified and it is
now a little shorter to interface with it in most cases.
I think this two patches can be applied with any changes thanks to Arnout's
recommendations, so I will appreciate it if they can be applied.
The next step, in which I think Spencer is working on, is the DTS support,
which can the be used for lots of different platforms.
I think I've correctly signed-off both patches, but let me know if I have
used some ideas from someone and I've forgotten about it.
Alvaro G. M (2):
DOWNLOAD: change $1=DIRECTORY_URL, $2=FILE_NAME to $1=FULL_FILE_URL,
$2=FILE_NAME
Microblaze: added external toolchain from Xilinx
docs/manual/adding-packages-handwritten.txt | 2 +-
linux/linux.mk | 2 +-
package/Makefile.package.in | 18 +++++++++++-------
package/cups/cups.mk | 2 +-
package/fis/fis.mk | 2 +-
package/games/doom-wad/doom-wads.mk | 2 +-
package/gettext/gettext.mk | 2 +-
package/microperl/microperl.mk | 2 +-
package/netkitbase/netkitbase.mk | 2 +-
package/netkittelnet/netkittelnet.mk | 2 +-
package/newt/newt.mk | 2 +-
package/tinyhttpd/tinyhttpd.mk | 2 +-
package/ttcp/ttcp.mk | 2 +-
package/uemacs/uemacs.mk | 2 +-
package/vpnc/vpnc.mk | 2 +-
package/xfsprogs/xfsprogs.mk | 2 +-
toolchain/gcc/gcc-uclibc-4.x.mk | 2 +-
toolchain/gdb/gdb.mk | 2 +-
toolchain/kernel-headers/kernel-headers.mk | 2 +-
toolchain/toolchain-external/Config.in | 16 ++++++++++++++++
toolchain/toolchain-external/ext-tool.mk | 12 +++++++++---
toolchain/uClibc/uclibc.mk | 2 +-
22 files changed, 55 insertions(+), 29 deletions(-)
--
1.7.9
next reply other threads:[~2012-02-19 12:14 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-19 12:14 Alvaro G. M [this message]
2012-02-19 12:17 ` [Buildroot] [PATCH 1/2] DOWNLOAD: change $1=DIRECTORY_URL, $2=FILE_NAME to $1=FULL_FILE_URL, $2=FILE_NAME Alvaro G. M
2012-02-19 12:17 ` [Buildroot] [PATCH 2/2] Microblaze: added external toolchain from Xilinx Alvaro G. M
2012-02-19 12:34 ` [Buildroot] [PATCH] Microblaze: added architecture support for both big endian and low endian Alvaro G. M
2012-02-20 8:49 ` Arnout Vandecappelle
2012-02-20 9:51 ` Arnout Vandecappelle
2012-02-20 8:48 ` [Buildroot] [PATCH 2/2] Microblaze: added external toolchain from Xilinx Arnout Vandecappelle
2012-02-20 9:20 ` Alvaro Gamez
2012-02-20 9:51 ` Arnout Vandecappelle
2012-02-20 9:59 ` Alvaro Gamez
2012-02-20 10:01 ` [Buildroot] [PATCH 1/2] " Alvaro G. M
2012-02-25 15:03 ` Arnout Vandecappelle
2012-02-20 8:45 ` [Buildroot] [PATCH 1/2] DOWNLOAD: change $1=DIRECTORY_URL, $2=FILE_NAME to $1=FULL_FILE_URL, $2=FILE_NAME Arnout Vandecappelle
2012-02-19 12:23 ` [Buildroot] [PATCH 0/2] Downloading from esoteric URIs, such as Xilinx toolchain Alvaro Gamez
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=cover.1329651936.git.alvaro.gamez@hazent.com \
--to=alvaro.gamez@hazent.com \
--cc=buildroot@busybox.net \
/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