public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: James <wireless@tampabay.rr.com>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Re: new linux router
Date: Fri, 6 Mar 2015 17:37:38 +0000 (UTC)	[thread overview]
Message-ID: <loom.20150306T180251-442@post.gmane.org> (raw)
In-Reply-To: 20150306080215.7063e5f7@digimed.co.uk

Neil Bothwick <neil <at> digimed.co.uk> writes:


> > I'm not sure the arch of a 500 MHz AMD Geode LX800;
> > isn't that compatible with i686 binaries? I found this:

> The Geode LX800 is more like an i486. I used to use a box based on one
> (not as a router) in the days before the Raspberry Pi. I used to build
> packages in a chroot on my i7 box, using these settings

Yes, this processor is a bit of a chameleon. Several companies
manufactured it and under several different versions with slightly
different instruction sets inside. You really have look at
the part id number and the silicon vendors data sheets or
test out some of the options to be for sure. They all mask (label
print) the chips to look the same....... Some are full i686
and some are crappy i486 and some are in between. They are intended
for embedded products, so the firmware folks developing the codes
get the accurate data from the chip vendors directly. It's 
kinda like buying drugs in south america, you better know
your connection, really well (aha ha ha ha). Sorry, but the old,
jaded embedded engineer in me never really gets too quiet.....


> CFLAGS="-O2 -march=geode -pipe -fomit-frame-pointer"
> CXXFLAGS="${CFLAGS}"
> CHOST="i486-pc-linux-gnu" 
> MAKEOPTS="-j16 -l10"

This would be a keen starting point combined 
with  /proc probing....


> MAKEOPTS="-j16 -l10"

Might not be the best settings? [1] 
Look for these lines in the reference thread and translate 
to a makeopts syntax? Interesting discussion.

MAKE -j $nthreads -l $((nthreads-1)).8
EMERGE –jobs $((nthreads+1) –load-average ${nthreads}.4


thx,
James


[1] https://blogs.gentoo.org/ago/2013/01/14/makeopts-jcore-1-is-
not-the-best-optimization/




  reply	other threads:[~2015-03-06 17:38 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-04 15:10 [gentoo-user] new linux router James
2015-03-04 16:18 ` whytlze
2015-03-04 21:10   ` [gentoo-user] " James
2015-03-04 20:37 ` [gentoo-user] " Bruce Schultz
2015-03-04 21:24   ` [gentoo-user] " James
2015-03-05  1:12     ` Bruce Schultz
2015-03-05  4:21       ` James
2015-03-05 18:59 ` Nicolas Sebrecht
2015-03-06  2:03   ` James
2015-03-06  8:02     ` Neil Bothwick
2015-03-06 17:37       ` James [this message]
2015-03-06 21:55         ` Neil Bothwick
2015-03-07 17:31           ` James
2015-03-08 17:08             ` Neil Bothwick
2015-03-06 11:29     ` Nicolas Sebrecht
2015-03-06 17:01       ` James
2015-03-28 18:57         ` lee
2015-03-07  9:37 ` [gentoo-user] " thegeezer
2015-03-07 10:16 ` Marc Stuermer
2015-03-12 15:51 ` [gentoo-user] " Hans

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=loom.20150306T180251-442@post.gmane.org \
    --to=wireless@tampabay.rr.com \
    --cc=gentoo-user@lists.gentoo.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