From: David Gibson <david-xT8FGy+AXnRB3Ne2BGzF6laj5H9X9Tb+@public.gmane.org>
To: Simon Glass <sjg-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org>
Cc: Devicetree Compiler
<devicetree-compiler-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
Benjamin Bimmermann <b.bimmermann-LWAfsSFWpa4@public.gmane.org>,
Ulrich Langenbach
<ulrich.langenbach-srmvecZYGfHobmly5n/iKBvVK+yQ3ZXh@public.gmane.org>
Subject: Re: [PATCH v4 0/5] Introduce Python bindings for libfdt
Date: Fri, 10 Feb 2017 16:05:24 +1100 [thread overview]
Message-ID: <20170210050524.GH25381@umbus> (raw)
In-Reply-To: <20170205201323.15411-1-sjg-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 1405 bytes --]
On Sun, Feb 05, 2017 at 01:13:18PM -0700, Simon Glass wrote:
> At present libfdt consists of only a C implementation. Many scripts are
> written using Python so it useful to have Python bindings for libfdt.
> Apparently this has never been attempted before, or if so I cannot find a
> reference.
>
> This series starts the process of adding this support, with just a
> bare-bones set of methods.
>
> The v4 series provides binding that can be used like this:
>
> fdt = libfdt.Fdt(open(fname).read())
> node = fdt.path_offset('/subnode@1')
> print fdt.get_prop(node, 'compatible')
> subnode = fdt.first_subnode_quiet(node)
> while subnode > 0:
> print fdt.get_name(subnode)
> subnode = fdt.next_subnode_quiet(subnode)
>
> This version does not include a class for properties. That can be added
> if it is felt to be useful, but I want to get some basic functionality
> agreed first. The get_property_by_offset() function would likely benefit
> from this.
Sorry I've taken so long to look at this, I've finally given it a
review.
Fwiw, I ran into someone at linux.conf.au who also seemed to be rather
interested in a Python libfdt wrapper.
--
David Gibson | I'll have my music baroque, and my code
david AT gibson.dropbear.id.au | minimalist, thank you. NOT _the_ _other_
| _way_ _around_!
http://www.ozlabs.org/~dgibson
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2017-02-10 5:05 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-05 20:13 [PATCH v4 0/5] Introduce Python bindings for libfdt Simon Glass
[not found] ` <20170205201323.15411-1-sjg-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org>
2017-02-05 20:13 ` [PATCH v4 1/5] Add an initial Python library " Simon Glass
[not found] ` <20170205201323.15411-2-sjg-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org>
2017-02-10 4:37 ` David Gibson
2017-02-10 18:39 ` Simon Glass
[not found] ` <CAPnjgZ31rZqoYTg4m=3yAFuT2UuL9i4qc4+w-G34Aq75sdfrfA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-02-13 5:20 ` David Gibson
2017-02-15 18:55 ` Ulrich Langenbach
2017-02-16 2:11 ` David Gibson
[not found] ` <20170216021123.GO12369-K0bRW+63XPQe6aEkudXLsA@public.gmane.org>
2017-02-27 7:21 ` Ulrich Langenbach
2017-02-10 5:04 ` David Gibson
2017-02-05 20:13 ` [PATCH v4 2/5] Add tests for pylibfdt Simon Glass
[not found] ` <20170205201323.15411-3-sjg-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org>
2017-02-10 4:56 ` David Gibson
2017-02-10 18:39 ` Simon Glass
2017-02-05 20:13 ` [PATCH v4 3/5] Mention pylibfdt in the documentation Simon Glass
[not found] ` <20170205201323.15411-4-sjg-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org>
2017-02-10 4:58 ` David Gibson
2017-02-10 18:39 ` Simon Glass
2017-02-05 20:13 ` [PATCH v4 4/5] Adjust libfdt.h to work with swig Simon Glass
[not found] ` <20170205201323.15411-5-sjg-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org>
2017-02-10 5:01 ` David Gibson
2017-02-10 18:39 ` Simon Glass
2017-02-05 20:13 ` [PATCH v4 5/5] Build pylibfdt as part of the normal build process Simon Glass
2017-02-10 5:05 ` David Gibson [this message]
2017-02-10 18:39 ` [PATCH v4 0/5] Introduce Python bindings for libfdt Simon Glass
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=20170210050524.GH25381@umbus \
--to=david-xt8fgy+axnrb3ne2bgzf6laj5h9x9tb+@public.gmane.org \
--cc=b.bimmermann-LWAfsSFWpa4@public.gmane.org \
--cc=devicetree-compiler-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=sjg-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org \
--cc=ulrich.langenbach-srmvecZYGfHobmly5n/iKBvVK+yQ3ZXh@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).