devicetree-compiler.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Simon Glass <sjg-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org>
To: David Gibson <david-xT8FGy+AXnRB3Ne2BGzF6laj5H9X9Tb+@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 4/5] Adjust libfdt.h to work with swig
Date: Fri, 10 Feb 2017 11:39:26 -0700	[thread overview]
Message-ID: <CAPnjgZ28LYoJ7N_8sNhV_FXXQg0eDZMDOFrsJZxNVx9mXSQk5g@mail.gmail.com> (raw)
In-Reply-To: <20170210050132.GF25381@umbus>

Hi David,

On 9 February 2017 at 22:01, David Gibson <david-xT8FGy+AXnRB3Ne2BGzF6laj5H9X9Tb+@public.gmane.org> wrote:
> On Sun, Feb 05, 2017 at 01:13:22PM -0700, Simon Glass wrote:
>> There are a few places where libfdt.h cannot be used as is with swig:
>>
>> - macros like fdt_totalsize() have to be defined as C declarations
>> - fdt_offset_ptr() and fdt_getprop_namelen() need special treatment due to
>>     a TODO in the wrapper for fdt_getprop()
>
> fdt_offset_ptr() is a very low-level function which should be rarely
> needed outside libfdt internals, even in C.  I think it makes sense to
> exclude it from the Python interface.

Sounds good.

>
> fdt_getprop_namelen() is primarily to make certain things easier in C
> where copying and slicing up strings can be quite painful.  Since
> that's trivial in Python, I don't think there's any need to expose the
> namelen() functions in Python.

Yes that's a good point, will drop it.

>
>>
>> The second one can hopefully be resolved by someone with more knowledge of
>> SWIG than me.
>>
>> Add #ifdefs to work around this problem.
>>
>> Signed-off-by: Simon Glass <sjg-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org>
>> ---
>>
>> Changes in v4:
>> - Add new patch to adjust libfdt.h to work with swig
>>
>> Changes in v3: None
>> Changes in v2: None
>>
>>  libfdt/libfdt.h | 7 ++++++-
>>  1 file changed, 6 insertions(+), 1 deletion(-)
>>
>> diff --git a/libfdt/libfdt.h b/libfdt/libfdt.h
>> index c69e918..2e78754 100644
>> --- a/libfdt/libfdt.h
>> +++ b/libfdt/libfdt.h
>> @@ -143,7 +143,9 @@
>>  /* Low-level functions (you probably don't need these)                */
>>  /**********************************************************************/
>>
>> +#ifndef SWIG /* Use a special rule in libfdt.swig instead */
>>  const void *fdt_offset_ptr(const void *fdt, int offset, unsigned int checklen);
>> +#endif
>>  static inline void *fdt_offset_ptr_w(void *fdt, int offset, int checklen)
>>  {
>>       return (void *)(uintptr_t)fdt_offset_ptr(fdt, offset, checklen);
>> @@ -210,7 +212,7 @@ int fdt_next_subnode(const void *fdt, int offset);
>>  /**********************************************************************/
>>  /* General functions                                                  */
>>  /**********************************************************************/
>> -
>> +#ifndef SWIG /* Repeated in libfdt.swig (we cannot use macros) */
>
> You need to duplicate them in libfdt.swig, certainly, but why do you
> need to explicitly cut them out here?  Isn't swig smart enough to know
> it can't do anything with these?

Because the #define stuffs up my declarations. But it's easy to put
the declarations first to avoid that problem, so I'll do that.

[..]

Regards,
Simon

  reply	other threads:[~2017-02-10 18:39 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 [this message]
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   ` [PATCH v4 0/5] Introduce Python bindings for libfdt David Gibson
2017-02-10 18:39     ` 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=CAPnjgZ28LYoJ7N_8sNhV_FXXQg0eDZMDOFrsJZxNVx9mXSQk5g@mail.gmail.com \
    --to=sjg-f7+t8e8rja9g9huczpvpmw@public.gmane.org \
    --cc=b.bimmermann-LWAfsSFWpa4@public.gmane.org \
    --cc=david-xT8FGy+AXnRB3Ne2BGzF6laj5H9X9Tb+@public.gmane.org \
    --cc=devicetree-compiler-u79uwXL29TY76Z2rM5mHXA@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).