From: Stephan Hoffmann <sho@relinux.de>
To: buildroot@busybox.net
Subject: [Buildroot] Fwd: Re: [PATCH 4/5] Microblaze: build kernel with device tree
Date: Tue, 13 Mar 2012 18:34:36 +0100 [thread overview]
Message-ID: <4F5F852C.1060903@relinux.de> (raw)
Sorry, hit the wrong button;-(
Am 12.03.2012 23:10, schrieb Thomas Petazzoni:
> Hello,
>
> Le Sun, 11 Mar 2012 17:50:17 +0100,
> Stephan Hoffmann <sho@relinux.de> a ?crit :
>
>> Device Tree and SimpleImage will be handled in buildroot in the
>> future. Until then, this patch is needed.
>>
>> Signed-off-by: Stephan Hoffmann <sho@relinux.de>
> I am not yet familiar with how the device tree blob is generated, but I
> don't like the fact that this patch is Microblaze specific. Other
Hello,
There is a discussion here on the list regarding this. I submitted this
patch
only to be able to build the whole system until DTS support is ready. It
is not meant
to go into the main tree.
Kind regards
Stephan
--
reLinux - Stephan Hoffmann
Am Schmidtgrund 124 50765 K?ln
Tel. +49.221.95595-19 Fax: -64
www.reLinux.de sho at reLinux.de
--
reLinux - Stephan Hoffmann
Am Schmidtgrund 124 50765 K?ln
Tel. +49.221.95595-19 Fax: -64
www.reLinux.de sho at reLinux.de
reply other threads:[~2012-03-13 17:34 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4F5F852C.1060903@relinux.de \
--to=sho@relinux.de \
--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