Hi Tom,
Ah OK. I was worried about doing it in one step. It might be too late now but will take a look when I get time and we can see if it is safe.
Regards, Simon
On Wed, 28 Aug 2019 at 18:19, Tom Rini trini@konsulko.com wrote:
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