From: Bruce Hill <daddy@happypenguincomputers.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: {OT} Will ARM take over the world?
Date: Wed, 12 Dec 2012 12:40:50 -0600 [thread overview]
Message-ID: <20121212184050.GA8486@server> (raw)
In-Reply-To: <loom.20121212T183853-566@post.gmane.org>
On Wed, Dec 12, 2012 at 05:55:53PM +0000, James wrote:
> Bruce Hill <daddy <at> happypenguincomputers.com> writes:
>
>
> > Wish my Samsung Galaxy S could have it's piece of crap Android system replaced
> > by arm-linux -- if not it will drive me back to an iPhone.
>
> Your problem defined:
>
> http://www.androidpolice.com/2012/05/03/yep-its-pretty-likely-the-galaxy-s-iii-wont-have-a-quad-core-processor-in-the-us/
>
> http://en.wikipedia.org/wiki/Exynos_(system_on_chip)
>
> Dev board:
>
> http://www.engadget.com/2012/10/26/samsung-launches-arndale-community-board/
>
> Now go find embedded (gentoo?) Linux developers that have or are working
> on a port to the Arm15.
>
> On this page:
> http://www.arm.linux.org.uk/developer/machines/
>
> Look at entry: 3825
>
> All you really got to do is buy a dev board and give it to either
> Armin76 or Vapier; they'll get embedded gentoo on that puppy and
> figure out how to hack your Galaxy S-III. It's on my todo list.
>
> http://armin762.wordpress.com/
> http://www.gentoo.org/proj/en/base/embedded/
>
> gentoo.embedded is your friend!
>
> Good hunting. post back and I'll get a dev board too!
Too busy with RL atm, but afaict that doesn't apply to my Samsung Galaxy S.
Notice, just S ... nothing afterwards.
--
Happy Penguin Computers >')
126 Fenco Drive ( \
Tupelo, MS 38801 ^^
support@happypenguincomputers.com
662-269-2706 662-205-6424
http://happypenguincomputers.com/
Don't top-post: http://en.wikipedia.org/wiki/Top_post#Top-posting
next prev parent reply other threads:[~2012-12-12 18:42 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-09 3:25 [gentoo-user] {OT} Will ARM take over the world? Grant
2012-12-09 3:51 ` Michael Mol
2012-12-09 19:24 ` Florian Philipp
2012-12-09 19:53 ` Marc Joliet
2012-12-11 2:00 ` Walter Dnes
2012-12-13 13:45 ` Walter Dnes
2012-12-09 3:52 ` microcai
2012-12-09 8:03 ` Alan McKinnon
2012-12-09 21:44 ` Grant
2012-12-10 5:49 ` Alan McKinnon
2012-12-09 23:23 ` Grant
2012-12-10 3:06 ` [gentoo-user] " James
2012-12-10 5:35 ` [gentoo-user] " Alan McKinnon
2012-12-10 15:46 ` [gentoo-user] " James
2012-12-10 18:18 ` [gentoo-user] " Volker Armin Hemmann
2012-12-10 19:06 ` [gentoo-user] " Grant Edwards
2012-12-10 19:15 ` Michael Mol
2012-12-10 19:33 ` Grant Edwards
2012-12-10 19:38 ` Alan McKinnon
2012-12-10 20:06 ` Grant Edwards
2012-12-10 20:20 ` Volker Armin Hemmann
2012-12-10 20:37 ` Alan McKinnon
2012-12-10 21:10 ` Grant
2012-12-10 21:23 ` Alan McKinnon
2012-12-10 21:33 ` Grant
2012-12-10 21:42 ` Alan McKinnon
2012-12-12 17:05 ` James
2012-12-12 17:26 ` Bruce Hill
2012-12-12 17:55 ` James
2012-12-12 18:40 ` Bruce Hill [this message]
2012-12-13 5:02 ` Alan McKinnon
2012-12-13 6:06 ` Pandu Poluan
2012-12-13 14:10 ` Bruce Hill
2012-12-13 0:33 ` Walter Dnes
2012-12-13 1:00 ` Grant
2012-12-13 11:24 ` Kevin Chadwick
2012-12-13 13:37 ` Walter Dnes
2012-12-13 18:29 ` Volker Armin Hemmann
2012-12-14 17:13 ` Walter Dnes
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=20121212184050.GA8486@server \
--to=daddy@happypenguincomputers.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