From: Rolf Leggewie <no2spam@nospam.arcornews.de>
To: openembedded-devel@openembedded.org
Subject: Re: mtn disapprove
Date: Sun, 13 Jan 2008 16:06:58 +0100 [thread overview]
Message-ID: <fmd9ej$nt$1@ger.gmane.org> (raw)
In-Reply-To: <1200229756.6056.4.camel@HD>
Thomas Kunze schrieb:
> Have only things in zaurus-2.6.inc that are common to all zaurus.
Hehe, have a look at 4989371c8e7cec943a964b459ec3e71c0f547204 which I
committed yesterday. It already does exactly as you suggest. My mail
about it has not made it to the list, though. There seems to be a few
hours backlog with the OE ml.
From the commit message
conf/machine/: fix configuration for Strongarm devices
* replace erroneous TARGET_CC_ARCH line optimising for xscale instead of
strongarm
* remove inclusion of tune-strongarm.inc from collie.conf and replace it
with the correct TARGET_CC_ARCH. Collie is the only Strongarm 1110
device in OE and thus needs special treatment
* rename tune-strongarm.inc to tune-strongarm1100.inc and leave a short
note to make it clear the file only applies to Strongarm 1100 devices.
collie is apparently Strongarm 1110, all other Zaurus are 1100.
next prev parent reply other threads:[~2008-01-13 15:07 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-11 7:36 mtn disapprove Koen Kooi
2008-01-11 8:30 ` Rolf Leggewie
2008-01-11 8:38 ` Koen Kooi
2008-01-11 16:53 ` Rolf Leggewie
2008-01-11 18:48 ` Rolf Leggewie
2008-01-11 19:20 ` Koen Kooi
2008-01-11 19:32 ` Rolf Leggewie
2008-01-11 23:22 ` Thomas Kunze
2008-01-12 10:39 ` Rolf Leggewie
2008-01-13 13:09 ` Thomas Kunze
2008-01-13 15:06 ` Rolf Leggewie [this message]
2008-01-13 16:30 ` Koen Kooi
2008-01-14 11:21 ` Florian Boor
2008-01-14 11:44 ` Rolf Leggewie
2008-01-11 19:36 ` Rolf Leggewie
2008-01-11 11:06 ` ohviey1
-- strict thread matches above, loose matches on Subject: below --
2008-01-11 20:57 QMan
2008-01-12 10:42 ` Rolf Leggewie
2008-01-12 11:41 ` Richard Purdie
2008-01-13 20:26 QMan
2008-01-28 13:51 ` Rolf Leggewie
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='fmd9ej$nt$1@ger.gmane.org' \
--to=no2spam@nospam.arcornews.de \
--cc=openembedded-devel@lists.openembedded.org \
--cc=openembedded-devel@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