|
Invalid checksums for SRC_URI ignored?
Michael Opdenacker
Greetings,
I reused a simple "hello" recipe and added a non-matching checksum to it: ... SRC_URI = "file://helloworld.c" SRC_URI[md5sum] = "34f0efd76b4f18888888888833cdd129" ... The rest of the recipe comes from https://git.openembedded.org/openembedded-core/tree/meta-skeleton/recipes-skeleton/hello-single. Why doesn't Bitbake stop, reporting that the checksum doesn't match the source file? Anyway, why does the recipe build without a checksum? Shouldn't checksums be mandatory? I'm using the "master" version of Poky. Thanks in advance Michael. -- Michael Opdenacker, Bootlin Embedded Linux and Kernel engineering https://bootlin.com
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Re: Honister broken WiFi communication
JH
Hi Tomasz,
Thanks for your response. Are you using custom Linux kernel / custom device tree? Maybe there isYes, but the Zeus build image uses the same device tree that could run WiFi connection without any issues, I am comparing the same source and configuration between Zeus and Honister, the only difference is the two different OE Yocto versions. Thank you. Kind regards, - jh
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Re: Honister broken WiFi communication
tomzy
Hi JH, Are you using custom Linux kernel / custom device tree? Maybe there is
Kind regards,
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
[yocto-autobuilder2][PATCH] config.py: enable debian11 for hardknott
Anuj Mittal
Signed-off-by: Anuj Mittal <anuj.mittal@intel.com>
--- config.py | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/config.py b/config.py index 4c0b83b..0f99557 100644 --- a/config.py +++ b/config.py @@ -149,7 +149,7 @@ all_workers = workers + workers_bringup + workers_buildperf + workers_arm # Worker filtering for older releases workers_prev_releases = { - "hardknott" : ("centos7", "centos8", "debian8", "debian9", "debian10", "fedora31", "fedora32", "fedora33", "fedora34", "opensuse152", "ubuntu1604", "ubuntu1804", "ubuntu2004", "perf-"), + "hardknott" : ("centos7", "centos8", "debian8", "debian9", "debian10", "debian11", "fedora31", "fedora32", "fedora33", "fedora34", "opensuse152", "ubuntu1604", "ubuntu1804", "ubuntu2004", "perf-"), "gatesgarth" : ("centos7", "centos8", "debian8", "debian9", "debian10", "fedora30", "fedora31", "fedora32", "opensuse150", "opensuse151", "opensuse152", "ubuntu1604", "ubuntu1804", "ubuntu1904", "ubuntu2004", "perf-"), "dunfell" : ("centos7", "centos8", "debian8", "debian9", "debian10", "debian11", "fedora29", "fedora30", "fedora31", "fedora32", "fedora33", "fedora34", "opensuse150", "opensuse151", "opensuse152", "ubuntu1604", "ubuntu1804", "ubuntu1904", "ubuntu2004", "perf-"), "zeus" : ("centos7", "debian8", "debian9", "debian10", "fedora28", "fedora29", "fedora30", "opensuse150", "opensuse151", "ubuntu1604", "ubuntu1804", "ubuntu1904", "perf-"), -- 2.34.1
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Re: Honister broken WiFi communication
JH
Hi Rudolf,
Thanks for your response and comments. If you run ifconfig -a does your WiFi interface show up? If not there is anNot that bad, the WiFi interfaces was fine, but it could not get dhcp response and IP address so an automatic private IP address 169.254 was assigned mlan0 Link encap:Ethernet HWaddr D4:CA:6E:A4:E8:B4 inet addr:169.254.193.101 Bcast:169.254.255.255 Mask:255.255.0.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:2 errors:0 dropped:0 overruns:0 frame:0 TX packets:56 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:330 (330.0 B) TX bytes:16392 (16.0 KiB) I could see WiFi information well, it is not a major problem, but the subtle issues are connman and wpa_supplicant did not set up the WiFi driver correctly. Connected to 34:08:04:12:b1:a2 (on mlan0) SSID: JupiterIoT freq: 2437 RX: 660 bytes (4 packets) TX: 46622 bytes (129 packets) signal: -57 dBm rx bitrate: 1.0 MBit/s tx bitrate: 72.2 MBit/s MCS 7 short GI bss flags: short-slot-time dtim period: 1 beacon int: 100 Did you install the regulatory database?Did you mean to enable CONFIG_CFG80211_INTERNAL_REGDB? No, I did not install it in the Zeus version either so I don't see that could be an issue. What error messages are you seeing when attempting to connect to a WiFiNo error in connman, I don't think it is connman or wpa_supplicant issue, my suspicion is something missing in Honister built image to prevent connman and wpa_supplicant to set up the WiFi driver correctly. It is not the first time I have the WiFi setup trouble to get WiFi 169.254 address, when I upgraded from Thud to Zeus, I got the exactly the same problem that WiFi was assigned by a 169.254 address, no dhcp response, at time, I was totally convinced it was connman issue, I spend several months to debug connman and wpa_supplicant without any results, then after waiting several months to pull updated Zeus again, that problem was disappeared miraculous, that is why I suspect the same problem in oe-core and bitbake in Honister as well. Are there anyone in oe-core and bitbake tested connman, wpa_supplicant for the current Honister branch? I can help to test and to debug it if more advanced people in oe-core, bitbake, kernel, WiFi driver mwifiex can provide me more information. Thank you. Kind regards, - jupiter
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Re: gdb with a broken sdk
On 1/16/22 3:26 PM, dacav wrote:
On Wed, Jan 12, 2022 at 02:15:38AM +0000, dacav wrote:perhaps gdb-cross-${TARGET_ARCH} would be more generic.How can I include aarch64-foobar-gdb in the devshell's PATH?Follow up on this thread: I've been kindly helped by kroon on #yocto. At this point I can just use `bitbake -c devshell $myrecipe` and the
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Re: Advertise lore.kernel.org archives on website?
Michael Opdenacker
On 1/18/22 12:04 PM, Richard Purdie wrote:
On Tue, 2022-01-18 at 10:44 +0100, Michael Opdenacker wrote:Greetings,Sounds fine to me. Thanks for the feedback. Done on https://www.yoctoproject.org/community/mailing-lists/ I added lore.kernel.org links when applicable, and also added the openembedded-devel mailing list which was missing. I could shorten "Archives / Public Inbox" by just "Public Inbox" if you think it makes more sense. Cheers Michael. -- Michael Opdenacker, Bootlin Embedded Linux and Kernel engineering https://bootlin.com
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Re: Building uImage with appended DTB
Nicolas Jeker
On 17 Jan 2022, at 06:41, rgovostes@gmail.com wrote:Just a short hint if you didn’t discover it yourself, there is a (very) old BSP available from PHYTEC [1]. The downloads don’t seem to work, but they’re available on a probably forgotten FTP server [2]. [1]: https://web.archive.org/web/20120501212117/http://www.phytec.com/products/linux/bsp-LPC3180.html [2]: ftp://ftp.phytec.com/temp/PCM-031_phyCORE-LPC3180
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Yocto Project Status WW03`22
Stephen Jolley
Current Dev Position: YP 3.5 M2 Next Deadline: 17th Jan. 2022 YP 3.5 M2 build
Next Team Meetings:
Key Status/Updates:
Ways to contribute:
YP 3.5 Milestone Dates:
Upcoming dot releases:
Tracking Metrics:
The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at: https://wiki.yoctoproject.org/wiki/TSC
The Status reports are now stored on the wiki at: https://wiki.yoctoproject.org/wiki/Weekly_Status
[If anyone has suggestions for other information you’d like to see on this weekly status update, let us know!]
Thanks,
Stephen K. Jolley Yocto Project Program Manager ( Cell: (208) 244-4460 * Email: sjolley.yp.pm@...
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Re: Honister broken WiFi communication
Hi JH, On Tue, Jan 18, 2022, 01:54 JH <jupiter.hce@...> wrote: Hi, Yes, I have, but with Network Manager instead of connman. WiFi works just fine.
There are a lot of pieces in the chain and it is not obvious from your description where it is broken. If you run ifconfig -a does your WiFi interface show up? If not there is an issue with the driver. Use dmesg and filter for the driver. Often a driver cannot load the firmware. What is your WiFi hardware? Did you install the regulatory database? What error messages are you seeing when attempting to connect to a WiFi network? Did you look at the connman logs?
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Re: gdb with a broken sdk
dacav
On Wed, Jan 12, 2022 at 02:15:38AM +0000, dacav wrote:
How can I include aarch64-foobar-gdb in the devshell's PATH?Follow up on this thread: I've been kindly helped by kroon on #yocto. The trick consists in adding a build-time dependency to gdb-cross-aarch64 in my recipe: DEPEND = "gdb-cross-aarch64" At this point I can just use `bitbake -c devshell $myrecipe` and the debugger is available. Bonus: the devshell turns out to be very useful as a replacement for the SDK: the environment allows me to do the cross-compilation with just a `make`, while earlier I needed to run `bitbake $myrecipe` and wait several seconds. - dacav
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Re: Advertise lore.kernel.org archives on website?
Richard Purdie
On Tue, 2022-01-18 at 10:44 +0100, Michael Opdenacker wrote:
Greetings,Sounds fine to me. Cheers, Richard
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Honister broken WiFi communication
JH
Hi,
Has anyone successfully built a Linux image by Honister to run WiFi driver, connman and wpa_supplicant for WiFi interface? I could build an image by Zeus to run WiFi driver, wpa_supplicant, connman and dbus well, but after upgrading to Honister, the Linux image building was fie, but the WiFi is now broken, the WiFi failed to respond DHCP the WiFi could not connect to Internet, something is broken between wpa_supplicant and connman which setting kernel WiFi driver, WiFi interface and connection. I don't see any issues in kernel WiFi driver, connman and wpa_supplicant, something missing in the Linux image failing to set up the WiF network interface. Appreciate your comments. Thank you. Kind regards, - jupiter
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Advertise lore.kernel.org archives on website?
Michael Opdenacker
Greetings,
I see more and more people using links to the lore.kernel.org archives, for example the ones for this list: https://lore.kernel.org/yocto/ These look more convenient to use than the ones on https://lists.yoctoproject.org/. So what about advertising such archives on https://www.yoctoproject.org/community/mailing-lists/, at least for the ones which have archives on lore.kernel.org? I was thinking about just adding an "(archives)" or "(archives / public mailbox) link at the end of the description for each list. What do you think? Cheers Michael. -- Michael Opdenacker, Bootlin Embedded Linux and Kernel engineering https://bootlin.com
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Installing only python .pyc files onto the image
#yocto
Sam
Was wondering if there was a way to edit the distitils3.bbclass or a similar file to only install the python .pyc files onto a yocto image?
I saw something about editing the distutils-common-base.bbclass online, however, it was only mentioned and not elaborated on. I am currently working with a setup that installs .py files, then generates the .pyc files and removes the .py files. I am now looking for a method that will only install the .pyc files. Any help would be appreciated.
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Enhancements/Bugs closed WW03!
Stephen Jolley
All,
Thanks,
Stephen K. Jolley Yocto Project Program Manager ( Cell: (208) 244-4460 * Email: sjolley.yp.pm@...
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Current high bug count owners for Yocto Project 3.5
Stephen Jolley
All,
Thanks,
Stephen K. Jolley Yocto Project Program Manager ( Cell: (208) 244-4460 * Email: sjolley.yp.pm@...
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Yocto Project Newcomer & Unassigned Bugs - Help Needed
Stephen Jolley
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 the triage page under the appropriate heading: https://wiki.yoctoproject.org/wiki/Bug_Triage#Newcomer_Bugs Also please review: https://www.openembedded.org/wiki/How_to_submit_a_patch_to_OpenEmbedded and how to create a bugzilla account at: https://bugzilla.yoctoproject.org/createaccount.cgi The idea is these bugs should be straight forward for a person to help work on who doesn't have deep experience with the project. If anyone can help, please take ownership of the bug and send patches! If anyone needs help/advice there are people on irc who can likely do so, or some of the more experienced contributors will likely be happy to help too.
Also, the triage team meets weekly and does its best to handle the bugs reported into the Bugzilla. The number of people attending that meeting has fallen, as have the number of people available to help fix bugs. One of the things we hear users report is they don't know how to help. We (the triage team) are therefore going to start reporting out the currently 401 unassigned or newcomer bugs.
We're hoping people may be able to spare some time now and again to help out with these. Bugs are split into two types, "true bugs" where things don't work as they should and "enhancements" which are features we'd want to add to the system. There are also roughly four different "priority" classes right now, “3.5, “3.6”, "3.99" and "Future", the more pressing/urgent issues being in "3.4" and then “3.5”.
Please review this link and if a bug is something you would be able to help with either take ownership of the bug, or send me (sjolley.yp.pm@...) an e-mail with the bug number you would like and I will assign it to you (please make sure you have a Bugzilla account). The list is at: https://wiki.yoctoproject.org/wiki/Bug_Triage_Archive#Unassigned_or_Newcomer_Bugs
Thanks,
Stephen K. Jolley Yocto Project Program Manager ( Cell: (208) 244-4460 * Email: sjolley.yp.pm@...
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Re: Building uImage with appended DTB
Ryan Govostes
A solution that seems to work is to create a new .bbclass inherited from my layer's linux .bbappend file that implements uboot_prep_kimage:append() to append the DTB to linux.bin. This code would run at the beginning of do_uboot_mkimage() before the uImage is created.
There are a couple of prerequisites such as setting KEEPUIMAGE = "yes" and KERNEL_DEVICETREE_BUNDLE = "0". https://gist.github.com/rgov/0628785685ab858a99c5bfca626c1d8f I would still be curious to know why KERNEL_DEVICETREE_BUNDLE doesn't work as expected if that is supposed to be the supported method of achieving this, but my solution at least lets me move on.
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
[psplash][PATCH] psplash: Fix double buffering initialization
Horn, Michal
Some fb drivers do not implement double buffering completely or correctly.
For example mxsfb driver does not set yres_virtual to double on
initialization, nor it allows its doubling by FBIOPUT_VSCREENINFO ioctl
call. In such case, the double buffering gets enabled, but psplash fails
to display every second frame with error 'psplash_fb_flip: FBIOPAN_DISPLAY failed: Invalid argument'.
Panning the display by FBIOPAN_DISPLAY ioctl is always checking carefully
that the resolution, virtual buffer resolutin and offsets are in
bounds at fb_pan_display - https://elixir.bootlin.com/linux/v4.9.275/source/drivers/video/fbdev/core/fbmem.c#L891.
Swapping the front and back buffers is done by switching the
yoffset between 0 and yres values. For double buffering, the whole buffer
must have yres_virtual buffer size double of yres.
But in case of the mxsfb driver, the yres_virtual is always equal to yres,
so drawing with the offset set to yres would overrun the buffer. So the
panning is stopped and error 'Invalid argument' is returned.
Psplash tries to double the yres_virtual on initialization by FBIOPUT_VSCREENINFO ioctl call,
that at some point calls the mxsfb_check_var - https://elixir.bootlin.com/linux/v4.9.275/source/drivers/video/fbdev/mxsfb.c#L269
function, which for some reason always sets the yres_virtual back to yres,
effectively canceling the doubling. But no error is returned in this case,
so it gets silently ignored.
So in general, checking for the ioctl call success is not enough as some drivers may pass this test, but fail double buffering anyway. So now we double check the yres_virtual on fb_new and disable double
buffering in case of doubling yres_virtual fails. Signed-off-by: Michal Horn <michalhorn@...>
---
psplash-fb.c | 14 ++++++++++++--
1 file changed, 12 insertions(+), 2 deletions(-)
diff --git a/psplash-fb.c b/psplash-fb.c
index 2babb5f..1b73807 100644
--- a/psplash-fb.c
+++ b/psplash-fb.c
@@ -213,8 +213,18 @@ psplash_fb_new (int angle, int fbdev_id)
perror(" Error getting the fixed framebuffer info");
goto fail;
} else {
- DBG("Virtual resolution set to double");
- fb->double_buffering = 1;
+ if (ioctl(fb->fd, FBIOPAN_DISPLAY, &fb_var) == -1) {
+ fprintf(stderr, "warning: FBIOPAN_DISPLAY failed, "
+ "double buffering disabled\n");
+ } else {
+ if (fb_var.yres_virtual == fb_var.yres * 2) {
+ DBG("Virtual resolution set to double");
+ fb->double_buffering = 1;
+ } else {
+ fprintf(stderr, "warning: Doubling virtual "
+ "resolution failed, double buffering disabled\n");
+ }
+ }
}
}
}
--
2.25.1
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|