From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] configs/xilfpga: Add xilfpga defconfig
Date: Wed, 21 Oct 2015 17:14:02 +0200 [thread overview]
Message-ID: <20151021171402.5d9aa7d0@free-electrons.com> (raw)
In-Reply-To: <1445439476-32911-1-git-send-email-Zubair.Kakakhel@imgtec.com>
Zubair,
On Wed, 21 Oct 2015 15:57:56 +0100, Zubair Lutfullah Kakakhel wrote:
> Under the IMG University Program 'MIPSfpga', RTL verilog code for a MIPS
> m14kEC core is released under an academic license.
>
> The core is used to make a soft-SOC which can run the Linux kernel +
> buildroot.
Cool! :-)
>
> This patch adds a defconfig for it and a readme file.
>
> The config generates a simple mips32r2 rootfs using uClibc.
>
> Signed-off-by: Zubair Lutfullah Kakakhel <Zubair.Kakakhel@imgtec.com>
> Reviewed-by: Vicente Olivert Riera <Vincent.Riera@imgtec.com>
>
> ---
> p.s.
>
> The kernel patches for MIPSfpga will hopefully be upstreamed by 4.4.
>
> Once that is done, I'll look into adding the stuff to enable buildroot
> to compile the kernel as well.
A defconfig which doesn't build a kernel nor a bootloader is pretty
useless IMO.
Isn't the code to build this kernel available on some Git repository,
even if it's not upstream yet ? If so, then it would be better to have
a defconfig that points to this Git repository (actually, many of our
defconfigs point to non-upstream kernel source code).
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2015-10-21 15:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-21 14:57 [Buildroot] [PATCH 1/1] configs/xilfpga: Add xilfpga defconfig Zubair Lutfullah Kakakhel
2015-10-21 15:14 ` Thomas Petazzoni [this message]
2015-10-22 9:26 ` Zubair Lutfullah Kakakhel
2015-10-22 14:20 ` Arnout Vandecappelle
2015-10-22 15:55 ` Thomas Petazzoni
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=20151021171402.5d9aa7d0@free-electrons.com \
--to=thomas.petazzoni@free-electrons.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 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.