<div dir="ltr">Andrew,<div><br></div><div>Thans for your answer.</div><div><br></div><div>Bug reported: <a href="https://github.com/openbmc/openbmc/issues/2434">https://github.com/openbmc/openbmc/issues/2434</a></div><div><br></div><div>I`d like to try to cook up a patch, but do I need to know a specific language programming to do this ?</div><div><br></div><div>Regards,</div><div><br></div><div><br></div><div><br></div><div><br></div><div><br></div><div><br></div><div><br></div><div><br></div><div><br></div></div><div class="gmail_extra"><br clear="all"><div><div class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div style="text-align:left"><i><b>Javier Romero<br></b></i></div><div style="text-align:left"><span style="color:rgb(19,79,92)"><i><b><span style="color:rgb(0,0,0)">E-mail:<span style="color:rgb(0,0,255)"> </span></span><span style="color:rgb(0,0,255)"><a href="mailto:xavinux@gmail.com" target="_blank">xavinux@gmail.com</a></span><br></b></i></span></div><div style="text-align:left"><i><b><span style="color:rgb(19,79,92)"><span style="color:rgb(0,0,0)">Skype:</span> <span style="color:rgb(11,83,148)"><u><span style="color:rgb(0,0,255)">xavinux</span><br></u></span></span></b></i></div><div style="text-align:left"><br></div> </div></div></div>
<br><div class="gmail_quote">2017-10-08 9:44 GMT-03:00 Andrew Jeffery <span dir="ltr"><<a href="mailto:andrew@aj.id.au" target="_blank">andrew@aj.id.au</a>></span>:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="HOEnZb"><div class="h5">On Sun, 2017-10-08 at 01:45 -0300, Javier Romero wrote:<br>
> I've tried these steps:<br>
> <br>
> 1. tester@obmc:~$ cd openbmc<br>
> <br>
> 2. tester@obmc:/openbmc$ export TEMPLATECONF=meta-openbmc-<wbr>machines/meta-evb/meta-evb-<wbr>raspberrypi/conf<br>
> <br>
> 3. tester@obmc:/openbmc$ . oe-init-build-env ~/my-build-raspberrypi<br>
> <br>
> 4. tester@obmc:~/my-build-<wbr>raspberrypi$ bitbake obmc-phosphor-image<br>
> <br>
> Build Configuration:<br>
> BB_VERSION = "1.32.0"<br>
> BUILD_SYS = "x86_64-linux"<br>
> NATIVELSBSTRING = "Ubuntu-16.04"<br>
> TARGET_SYS = "arm-openbmc-linux-gnueabi"<br>
> MACHINE = "raspberrypi"<br>
> DISTRO = "openbmc-phosphor"<br>
> DISTRO_VERSION = "0.1.0"<br>
> TUNE_FEATURES = "arm armv6 vfp arm1176jzfs callconvention-hard"<br>
> TARGET_FPU = "hard"<br>
> meta <br>
> meta-poky <br>
> meta-oe <br>
> meta-networking <br>
> meta-python <br>
> meta-virtualization <br>
> meta-phosphor <br>
> meta-raspberrypi = "master:<wbr>65edf7d796c34012982632d0a724d8<wbr>0ff44c9e4a"<br>
> <br>
> <br>
> But the following error appears:<br>
> <br>
> ERROR: linux-raspberrypi-1_4.4.48+<wbr>gitAUTOINC+7ddf96fbb7-r0 do_kernel_metadata: Function failed: do_kernel_metadata (log file is located at /home/tester/my-build-<wbr>raspberrypi/tmp/work/<wbr>raspberrypi-openbmc-linux-<wbr>gnueabi/linux-raspberrypi/1_4.<wbr>4.48+gitAUTOINC+7ddf96fbb7-r0/<wbr>temp/log.do_kernel_metadata.<wbr>7276)<br>
> ERROR: Logfile of failure stored in: /home/tester/my-build-<wbr>raspberrypi/tmp/work/<wbr>raspberrypi-openbmc-linux-<wbr>gnueabi/linux-raspberrypi/1_4.<wbr>4.48+gitAUTOINC+7ddf96fbb7-r0/<wbr>temp/log.do_kernel_metadata.<wbr>7276<br>
> Log data follows:<br>
> | DEBUG: Executing shell function do_kernel_metadata<br>
> | ERROR. input file "phosphor-gpio-keys" does not exist<br>
> | ERROR: could not process input files: /home/tester/openbmc/import-<wbr>layers/meta-raspberrypi/<wbr>recipes-kernel/linux/linux-<wbr>raspberrypi/defconfig /home/tester/openbmc/import-<wbr>layers/meta-raspberrypi/<wbr>recipes-kernel/linux/linux-<wbr>raspberrypi-4.4/0001-fix-dtbo-<wbr>rules.patch phosphor-gpio-keys<br>
> | See /tmp/tmp.GA2zgVbszZ for details<br>
> | ERROR. input file "phosphor-gpio-keys" does not exist<br>
> | ERROR: could not process input files: /home/tester/openbmc/import-<wbr>layers/meta-raspberrypi/<wbr>recipes-kernel/linux/linux-<wbr>raspberrypi/defconfig /home/tester/openbmc/import-<wbr>layers/meta-raspberrypi/<wbr>recipes-kernel/linux/linux-<wbr>raspberrypi-4.4/0001-fix-dtbo-<wbr>rules.patch phosphor-gpio-keys<br>
> | See /tmp/tmp.BEzIPRvVMy for details<br>
> | WARNING: exit code 1 from a shell command.<br>
> | ERROR: Function failed: do_kernel_metadata (log file is located at /home/tester/my-build-<wbr>raspberrypi/tmp/work/<wbr>raspberrypi-openbmc-linux-<wbr>gnueabi/linux-raspberrypi/1_4.<wbr>4.48+gitAUTOINC+7ddf96fbb7-r0/<wbr>temp/log.do_kernel_metadata.<wbr>7276)<br>
> ERROR: Task (/home/tester/openbmc/import-<wbr>layers/meta-raspberrypi/<wbr>recipes-kernel/linux/linux-<wbr>raspberrypi_4.4.bb:do_kernel_<wbr>metadata) failed with exit code '1'<br>
> NOTE: Tasks Summary: Attempted 632 tasks of which 0 didn't need to be rerun and 1 failed.<br>
> Summary: 1 task failed:<br>
> /home/tester/openbmc/import-<wbr>layers/meta-raspberrypi/<wbr>recipes-kernel/linux/linux-<wbr>raspberrypi_4.4.bb:do_kernel_<wbr>metadata<br>
> Summary: There were 6 WARNING messages shown.<br>
> Summary: There was 1 ERROR message shown, returning a non-zero exit code.<br>
> <br>
> Is there something wrong with the steps I've tried ?<br>
<br>
</div></div>Nope, that's just an outright bug in the raspi support. I'd recommend several<br>
things here:<br>
<br>
1. Open an issue in the github issue tracker[0]<br>
2. Cook up a patch! It looks like this might have to do with assumptions made<br>
in meta-phosphor/conf/distro/<wbr>openbmc-phosphor.conf, as the raspi uses a<br>
different kernel tree to the ASPEED SoCs<br>
3. For better or worse patches are submitted via Gerrit[1], so push your patch<br>
there<br>
<br>
Make sure to speak up here or on IRC if you get stuck :)<br>
<br>
Andrew<br>
<br>
[0] <a href="https://github.com/openbmc/openbmc/issues" rel="noreferrer" target="_blank">https://github.com/openbmc/<wbr>openbmc/issues</a><br>
[1] <a href="https://gerrit.openbmc-project.xyz/#/q/status:open" rel="noreferrer" target="_blank">https://gerrit.openbmc-<wbr>project.xyz/#/q/status:open</a></blockquote></div><br></div>