From: Joakim Tjernlund <Joakim.Tjernlund@infinera.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] u-boot.git or u-boot-x86.git for x86_64 u-boots?
Date: Tue, 24 Jan 2017 14:12:30 +0000 [thread overview]
Message-ID: <1485267148.4044.87.camel@infinera.com> (raw)
In-Reply-To: <CAPnjgZ07hwjb1JkwSmbd-oHaXsTG6GX_F+OkRuyjDcA-+JWvkw@mail.gmail.com>
On Sat, 2017-01-14 at 10:06 -0700, Simon Glass wrote:
> Hi Joakim,
>
> On 14 January 2017 at 04:51, Bin Meng <bmeng.cn@gmail.com> wrote:
> > +Simon,
> >
> > On Fri, Jan 13, 2017 at 4:12 AM, Joakim Tjernlund
> > <Joakim.Tjernlund@infinera.com> wrote:
> > > I found two repos w.r.t x86_64 for u-boot, which one should I use?
> > >
> >
> > U-Boot x86_64 support is not in mainstream yet.
>
> I'll be sending v3 fairly soon. But even then it is not complete.
> Various things need fixing up and polishing - e.g. SDRAM sizing,
> graphics ROMs, actually booting Linux!
>
> >
> > > I am ATM only looking at USING the qemu-x86 target for now.
> > >
> > > BTW, I found tools/binman/binman.py only worked with python 2.7, maybe you can change
> > > the shebang to python2.7 as my default python is 3.4
>
> We should probably patch it to work on 3.4 also.
I did a quick test using: 2to3 -w binman.py
This makes binman.py "build" on both 2.7 and 3.4 but running it on 3.4
hangs forever until Ctrl-C:
BINMAN u-boot.rom
Traceback (most recent call last):
File "./tools/binman/binman", line 113, in <module>
ret_code = RunBinman(options, args)
File "./tools/binman/binman", line 101, in RunBinman
ret_code = control.Binman(options, args)
File "/usr/local/src/u-boot-x86/tools/binman/control.py", line 95, in Binman
fdt = fdt_select.FdtScan(dtb_fname)
File "/usr/local/src/u-boot-x86/tools/binman/../dtoc/fdt_select.py", line 28, in FdtScan
dtb.Scan()
File "/usr/local/src/u-boot-x86/tools/binman/../dtoc/fdt.py", line 229, in Scan
self._root.Scan()
File "/usr/local/src/u-boot-x86/tools/binman/../dtoc/fdt_fallback.py", line 61, in Scan
for name, byte_list_str in self._fdt.GetProps(self.path).items():
File "/usr/local/src/u-boot-x86/tools/binman/../dtoc/fdt_fallback.py", line 128, in GetProps
out = command.Output('fdtget', self._fname, node, '-p')
File "/usr/local/src/u-boot-x86/tools/binman/../patman/command.py", line 109, in Output
return RunPipe([cmd], capture=True, raise_on_error=raise_on_error).stdout
File "/usr/local/src/u-boot-x86/tools/binman/../patman/command.py", line 97, in RunPipe
last_pipe.CommunicateFilter(None))
File "/usr/local/src/u-boot-x86/tools/binman/../patman/cros_subprocess.py", line 168, in CommunicateFilter
rlist, wlist, _ = select.select(read_set, write_set, [], 0.2)
KeyboardInterrupt
Makefile:1070: recipe for target 'u-boot.rom' failed
make: *** [u-boot.rom] Error 1
Please just change shebang to python2.7 for now. This is the only fix needed
to build the x86 qemu target.
Jocke
prev parent reply other threads:[~2017-01-24 14:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-12 20:12 [U-Boot] u-boot.git or u-boot-x86.git for x86_64 u-boots? Joakim Tjernlund
2017-01-14 11:51 ` Bin Meng
2017-01-14 13:25 ` Joakim Tjernlund
2017-01-14 13:30 ` Bin Meng
2017-01-14 17:06 ` Simon Glass
2017-01-15 16:49 ` Joakim Tjernlund
2017-01-16 1:20 ` Bin Meng
2017-01-16 2:50 ` Simon Glass
2017-01-24 14:12 ` Joakim Tjernlund [this message]
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=1485267148.4044.87.camel@infinera.com \
--to=joakim.tjernlund@infinera.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