From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] python3 support for pylibfdt
Date: Wed, 28 Aug 2019 21:19:26 -0400 [thread overview]
Message-ID: <20190829011926.GF26850@bill-the-cat> (raw)
In-Reply-To: <CAPnjgZ0C8EswFL5cG4kcwDRniYs2sZuNZgi7mfiJr61NBQpsAg@mail.gmail.com>
On Wed, Aug 28, 2019 at 10:11:16AM -0600, Simon Glass wrote:
> Hi Tom,
>
> On Wed, 28 Aug 2019 at 07:47, Tom Rini <trini@konsulko.com> wrote:
> >
> > On Wed, Aug 28, 2019 at 07:44:11AM -0600, Simon Glass wrote:
> > > Hi Peter,
> > >
> > > On Wed, 28 Aug 2019 at 05:46, Peter Robinson <pbrobinson@gmail.com> wrote:
> > > >
> > > > Hi Simon,
> > > >
> > > > > > > > > > With the EOL of python2 soon I've been looking at the Fedora U-Boot
> > > > > > > > > > builds to see what it would take to move over to python3. There's a
> > > > > > > > > > couple of issues building the bundled pylibfdt, the first is the
> > > > > > > > > > Makefile hard codes python2, the second is that the generated
> > > > > > > > > > libfdt_wrap.c doesn't seem to find the python3 version of Python.h
> > > > > > > > > > (errors below).
> > > > > > > > > >
> > > > > > > > > > It seems upstream now supports building pylibfdt with dtc 1.5.0 but I
> > > > > > > > > > couldn't quite work out how this fits into the U-Boot bundled version.
> > > > > > > > > > Is there plans to be able to support pylibfdt with python3?
> > > > > > > > >
> > > > > > > > > Sounds like we need to run the normal kernel script to re-sync with
> > > > > > > > > upstream? Thanks!
> > > > > > > >
> > > > > > > > Seems reasonable, I'll keep an eye out for a patch series to test,
> > > > > > > > it's quite straight forward to test from my PoV.
> > > > > > >
> > > > > > > It won't be any time soon, sadly. Updating to the same dtc in the
> > > > > > > kernel (so just v1.4.7+) causes both massive amount of new device tree
> > > > > > > warnings as well as several fail to link due to size growth problems.
> > > > > >
> > > > > > For reference the kernel moved to v1.5.0-30-g702c1b6c0e73 in the 5.3
> > > > > > merge window.
> > > > >
> > > > > Also I sent a series for libfdt to reduce the size, as a first step to
> > > > > syncing up U-Boot again. It needs work, but I expect to get back to it
> > > > > next week.
> > > >
> > > > What's the latest on this?
> > >
> > > No new progress but I just emailed David again about my pending question.
> >
> > Should we perhaps sync including your proposed changes for now and
> > re-sync once it's in? There's more than just Fedora folks unhappy about
> > us being one of the last requires python2 things they support.
>
> OK I can try this, but there is a bit of work before we can move to
> Python 3. I asked a month or two ago whether we should move to default
> Python 3 for this release, but I don't think I got an answer so did
> not focus on it. Then again, maybe I imagined it or missed it.
Hmm, I think I had taken your statement at the time as more of a
declaration of intent than a question, sorry!
--
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20190828/1bda9109/attachment.sig>
next prev parent reply other threads:[~2019-08-29 1:19 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-18 9:39 [U-Boot] python3 support for pylibfdt Peter Robinson
2019-06-19 18:22 ` Tom Rini
2019-06-20 10:45 ` Peter Robinson
2019-06-26 21:32 ` Tom Rini
2019-06-28 12:38 ` Peter Robinson
2019-06-28 12:51 ` Tom Rini
2019-06-28 13:52 ` Simon Glass
2019-07-24 9:23 ` Peter Robinson
2019-07-24 14:47 ` Simon Glass
2019-08-28 11:46 ` Peter Robinson
2019-08-28 13:44 ` Simon Glass
2019-08-28 13:47 ` Tom Rini
2019-08-28 16:11 ` Simon Glass
2019-08-29 1:19 ` Tom Rini [this message]
2019-09-04 14:36 ` Simon Glass
2019-10-25 3:31 ` 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=20190829011926.GF26850@bill-the-cat \
--to=trini@konsulko.com \
--cc=u-boot@lists.denx.de \
/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