edison-fw / meta-intel-edison

Here is the meta-intel-edison that builds, tries to stay up to date. Master is based on Yocto Poky Gatesgarth LTS 5.10.yy vanilla kernels. It builds a 32bit kernel (Gatesgarth branch 64bit) with ACPI enabled and corresponding rootfs. Telegram group: https://t.me/IntelEdison Web-site:
https://edison-fw.github.io/meta-intel-edison/
MIT License
60 stars 37 forks source link

Pyro64 proposed #10

Closed htot closed 6 years ago

htot commented 6 years ago

1 - Added 4.14 recipe and switched to that 2 - When booting you can put debugshell on the command, this will fall back to busy box if there is no kernel to boot. But the screen was messed do to a remaining set -x . Clean up. 3 - cross-localdef-native is broken on pyro 2.3.2. According to https://bugzilla.yoctoproject.org/show_bug.cgi?id=12335 the fix will be backported shortly.At that time we need to revert this patch

alext-mkrs commented 6 years ago

Looks good to me by inspection - do you need additional "live" testing, I can do that?

htot commented 6 years ago

I have tested, but as part of a larger set of commits (I am debugging the kernel). This is cherry picked from that. So unless I forgot something, this should build fine. If you test and confirm I'll push or merge.

alext-mkrs commented 6 years ago

No worries, I'm starting the build and will post back when tested.

alext-mkrs commented 6 years ago

Right away - there's a warning like this:

NOTE: preferred version 2.26.% of cross-localedef-native not available (for item cross-localedef-native)
NOTE: versions of cross-localedef-native available: 2.25 2.26

Basically, the dot in the pattern is the reason, as the version itself doesn't have anything after "26". However I wonder why would you need to set the preferred version at all - the one you backported is the newest one, so Yocto will pick it automatically anyway.

alext-mkrs commented 6 years ago

Tested, besides that warning I mentioned earlier, no issues I could spot - builds and runs fine. Given the layer configuration and Yocto default logic, you can simply remove the line, which tries to set the 2.26 as the preferred version - I've tested that as well and it simply picked 2.26.

htot commented 6 years ago

I think when I didn't set the preferred version it still built the old one. Not sure any more. your right, it should be automatic. I'll remove the line entirely. I had a similar warning then corrected this text (corrected again wrong). But because a warning no new warning on 2nd build.