From: Steffen Sledz <sledz@dresearch-fe.de>
To: Koen Kooi <koen@dominion.thruhere.net>
Cc: Christopher Larson <clarson@kergoth.com>,
openembedded-core <openembedded-core@lists.openembedded.org>
Subject: Re: fido -> jethro switching problem
Date: Mon, 18 Jan 2016 09:28:49 +0100 [thread overview]
Message-ID: <569CA241.20805@dresearch-fe.de> (raw)
In-Reply-To: <6AFD6AF0-3B94-44BB-BAA0-30EBB9747193@dominion.thruhere.net>
On 15.01.2016 15:29, Koen Kooi wrote:
>> Op 15 jan. 2016 om 15:26 heeft Steffen Sledz <sledz@dresearch-fe.de> het volgende geschreven:
>> It seems that all machines based on armv5e are affected.
>
> FWIW, I'm seeing the same problem. The last time it happened it was due to the fixup angstrom does for broken arm BSPs
What commits do you talking about ("last time it happened")?
https://github.com/Angstrom-distribution/meta-angstrom/commit/7f3d898930077710dfa42150882bce60d437af7d ?
https://github.com/Angstrom-distribution/meta-angstrom/commit/4b2e8ecb9a82109022727f6d80b8db56ae493fe8 ?
Or something else?
--
DResearch Fahrzeugelektronik GmbH
Otto-Schmirgal-Str. 3, 10319 Berlin, Germany
Tel: +49 30 515932-237 mailto:sledz@dresearch-fe.de
Fax: +49 30 515932-299
Geschäftsführer: Dr. Michael Weber, Werner Mögle;
Amtsgericht Berlin Charlottenburg; HRB 130120 B;
Ust.-IDNr. DE273952058
next prev parent reply other threads:[~2016-01-18 8:28 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-15 12:03 fido -> jethro switching problem Steffen Sledz
2016-01-15 13:06 ` Richard Purdie
2016-01-15 13:24 ` Steffen Sledz
2016-01-15 14:26 ` Steffen Sledz
2016-01-15 14:29 ` Koen Kooi
2016-01-18 8:28 ` Steffen Sledz [this message]
2016-01-18 8:41 ` Koen Kooi
2016-01-18 10:10 ` Steffen Sledz
2016-01-18 10:19 ` Koen Kooi
2016-01-18 11:55 ` Steffen Sledz
2016-01-18 12:25 ` Koen Kooi
2016-01-15 14:29 ` Richard Purdie
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=569CA241.20805@dresearch-fe.de \
--to=sledz@dresearch-fe.de \
--cc=clarson@kergoth.com \
--cc=koen@dominion.thruhere.net \
--cc=openembedded-core@lists.openembedded.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox