9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Steven Stallion <sstallion@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] Plan 9/ARM port wishlist: ODROID-U3 or XU3
Date: Wed, 19 Nov 2014 15:06:17 -0600	[thread overview]
Message-ID: <CAGGHmKECqvwhP58ah3TR6aUo9Y+5bEtxt2Nmqy36QLsJnWM0hA@mail.gmail.com> (raw)
In-Reply-To: <CA+db=n0+bFX-d_66Ds+PWA3_SQSEHCOk2d-Dz_DdQj5nXfCdJw@mail.gmail.com>

Interesting. Looks based on an Exynos. I've already started kernel
support for this (I even have a booting kernel, though it is very much
a work in progress). Work has been hectic this year, so I haven't had
a chance to get back to it since February. I've posted the code
online, though nothing is documented and most of it is largely still
in my head.

https://code.google.com/p/9chrome/source/browse/#hg%2Fsys%2Fsrc%2F9%2Fexynos

FWIW, there was a fair bit of work done in 5[al] that's also contained
in this source tree.

Steve

On Wed, Nov 19, 2014 at 1:35 PM, minux <minux.ma@gmail.com> wrote:
> On Wed, Nov 19, 2014 at 2:22 PM, Skip Tavakkolian
> <skip.tavakkolian@gmail.com> wrote:
>> they're well made, priced right, and fast (e.g. compiling Go on linux on rpi
>> is *very* slow when compared with older odroid-u2 with the same config).
> the problem is that samsung doesn't publish the datasheet for its processors
> without NDA, so the only reference is linux and uboot source code.
>



  reply	other threads:[~2014-11-19 21:06 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-19 19:22 Skip Tavakkolian
2014-11-19 19:35 ` minux
2014-11-19 21:06   ` Steven Stallion [this message]
2014-11-20 22:13 ` Joshua Boyd
2014-11-20 22:28   ` hiro
2014-11-20 23:06   ` Andrés Domínguez

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=CAGGHmKECqvwhP58ah3TR6aUo9Y+5bEtxt2Nmqy36QLsJnWM0hA@mail.gmail.com \
    --to=sstallion@gmail.com \
    --cc=9fans@9fans.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;
as well as URLs for NNTP newsgroup(s).