Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Joel Sherrill <joel.sherrill@oarcorp.com>
To: Joel Brobecker <brobecker@adacore.com>,
	 Mike Frysinger <vapier@gentoo.org>
Cc: "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:11:00 -0000	[thread overview]
Message-ID: <53F4C8A5.1070503@oarcorp.com> (raw)
In-Reply-To: <20140820160635.GK4828@adacore.com>

On 8/20/2014 11:06 AM, Joel Brobecker wrote:
>> moxie is the only one that hard requires dtc (it might be limited to
>> maintainer mode).  but the larger point is to delete a large body of
>> custom code that the sim has today for parsing its device tree like
>> data format and convert over to the standard format that the rest of
>> the world is using now.  and longer term, make it so we can share dtc
>> files between linux/u-boot/qemu such that you can feed a fdt to the
>> sim and it'll automatically bring up hardware in the same way as the
>> kernel would have found it.
>>
>> atm, you have to basically write two different device trees with
>> different syntax and names, then feed one to the sim and the other to
>> the kernel.  and hope they don't get out of sync :).
>>
>> there's basically no chance of people rewriting the existing sim code
>> so that it gains all the same functionality as the public dtc, and
>> then keeping it in sync.  i'd rather just gut it and be done, and get
>> the dtc updates for free.
> My 2 cents: This sounds interesting, but on the other hand, I have
> this feeling that requiring dtc might be a big ask. I'm not sure
> how portable the dtc project is, and how easy it is to get it
> installed. I went to the "Device Tree Compiler" page you referenced,
> and it doesn't give at all the impression of being a mature and
> widespread project... For instance, I was looking for the documentation
> in order to check for things like installation, OS support,
> requirements, etc. I ended up looking inside the source tree itself,
> and found Documentation/manual.txt and README, but none of them answered
> any of these questions. I am also wondering about releases and such,
> but couldn't really find much about it.
>
> I hope this explains why I would personally feel a little more
> comfortable if that dependency remained optional.
>
> Now, if the project was really super easy to install and completely
> portable (think Linux & Windows, of course, but also Darwin,
> Solaris...), I would consider making it mandatory.
>
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.

-- 
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


  reply	other threads:[~2014-08-20 16:11 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 [this message]
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=53F4C8A5.1070503@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