From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 4/5] Microblaze: build kernel with device tree
Date: Wed, 14 Mar 2012 00:25:23 +0100 [thread overview]
Message-ID: <201203140025.24202.arnout@mind.be> (raw)
In-Reply-To: <20120312231055.5ba3a3be@skate>
On Monday 12 March 2012 23:10:55 Thomas Petazzoni wrote:
> > 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
> architectures such as ARM or PowerPC have device tree support, and I
> think the build procedure of the device tree blob is the same
> regardless of the architecture.
I fully agree that we should have DTS support in buildroot. However:
- Stephan doesn't see how to do it, and
- for microblaze, the kernel source provides slightly different targets
than for arm/powerpc.
If I understand correctly, for microblaze, you *have* to use a
simpleImage, which is a uImage with a DTB subimage. In other words,
unless we have some kind of DTS support in buildroot, we can't support
microblaze.
Since nobody seems to be stepping up to add generic DTS support, that
means microblaze is blocked. That, I think, is stupid. If we have
working patches for microblaze now, why not accept them? We can
always add DTS support later and refactor the microblaze-specific stuff
away. In fact, this microblaze-specific stuff makes it easier to add
generic DTS support, because you already get a defconfig that uses it
and that you can use for testing.
That said, your other comments are still valid and this patch is not yet
ready for inclusion.
Regards,
Arnout
--
Arnout Vandecappelle arnout at mind be
Senior Embedded Software Architect +32-16-286540
Essensium/Mind http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint: 7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F
next prev parent reply other threads:[~2012-03-13 23:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-11 16:50 [Buildroot] [PATCH 4/5] Microblaze: build kernel with device tree Stephan Hoffmann
2012-03-12 22:10 ` Thomas Petazzoni
2012-03-13 23:25 ` Arnout Vandecappelle [this message]
2012-03-14 16:41 ` Alvaro Gamez
2012-03-15 18:57 ` Stephan Hoffmann
2012-03-15 19:21 ` Alvaro Gamez
2012-03-16 13:39 ` 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=201203140025.24202.arnout@mind.be \
--to=arnout@mind.be \
--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