I'm trying to piece together the various load addresses used in the boot
sequence. I have built core-image-minimal for a Beaglebone. How can I
determine which load address and entry point is used when mkimage is called
for the kernel? Should I dig in to the recipe? Search some log files? I've
tried
I actually wasn't able to reproduce the issue.I added alexapi to my
IMAGE_INSTALL and ran a build, see below:
[clsulliv@clsulliv build]$ bitbake core-image-minimal
Parsing recipes: 100%
|
python-setuptools-scm-native is needed at build time for:
python-cheroot
python-cherrypy
python-portend
python-tempora
Signed-off-by: Tim Orling
---
recipes-devtools/python/python-cheroot_5.1.0.bb | 2 +-
recipes-devtools/python/python-cherrypy_10.1.1.bb | 2 +-
recipes-devtools/python
From: Libertad Cruz
Added OpenSuse 42.3, Fedora 26 and Ubuntu 17.04 distributions.
Removed unsupported distribution OpenSuse 13.2, Ubuntu 16.10.
Signed-off-by: Libertad Cruz
---
scripts/full-test-cycle-wrapper.sh | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/scripts/f
Attendees: Saul, Stephen, Joshua L., Richard, Paul, Stephano, Joshua W., Ross,
Libby, Trevor, Christopher,
Agenda:
* Opens collection - 5 min (Stephen)
* Yocto Project status - 5 min (Stephen/team)
YP 2.4 M1 has been released
YP 2.1.3 has been released
YP 2.3.1 and YP 2.2.2 are still planned, bu
- We need various python3 modules and we can only really solve this
problem by including all python3-modules.
- aa-easyprof needs to have its shebang corrected, do so.
- The apparmor initscript depends on functions that LSB does not require
so we must provide them. In some cases it's using non
On Mon, 2017-07-10 at 14:04 -0700, Stephano Cetola wrote:
> Certain distros (Ubuntu) use a less desirable shell for /bin/sh
> (dash). In some edge cases, if we source oe-init-build-env from
> outside the OEROOT folder, the script will fail (as stated in the
> oe-init-build-env script). By adding a
On Mon, 2017-07-10 at 14:05 -0700, Stephano Cetola wrote:
> Using awk, sed, or grep to pull a shell variable out of stdio proved
> complex. Instead, simply cat the entire "inc" file to stdio and use
> python/regex to find the variable.
Merged, thanks!
> Signed-off-by: Stephano Cetola
> ---
> ..
Hi Khem,
i.A. Dr.-Ing. Matthias Schöpfer | ithinx GmbH | Software Engineer
Phone: +49 (221) 99589-332 | Fax: +49 (221) 99 589-199 | E-Mail:
matthias.schoep...@ithinx.io
On 07/10/2017 07:27 PM, Khem Raj wrote:
> On 7/10/17 9:19 AM, Dr. Matthias Schöpfer wrote:
>> Hi!
>>
>> We are using y
