Re: [yocto] [meta-yocto-bsp][PATCH v2] beaglebone-yocto: Update u-boot config to match u-boot 19.04
Hello Stefano,
Thank you for your reply. So, as expected, patches are in. Since I see
only this from A. Graf recently:
https://patchwork.ozlabs.org/project/uboot/list/?submitter=1212
After all, Tom Rini did it on A. Graf's behalf.
Once I start trying U-Boot post 2019.01 release on my BBB, I'll
subscribe to U-Boot email list again for the help. Now I am busy with
something else. :-)
I'll also give upon the (successful) event a short notice about BBB
U-Boot EFI shell status on this @ thread.
Once again, thank you,
Zoran
___
On Sat, Apr 13, 2019 at 8:40 PM Stefano Babic wrote:
>
> Hi Zoran,
>
> On 12/04/19 09:00, Zoran Stojsavljevic wrote:
> > Hello to all,
> >
> > I will ask few questions here regarding U-Boot, since U-Boot mailing
> > list is too frequent/clogged...
> >
> > Apropos (Regarding to) U-Boot 2019.04, I have some questions? May I?
> >
> > I know for the fact the following:
> > Alexander Graf (till 03.2019 SUSE developer) said (September 2018. in
> > Erlangen, Bavaria, DE) that U-Boot folks will move his UEFI patches in
> > master U-Boot git somewhere in midst of January 2019.
> >
> > I am wondering, did these patches were moved from Alexander Graf's U-Boot
> > git?
>
> As far as I know, Alex's patches at the time were already integrated in
> 2019.01.
>
> >
> > If yes, from which release UEFI shell support does reside in Coreboot
> > (version number)?
> >
> > Here is the pointer to Alex Graf's Git, I am talking about:
> > https://github.com/agraf/u-boot
>
> As far as I see, Alex's efi-2019.01 was integrated by Tom in 2019.01.
> But I have not tried myself, I fear you have to post U-Boot's ML if you
> need some help.
>
> > ___
> >
> > I have UEFI USB stick with already pre-compiled ready EFI shell 2.40,
> > so I would like to program such an U-Boot (2019.04?!) to my BBB and
> > try to get to the EFI shell with attached UEFI USB stick.
> >
> > Nice exercise, won't you all agree!? ;-)
> >
>
> Best regards,
> Stefano Babic
>
> > Thank you,
> > Zoran Stojsavljevic
> > ___
> >
> > On Fri, Apr 12, 2019 at 12:09 AM Alistair Francis
> > wrote:
> >>
> >> [YOCTO #13145]
> >>
> >> This was announced at 2019.01:
> >> https://www.mail-archive.com/u-boot@lists.denx.de/msg305424.html
> >>
> >> Basically, am335x_boneblack is just a special subset of am335x_evm config,
> >> created and owned by BeagleBoard.org community. Since it was not migrated
> >> to
> >> use CONFIG_BLK in time for 2019.04 release.
> >>
> >> Signed-off-by: Alistair Francis
> >> Acked-by: Denys Dmytriyenko
> >> ---
> >> meta-yocto-bsp/conf/machine/beaglebone-yocto.conf | 2 +-
> >> 1 file changed, 1 insertion(+), 1 deletion(-)
> >>
> >> diff --git a/meta-yocto-bsp/conf/machine/beaglebone-yocto.conf
> >> b/meta-yocto-bsp/conf/machine/beaglebone-yocto.conf
> >> index 70d3cfe..bc18ee8 100644
> >> --- a/meta-yocto-bsp/conf/machine/beaglebone-yocto.conf
> >> +++ b/meta-yocto-bsp/conf/machine/beaglebone-yocto.conf
> >> @@ -32,7 +32,7 @@ KERNEL_EXTRA_ARGS += "LOADADDR=${UBOOT_ENTRYPOINT}"
> >>
> >> SPL_BINARY = "MLO"
> >> UBOOT_SUFFIX = "img"
> >> -UBOOT_MACHINE = "am335x_boneblack_config"
> >> +UBOOT_MACHINE = "am335x_evm_defconfig"
> >> UBOOT_ENTRYPOINT = "0x80008000"
> >> UBOOT_LOADADDRESS = "0x80008000"
> >>
> >> --
> >> 2.21.0
> >>
> >> --
> >> ___
> >> yocto mailing list
> >> yocto@yoctoproject.org
> >> https://lists.yoctoproject.org/listinfo/yocto
>
> --
> =
> DENX Software Engineering GmbH, Managing Director: Wolfgang Denk
> HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
> Phone: +49-8142-66989-53 Fax: +49-8142-66989-80 Email: sba...@denx.de
> =
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Thud Kernel Configuration not Working
On Sat, Apr 13, 2019 at 9:54 PM nick wrote:
>
> Greetings,
> I was trying to build a kernel with these files in a new layer for no smp to
> be enabled but have no
> idea why it doesn't work. This is after looking at the kernel manual and it's
> literally the same
> files excluding the disabling of smp as the chosen option.
>
> .cfg for kernel option is called smp.cfg and this the file's content:
> #Disable SMP
> CONFIG_SMP=n
>
> This is my bbappend called linux-yocto-4.1.8.bbappend:
> # Include kernel configuration fragment
> FILESEXTRAPATHS_prepend := "${THISDIR}/files:"
> SRC_URL += "file://smp.cfg"
>
> If anyone has ideas thanks in advance,
We need a lot more information to help with this. I put the type of
information in the
bugzilla that was opened for this, so I won't repeat it here. Best to
keep all the details
in one place.
Bruce
>
> Nick
>
> --
> ___
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
--
- Thou shalt not follow the NULL pointer, for chaos and madness await
thee at its end
- "Use the force Harry" - Gandalf, Star Trek II
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] QA cycle report for 2.6.2 RC3
>-Original Message- >From: richard.pur...@linuxfoundation.org >Sent: Friday, 12 April, 2019 6:58 PM >To: Jain, Sangeeta ; 'yocto@yoctoproject.org' >; Eggleton, Paul ; 'Michael >Halstead' ; Erway, Tracey M >; 'sjolley.yp...@gmail.com' >; openembedded-core- >requ...@lists.openembedded.org >Cc: Sangal, Apoorv ; Yeoh, Ee Peng > >Subject: Re: QA cycle report for 2.6.2 RC3 > >On Wed, 2019-04-10 at 02:38 +, Jain, Sangeeta wrote: >> >> QA cycle report for 2.6.2 RC3: >> >> No high milestone defects. >> Test results are available at following location: >> ·For results of all automated tests, refer to results at >> public AB [1]. >> ·For other test results, refer to attachment [2]. >> ·For test report for test cases run by Intel and WR team, >> refer attachment [3] >> ·For full test report, refer attachment [4] >> ·For ptest results, please refer to results at public AB [5] >> ·For ptest report, refer to attachment [6] >> 1 new defects are found in this cycle, Beaglebone [7]. >> QA hint: Similar issue for sysemtap failure (bug 13153) was found in >> 2.7 M2 RC1 which is now resolved for master. >> Number of existing issues observed in this release is 3- toaster [8], >> Build-appliance [9] and qemu-shutdown [10] For ptest, regression data >> is not available for this release. 3 packages are facing timeout >> issues: lttng-tools [11], openssh [12] and strace [13]. >> Test result report on Public AB shows following failures: >> buildgalculator.GalculatorTest.test_galculator >> QA Comment: Expected failure for hw limitation >> python.PythonTest.test_python3 >> QA Comment: Failure due to “python3” test case not backported to Thud. >> No bug filed as not real Yocto failure. > >Thanks for running QA on this. Firstly, I can comment on the bugs: > >> [7] Bug 13273 - [2.6.2 RC3] Systemtap doesn't work on beaglebone >> https://bugzilla.yoctoproject.org/show_bug.cgi?id=13273 > >We've root caused this on master and believe we know how to fix this, its a >kernel makefile configuration issue. We can likely document this as a known >issue >and fix in 2.6.3. > >> Previous Bugs observed in this release: >> >> [8] Bug 13191 – [Test Case 1439] Build Failure after adding or >> removing packages with and without dependencies >> https://bugzilla.yoctoproject.org/show_bug.cgi?id=13191 >> >> [9] Bug 12991 - [Bug] [2.6 M4 RC1][Build-Appliance] Bitbake build- >> appliance-image getting failed during building image due to webkitgtk >> package. >> https://bugzilla.yoctoproject.org/show_bug.cgi?id=12991 > >This is a long running issue we've been "ignoring", its likely resource issues >on the >machine/VM running the test. > >> [10] Bug 13234 - [2.7 M3 RC1] qemumips & qemumips64: failed to >> shutdown >> https://bugzilla.yoctoproject.org/show_bug.cgi?id=13234 > >This is an issue root caused to be from 4.19 and 5.0 kernels. I thought >2.6.2 had a 4.18 kernel so shouldn't have this issue? The bug wasn't reopened? 2.6.2 had shutdown issue with qemuarm. Which is a known issue for 2.6 release and marked as won't fix. Correct bug id for Qemu arm shutdown issue is: Bug 12499 - [2.5 M1 RC3] qemuarm: failed to shutdown https://bugzilla.yoctoproject.org/show_bug.cgi?id=12499 Thanks for pointing out! > >> ptest Bugs: >> >> [11] Bug 13255 - [2.7 M3 rc1] lttng-tools ptest facing timeout issue >> https://bugzilla.yoctoproject.org/show_bug.cgi?id=13255 >> >> [12] Bug 13256 - [2.7 M3 rc1] openssh ptest facing timeout issue >> https://bugzilla.yoctoproject.org/show_bug.cgi?id=13256 >> >> [13] Bug 13274 - [2.6.2 RC3] strace ptest facing timeout issue >> https://bugzilla.yoctoproject.org/show_bug.cgi?id=13274 > >ptest has been a bit tricky and we've been actively working these bugs on >master. >Once we have them resolved there we can backport to older releases. > >There is one other critical issue we have with 2.6.2 which is the revert of the >boost upgrade. I'm very reluctant to release without that revert as it caused >problems for a lot of people. > >I'm wondering whether we should rebuild 2.6.2 one commit later and then >release that assuming it passes a rerun of the automated QA (but not the manual >QA). Opinions on that? > >I'd propose fixing the systemtap and ptest issues for 2.6.3. > >Cheers, > >Richard > > Thanks & Regards, Sangeeta Jain -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] [meta-selinux][PATCH] audit: change to use ${WORKDIR} instead ${S}/../
The do_install function is assuming that ${S}/../ is ${WORKDIR},
but this is not true when using `devtool modify audit'.
So change to use ${WORKDIR}.
Signed-off-by: Chen Qi
---
recipes-security/audit/audit_2.8.4.bb | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/recipes-security/audit/audit_2.8.4.bb
b/recipes-security/audit/audit_2.8.4.bb
index c29bb74..594786a 100644
--- a/recipes-security/audit/audit_2.8.4.bb
+++ b/recipes-security/audit/audit_2.8.4.bb
@@ -82,7 +82,7 @@ do_install_append() {
rmdir ${D}/etc/sysconfig/
# replace init.d
- install -D -m 0755 ${S}/../auditd ${D}/etc/init.d/auditd
+ install -D -m 0755 ${WORKDIR}/auditd ${D}/etc/init.d/auditd
rm -rf ${D}/etc/rc.d
if ${@bb.utils.contains('DISTRO_FEATURES', 'systemd', 'true', 'false',
d)}; then
--
2.7.4
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Thud Kernel Configuration not Working
> This is my bbappend called linux-yocto-4.1.8.bbappend:
> # Include kernel configuration fragment
> FILESEXTRAPATHS_prepend := "${THISDIR}/files:"
> SRC_URL += "file://smp.cfg"
I am wondering... Why so old kernel used (4.1.8)?
Zoran
___
On Sun, Apr 14, 2019 at 3:54 AM nick wrote:
>
> Greetings,
> I was trying to build a kernel with these files in a new layer for no smp to
> be enabled but have no
> idea why it doesn't work. This is after looking at the kernel manual and it's
> literally the same
> files excluding the disabling of smp as the chosen option.
>
> .cfg for kernel option is called smp.cfg and this the file's content:
> #Disable SMP
> CONFIG_SMP=n
>
> This is my bbappend called linux-yocto-4.1.8.bbappend:
> # Include kernel configuration fragment
> FILESEXTRAPATHS_prepend := "${THISDIR}/files:"
> SRC_URL += "file://smp.cfg"
>
> If anyone has ideas thanks in advance,
>
> Nick
>
> --
> ___
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
