From: Joel Sherrill <joel.sherrill@oarcorp.com>
To: Joel Brobecker <brobecker@adacore.com>
Cc: Mike Frysinger <vapier@gentoo.org>,
"gdb@sourceware.org" <gdb@sourceware.org>,
Anthony Green <green@moxielogic.com>
Subject: Re: integrating dtc into the sim/ tree
Date: Wed, 20 Aug 2014 16:37:00 -0000 [thread overview]
Message-ID: <53F4CEDE.3000208@oarcorp.com> (raw)
In-Reply-To: <20140820161921.GL4828@adacore.com>
On 8/20/2014 11:19 AM, Joel Brobecker wrote:
>> I would have been happy if the generated files were in the tree and
>> only maintainer mode would result in the dependencies being checked.
>>
>> This has precedence for other tools.
> Is it just generated files? I was under the impression that you had
> to link against a library as well. If that wasn't the case, then it
> would certainly mitigate most of my concerns!
>
Inspecting the Makefile.in, I believe that is the case. This is all
there is:
moxie-gdb.dtb: moxie-gdb.dts
dtc -O dtb -o moxie-gdb.dtb ${srcdir}/moxie-gdb.dts
install-dtb: moxie-gdb.dtb
$(SHELL) $(srcdir)/../../mkinstalldirs $(DESTDIR)$(dtbdir)
$(INSTALL_DATA) moxie-gdb.dtb $(DESTDIR)$(dtbdir)/moxie-gdb.dtb
No reference to libraries. I checked the generated moxie-gdb.dtb and it
shows this:
$ file moxie-gdb.dtb
moxie-gdb.dtb: Device Tree Blob version 17, size=519, boot CPU=0, string
block size=75, DT structure block size=388
I am nearly 100% sure this could be a maintainer only option.
FWIW we have been looking into using dtc with RTEMS. It is a nice
way to abstract away the particulars of a SoC and let the BSP/drivers
find their properties from a configuration file/blob during initialization.
But I don't know how this package is distributed.
--
Joel Sherrill, Ph.D. Director of Research & Development
joel.sherrill@OARcorp.com On-Line Applications Research
Ask me about RTEMS: a free RTOS Huntsville AL 35805
Support Available (256) 722-9985
next prev parent reply other threads:[~2014-08-20 16:37 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 ` integrating dtc into the sim/ tree Mike Frysinger
2014-08-19 6:26 ` 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 [this message]
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=53F4CEDE.3000208@oarcorp.com \
--to=joel.sherrill@oarcorp.com \
--cc=brobecker@adacore.com \
--cc=gdb@sourceware.org \
--cc=green@moxielogic.com \
--cc=vapier@gentoo.org \
/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