From: Mike Frysinger <vapier@gentoo.org>
To: gdb@sourceware.org
Cc: Joel Sherrill <joel.sherrill@oarcorp.com>,
Anthony Green <green@moxielogic.com>
Subject: integrating dtc into the sim/ tree
Date: Tue, 19 Aug 2014 05:38:00 -0000 [thread overview]
Message-ID: <2237241.5jc4xaopjm@vapier> (raw)
In-Reply-To: <53F27ADC.4070609@oarcorp.com>
[-- Attachment #1: Type: text/plain, Size: 2483 bytes --]
On Mon 18 Aug 2014 17:14:52 Joel Sherrill wrote:
> gdb on the head has moxie-rtems fail like this:
>
> echo "/* generated by Makefile */" > tmp-hw.h
> /bin/sh ../../../binutils-gdb/sim/moxie/../common/create-version.sh
> ../../../binutils-gdb/sim/moxie/.. x86_64-unknown-linux-gnu
> moxie-rtems4.11 version.c
> sim_hw=""; \
> for hw in $sim_hw ; do \
> echo "extern const struct hw_descriptor dv_${hw}_descriptor[];" ; \
> done >> tmp-hw.h
> dtc -O dtb -o moxie-gdb.dtb ../../../binutils-gdb/sim/moxie/moxie-gdb.dts
> make[3]: dtc: Command not found
> echo "const struct hw_descriptor *hw_descriptors[] = {" >> tmp-hw.h
> make[3]: *** [moxie-gdb.dtb] Error 127
> make[3]: *** Waiting for unfinished jobs....
> sim_hw=""; \
> for hw in $sim_hw ; do \
>
> Is dtc a required tool that is not checked for? Is the output in the tree
> but not timestamped? maintainer only tool?
yeah, you need dtc for moxie. it's been this way forever ? for people
building from git, i think it's fine. it also leads me to a topic i've been
meaning to start for a while, so let's fork the thread.
what issues are there with making the sim use the existing dtc project ? the
dtc tool is licensed under the GPL-2 or later, and the libfdt library is dual
licensed (BSD-2 & GPL-2 or later).
http://www.devicetree.org/Device_Tree_Compiler
the reason i ask is that the existing sim code uses device tree style logic
heavily as it comes from the ppc sim import/commonization logic. afaik, this
codebase is somewhat a predecessor of the dtc codebase -- they both originated
at IBM, and the ppc sim is dated mid-1990's while dtc is dated mid-2000. i'm
not saying they necessarily share actual code, but they certainly have shared
lineage above that. at this point though, the syntax has diverged quite a
bit, so i'd love to just gut all the logic in sim and use the common dtc
package as that's what the rest of the world is using now. it'd also make it
easier to share device tree definitions between projects (sim/u-
boot/linux/etc...).
importing dtc in directly would be my preference, but iiuc, people would
prefer to only import FSF owned projects. i know that ship sailed long ago
with the sim codebase (large portions of it are not owned by the FSF), but
still the FSF seems to want to keep that from expanding further.
so i guess that leaves us with linking against a system copy. i'm fine with
that too. thoughts ?
-mike
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2014-08-19 5:38 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-18 22:14 gdb moxie build failure Joel Sherrill
2014-08-19 5:38 ` Mike Frysinger [this message]
2014-08-19 6:26 ` integrating dtc into the sim/ tree Joel Brobecker
2014-08-20 9:33 ` Mike Frysinger
2014-08-20 9:53 ` Joel Brobecker
2014-08-20 15:30 ` Mike Frysinger
2014-08-20 16:06 ` Joel Brobecker
2014-08-20 16:11 ` Joel Sherrill
2014-08-20 16:19 ` Joel Brobecker
2014-08-20 16:37 ` Joel Sherrill
2014-08-21 1:31 ` Mike Frysinger
2014-08-21 1:25 ` Mike Frysinger
2014-08-21 7:32 ` Joel Brobecker
2014-08-21 9:05 ` Pedro Alves
2014-08-21 13:58 ` Joel Sherrill
2014-08-21 16:25 ` Richard Henderson
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=2237241.5jc4xaopjm@vapier \
--to=vapier@gentoo.org \
--cc=gdb@sourceware.org \
--cc=green@moxielogic.com \
--cc=joel.sherrill@oarcorp.com \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).