All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marcin Juszkiewicz <marcin@juszkiewicz.com.pl>
To: openembedded-devel@lists.openembedded.org
Subject: RFC: Geode machines support changes
Date: Tue, 17 Nov 2009 13:37:17 +0100	[thread overview]
Message-ID: <200911171337.35127.marcin@juszkiewicz.com.pl> (raw)


Hi

Currently .dev tree supports AMD GeodeGX and GeodeLX based machines:

- "geodegx"        - generic config
- "iei-nanogx-466" - IEI Nano GX-466

- "geodelx"        - generic config
- "alix"           - PC Engines Alix 1c/d mainboard
- "xo"             - OLPC XO v1

For "geodegx" we have linux-geodegx-2.4.24 kernel which was added with 
machine. Looks like no one use it and we got linux-2.6.31 update some time ago 
from Petr Štetiar (who works on "iei-nanogx-466" SBC). Update needs to be 
selected in machine config anyway and is not yet building.

For "geodelx" we use linux-geodelx-2.6.11 which also was added with machine. 
Other good device with this CPU is "alix" which is now set to linux-2.6.25 as 
I did not booted this board for quite long time. OLPC is 3rd device with this 
CPU which we support.

GeodeLX processor is i586 class. Has MMX, 3Dnow and few other flags from that 
family. We treat it as i486 anyway as someone noted that they are faster that 
way.

I would like to do few changes:

1. drop "geodelx" kernel and machine config.
2. rename "alix" to "geodelx" and use Alix defconfig
3. move all target related flags from machine configs to tune-geode.inc
   - TARGET_ARCH
   - glibc tune (GLIBC_ADDONS, GLIBC_EXTRA_OECONF)

Then we can consider changing TARGET_ARCH to i586 for Geode machines.

Opinions? suggestions?

Regards, 
-- 
JID:      hrw@jabber.org
Website:  http://marcin.juszkiewicz.com.pl/
LinkedIn: http://www.linkedin.com/in/marcinjuszkiewicz





             reply	other threads:[~2009-11-17 12:38 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-17 12:37 Marcin Juszkiewicz [this message]
2009-11-17 13:23 ` RFC: Geode machines support changes Stefan Schmidt
2009-11-17 14:02 ` Marcin Juszkiewicz
2009-11-17 14:08   ` Otavio Salvador
2009-11-17 15:22 ` Petr Štetiar

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=200911171337.35127.marcin@juszkiewicz.com.pl \
    --to=marcin@juszkiewicz.com.pl \
    --cc=openembedded-devel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.