From: Michal Simek <monstr-pSz03upnqPeHXe+LvDLADg@public.gmane.org>
To: "Marc Marí" <marc.mari.barcelo-Iylbf7zvluZi+jfwTKn9+w@public.gmane.org>
Cc: devicetree <devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: Device Tree Generator
Date: Mon, 10 Mar 2014 11:19:57 +0100 [thread overview]
Message-ID: <531D91CD.2010300@monstr.eu> (raw)
In-Reply-To: <CA+nFU8SUbmwmUN1SWVoh2VEEQ-r347v=GMfDJmAbMhn_yLQCRA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 814 bytes --]
On 03/07/2014 07:57 PM, Marc Marí wrote:
> Hello everyone
>
> In the context of Google Summer of Code project, I'm thinking to work
> on a device-tree generator, starting at the Beagleboard platform.
>
> To define better the scope of this project, so it can be useful too
> outside this specific platform, I would like to ask for your opinions
> in necessary and good-to-have features.
FYI: Xilinx have device-tree generator which extract information
from design tools.
Thanks,
Michal
--
Michal Simek, Ing. (M.Eng), OpenPGP -> KeyID: FE3D1F91
w: www.monstr.eu p: +42-0-721842854
Maintainer of Linux kernel - Microblaze cpu - http://www.monstr.eu/fdt/
Maintainer of Linux kernel - Xilinx Zynq ARM architecture
Microblaze U-BOOT custodian and responsible for u-boot arm zynq platform
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 263 bytes --]
next prev parent reply other threads:[~2014-03-10 10:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-07 18:57 Device Tree Generator Marc Marí
[not found] ` <CA+nFU8SUbmwmUN1SWVoh2VEEQ-r347v=GMfDJmAbMhn_yLQCRA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-03-10 10:19 ` Michal Simek [this message]
[not found] ` <531D91CD.2010300-pSz03upnqPeHXe+LvDLADg@public.gmane.org>
2014-03-10 13:26 ` Walter Goossens
[not found] ` <531DBD81.40201-CmkmPbn3yAE@public.gmane.org>
2014-03-10 13:26 ` Marc Marí
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=531D91CD.2010300@monstr.eu \
--to=monstr-psz03upnqpehxe+lvdladg@public.gmane.org \
--cc=devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=marc.mari.barcelo-Iylbf7zvluZi+jfwTKn9+w@public.gmane.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;
as well as URLs for NNTP newsgroup(s).