|
Re: Customizing SERIAL_CONSOLES
there can be multiple entries in SERIAL_CONSOLES so you might try
adding instead of replacing
SERIAL_CONSOLES += "115200;ttymxc0"
might work
there can be multiple entries in SERIAL_CONSOLES so you might try
adding instead of replacing
SERIAL_CONSOLES += "115200;ttymxc0"
might work
|
By
Khem Raj
·
#57506
·
|
|
Customizing SERIAL_CONSOLES
Hi,
I’m trying to customize the SERIAL_CONSOLESvariable. In another thread I read this can be done by adding amachine-extra.conf file too my custom layer. So I added “ SERIAL_CONSOLES
Hi,
I’m trying to customize the SERIAL_CONSOLESvariable. In another thread I read this can be done by adding amachine-extra.conf file too my custom layer. So I added “ SERIAL_CONSOLES
|
By
chris yocto
·
#57505
·
|
|
[PATCH yocto-autobuilder-helper] config.json: Set SDKMACHINE to aarch64 for oe-selftest-armhost
Although bitbake.conf sets the default SDKMACHINE to the build
architecture, config.json resets that to i686.
As oe-selftest assumes that the SDKs it builds are usable on the host
machine, we should
Although bitbake.conf sets the default SDKMACHINE to the build
architecture, config.json resets that to i686.
As oe-selftest assumes that the SDKs it builds are usable on the host
machine, we should
|
By
Ross Burton
·
#57504
·
|
|
Sorry, a test
Apologies for the test spam. Hopefully this doesn’t have a legal disclaimer attached.
Ross
Apologies for the test spam. Hopefully this doesn’t have a legal disclaimer attached.
Ross
|
By
Ross Burton
·
#57503
·
|
|
Re: Installing gfortran into native sysroot for libgfortran
I think I've finally figured this out and just wanted to provide some
closure for posterity's sake.
My initial "solution" of clearing the SSTATE_MIRRORS variable was not
actually correct. It turns
I think I've finally figured this out and just wanted to provide some
closure for posterity's sake.
My initial "solution" of clearing the SSTATE_MIRRORS variable was not
actually correct. It turns
|
By
Gregory Anders <greg@...>
·
#57502
·
|
|
Recipe fails at do_rm_work due to failed attempt to delete a named pipe (FIFO)
Hi,
I'm working with a PetaLinux 2021.2 project, which defines a recipe called "petalinux-initramfs-image".
For reasons I don't understand, this recipe fails to build at the do_rm_work task. Looking
Hi,
I'm working with a PetaLinux 2021.2 project, which defines a recipe called "petalinux-initramfs-image".
For reasons I don't understand, this recipe fails to build at the do_rm_work task. Looking
|
By
David Antliff
·
#57501
·
|
|
M+ & H bugs with Milestone Movements WW2"All,
All,
YP M+ or high bugs which moved to a new milestone in WW28 are listed below:
Priority
Bug ID
Short Description
Changer
Owner
Was
Became
High
14065
Automated ptest regression
All,
YP M+ or high bugs which moved to a new milestone in WW28 are listed below:
Priority
Bug ID
Short Description
Changer
Owner
Was
Became
High
14065
Automated ptest regression
|
By
Stephen Jolley
·
#57500
·
|
|
Enhancements/Bugs closed WW28!
All,
The below were the owners of enhancements or bugs closed during the last week!
Who
Count
alejandro@...
2
yogesh.tyagi@...
1
ptsneves@...
1
randy.macleod@...
1
ross.burton@...
1
Grand
All,
The below were the owners of enhancements or bugs closed during the last week!
Who
Count
alejandro@...
2
yogesh.tyagi@...
1
ptsneves@...
1
randy.macleod@...
1
ross.burton@...
1
Grand
|
By
Stephen Jolley
·
#57499
·
|
|
Current high bug count owners for Yocto Project 4.1
All,
Below is the list as of top 35 bug owners as of the end of WW28 of who have open medium or higher bugs and enhancements against YP 4.1. There are 77 possible work days left until the final
All,
Below is the list as of top 35 bug owners as of the end of WW28 of who have open medium or higher bugs and enhancements against YP 4.1. There are 77 possible work days left until the final
|
By
Stephen Jolley
·
#57498
·
|
|
Yocto Project Newcomer & Unassigned Bugs - Help Needed
All,
The triage team is starting to try and collect up and classify bugs which a newcomer to the project would be able to work on in a way which means people can find them. They're being listed on
All,
The triage team is starting to try and collect up and classify bugs which a newcomer to the project would be able to work on in a way which means people can find them. They're being listed on
|
By
Stephen Jolley
·
#57497
·
|
|
missing cgroups when trying to re-mount rootfs from initramfs busybox image
I have busybox with an initramfs. When I try to re-mount the rootfs I
see this. This is with Yocto. Do I need to include systemd in my
initramfs image?
sh-5.0# exec switch_root /root
I have busybox with an initramfs. When I try to re-mount the rootfs I
see this. This is with Yocto. Do I need to include systemd in my
initramfs image?
sh-5.0# exec switch_root /root
|
By
Embedded 1
·
#57496
·
|
|
Re: Installing gfortran into native sysroot for libgfortran
In my notes:
cat /dev/null > conf/locked-signs.inc
Philip
In my notes:
cat /dev/null > conf/locked-signs.inc
Philip
|
By
Philip Balister
·
#57495
·
|
|
Re: Installing gfortran into native sysroot for libgfortran
(Apologies for the double post to the list.)
Philip, would you mind sharing what you did to disable it?
Thanks,
Greg
(Apologies for the double post to the list.)
Philip, would you mind sharing what you did to disable it?
Thanks,
Greg
|
By
Gregory Anders <greg@...>
·
#57494
·
|
|
How to get license text
Hi,
I was wondering if it is possible to get the license information for all of the deployed packages in the image? I know there's a license.manifest file in deploy/licenses, but I'm looking for a
Hi,
I was wondering if it is possible to get the license information for all of the deployed packages in the image? I know there's a license.manifest file in deploy/licenses, but I'm looking for a
|
By
William Huang
·
#57493
·
|
|
Re: Installing gfortran into native sysroot for libgfortran
I didn't know the sstate could be locked -- how would one unlock it? Could you
point me toward some relevant docs?
After some cursory searching the only thing I've found is the
I didn't know the sstate could be locked -- how would one unlock it? Could you
point me toward some relevant docs?
After some cursory searching the only thing I've found is the
|
By
Gregory Anders <greg@...>
·
#57492
·
|
|
ALTERNATIVE and RDEPENDS
Hi all,
is there a way to set the package metadata in a way that it would require one of the packages providing a tool via the ALTERNATIVE_ mechanism?
E.g. sed for instance could be provided by
Hi all,
is there a way to set the package metadata in a way that it would require one of the packages providing a tool via the ALTERNATIVE_ mechanism?
E.g. sed for instance could be provided by
|
By
Konrad Weihmann <kweihmann@...>
·
#57491
·
|
|
Re: source-less python
Hi,
So after a little bit of research, I've implemented this feature in poky.
The way buildroot works, is that it doesn't create any .pyc files during the build process of single packages but has a
Hi,
So after a little bit of research, I've implemented this feature in poky.
The way buildroot works, is that it doesn't create any .pyc files during the build process of single packages but has a
|
By
Aurum Nitrogen
·
#57490
·
|
|
Re: meta-riscv layer *seems* to have broken opensbi_%.bbappend file
This is a bug and this should be fixed to use full machine name for override since we do not have nezha SoC override
No it’s unrelated
This is a bug and this should be fixed to use full machine name for override since we do not have nezha SoC override
No it’s unrelated
|
By
Khem Raj
·
#57489
·
|
|
meta-riscv layer *seems* to have broken opensbi_%.bbappend file
the SRC_URI line:
SRC_URI:append:nezha = " \ ...
seems odd since the machine name is actually "nezha-allwinner-d1", not
just "nezha". i checked and the two listed patches there don't appear
to be
the SRC_URI line:
SRC_URI:append:nezha = " \ ...
seems odd since the machine name is actually "nezha-allwinner-d1", not
just "nezha". i checked and the two listed patches there don't appear
to be
|
By
Robert P. J. Day
·
#57488
·
|
|
Re: Installing gfortran into native sysroot for libgfortran
It is. It was great fun to find the path to disable it when I also had this issue :)
Philip
>
It is. It was great fun to find the path to disable it when I also had this issue :)
Philip
>
|
By
Philip Balister
·
#57487
·
|