Andrew,

Thans for your answer.

Bug reported: https://github.com/openbmc/openbmc/issues/2434

I`d like to try to cook up a patch, but do I need to know a specific
language programming to do this ?

Regards,











*Javier Romero*

*E-mail: xavinux@gmail.com <xavinux@gmail.com>*

*Skype: xavinux*


2017-10-08 9:44 GMT-03:00 Andrew Jeffery <andrew@aj.id.au>:

> On Sun, 2017-10-08 at 01:45 -0300, Javier Romero wrote:
> > I've tried these steps:
> >
> > 1. tester@obmc:~$ cd openbmc
> >
> > 2. tester@obmc:/openbmc$ export TEMPLATECONF=meta-openbmc-
> machines/meta-evb/meta-evb-raspberrypi/conf
> >
> > 3. tester@obmc:/openbmc$ . oe-init-build-env ~/my-build-raspberrypi
> >
> > 4. tester@obmc:~/my-build-raspberrypi$ bitbake obmc-phosphor-image
> >
> > Build Configuration:
> > BB_VERSION        = "1.32.0"
> > BUILD_SYS         = "x86_64-linux"
> > NATIVELSBSTRING   = "Ubuntu-16.04"
> > TARGET_SYS        = "arm-openbmc-linux-gnueabi"
> > MACHINE           = "raspberrypi"
> > DISTRO            = "openbmc-phosphor"
> > DISTRO_VERSION    = "0.1.0"
> > TUNE_FEATURES     = "arm armv6  vfp arm1176jzfs callconvention-hard"
> > TARGET_FPU        = "hard"
> > meta
> > meta-poky
> > meta-oe
> > meta-networking
> > meta-python
> > meta-virtualization
> > meta-phosphor
> > meta-raspberrypi  = "master:65edf7d796c34012982632d0a724d80ff44c9e4a"
> >
> >
> > But the following error appears:
> >
> > ERROR: linux-raspberrypi-1_4.4.48+gitAUTOINC+7ddf96fbb7-r0
> do_kernel_metadata: Function failed: do_kernel_metadata (log file is
> located at /home/tester/my-build-raspberrypi/tmp/work/
> raspberrypi-openbmc-linux-gnueabi/linux-raspberrypi/1_4.
> 4.48+gitAUTOINC+7ddf96fbb7-r0/temp/log.do_kernel_metadata.7276)
> > ERROR: Logfile of failure stored in: /home/tester/my-build-
> raspberrypi/tmp/work/raspberrypi-openbmc-linux-
> gnueabi/linux-raspberrypi/1_4.4.48+gitAUTOINC+7ddf96fbb7-r0/
> temp/log.do_kernel_metadata.7276
> > Log data follows:
> > | DEBUG: Executing shell function do_kernel_metadata
> > | ERROR. input file "phosphor-gpio-keys" does not exist
> > | ERROR: could not process input files: /home/tester/openbmc/import-
> layers/meta-raspberrypi/recipes-kernel/linux/linux-raspberrypi/defconfig
> /home/tester/openbmc/import-layers/meta-raspberrypi/
> recipes-kernel/linux/linux-raspberrypi-4.4/0001-fix-dtbo-rules.patch
> phosphor-gpio-keys
> > |        See /tmp/tmp.GA2zgVbszZ for details
> > | ERROR. input file "phosphor-gpio-keys" does not exist
> > | ERROR: could not process input files: /home/tester/openbmc/import-
> layers/meta-raspberrypi/recipes-kernel/linux/linux-raspberrypi/defconfig
> /home/tester/openbmc/import-layers/meta-raspberrypi/
> recipes-kernel/linux/linux-raspberrypi-4.4/0001-fix-dtbo-rules.patch
> phosphor-gpio-keys
> > |        See /tmp/tmp.BEzIPRvVMy for details
> > | WARNING: exit code 1 from a shell command.
> > | ERROR: Function failed: do_kernel_metadata (log file is located at
> /home/tester/my-build-raspberrypi/tmp/work/raspberrypi-openbmc-linux-
> gnueabi/linux-raspberrypi/1_4.4.48+gitAUTOINC+7ddf96fbb7-r0/
> temp/log.do_kernel_metadata.7276)
> > ERROR: Task (/home/tester/openbmc/import-layers/meta-raspberrypi/
> recipes-kernel/linux/linux-raspberrypi_4.4.bb:do_kernel_metadata) failed
> with exit code '1'
> > NOTE: Tasks Summary: Attempted 632 tasks of which 0 didn't need to be
> rerun and 1 failed.
> > Summary: 1 task failed:
> >   /home/tester/openbmc/import-layers/meta-raspberrypi/
> recipes-kernel/linux/linux-raspberrypi_4.4.bb:do_kernel_metadata
> > Summary: There were 6 WARNING messages shown.
> > Summary: There was 1 ERROR message shown, returning a non-zero exit code.
> >
> > Is there something wrong with the steps I've tried ?
>
> Nope, that's just an outright bug in the raspi support. I'd recommend
> several
> things here:
>
> 1. Open an issue in the github issue tracker[0]
> 2. Cook up a patch! It looks like this might have to do with assumptions
> made
>    in meta-phosphor/conf/distro/openbmc-phosphor.conf, as the raspi uses a
>    different kernel tree to the ASPEED SoCs
> 3. For better or worse patches are submitted via Gerrit[1], so push your
> patch
>    there
>
> Make sure to speak up here or on IRC if you get stuck :)
>
> Andrew
>
> [0] https://github.com/openbmc/openbmc/issues
> [1] https://gerrit.openbmc-project.xyz/#/q/status:open