From: Mike Frysinger <vapier@gentoo.org>
To: gentoo-embedded@lists.gentoo.org
Cc: "M. Edward (Ed) Borasky" <znmeb@cesmail.net>
Subject: Re: [gentoo-embedded] gumstix anyone?
Date: Tue, 14 Nov 2006 16:07:46 -0500 [thread overview]
Message-ID: <200611141607.47496.vapier@gentoo.org> (raw)
In-Reply-To: <4559DE0B.5070909@cesmail.net>
[-- Attachment #1: Type: text/plain, Size: 1125 bytes --]
On Tuesday 14 November 2006 10:17, M. Edward (Ed) Borasky wrote:
> I am getting a couple of Gumstix small computers, and I'm wondering if
> there are any Gentoo embedded folks working with them.
i started to buy a Gumstix but then decided to buy some NSLU2s/Lofts instead
> What I found interesting is that the Gumstix "buildroot" environment
> contains a package called "portage". Is this a Gentoo Portage as we know
> it, or something else called "portage"?
gumstix just copies their buildroot env from the original one that was spawned
from uclibc:
http://buildroot.uclibc.org/
they include their own fixes on top of it i imagine
i have commit access to the original buildroot and ive added portage to that
back when i was using buildroot to bootstrap Gentoo/embedded ... but since
Gentoo can be used to bootstrap Gentoo/embedded, i dont really bother with
buildroot anymore
considering Gumstix is simply a little endian arm, there's no reason you cant
take existing little endian arm stages and use those on the board ... you'd
prob still have to get your kernel from them though
-mike
[-- Attachment #2: Type: application/pgp-signature, Size: 827 bytes --]
prev parent reply other threads:[~2006-11-14 21:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-14 15:17 [gentoo-embedded] gumstix anyone? M. Edward (Ed) Borasky
2006-11-14 18:16 ` Benjamin Burns
2006-11-15 2:57 ` M. Edward (Ed) Borasky
2006-11-14 21:07 ` Mike Frysinger [this message]
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=200611141607.47496.vapier@gentoo.org \
--to=vapier@gentoo.org \
--cc=gentoo-embedded@lists.gentoo.org \
--cc=znmeb@cesmail.net \
/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