9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: Re: [9fans] Raspberry Pi image
Date: Wed, 19 Feb 2014 20:24:03 -0500	[thread overview]
Message-ID: <48c0ee216ebb8a09d4a47532492753df@brasstown.quanstro.net> (raw)
In-Reply-To: <CANZw+5f4HiLZxjNC3o=E46JmShj+SyqKk8pV4HAb8AJkJO4n3g@mail.gmail.com>

On Wed Feb 19 05:16:16 EST 2014, edgecomberts@gmail.com wrote:

> So the "trade secret" thing explains why you don't see a port of Plan 9 for
> every new and exciting device and board that comes out. It is a shame, but
> these companies producing things like the GPUs in ARM devices insist on
> proprietary licences.

unfortunately, a port is still a big time commitment even with all the docs.
they get big, and you have to load a large amount of esoteric state into your
brain.  and debugging the early stages takes esoteric skills.  a frequent problem
is trying to debug the inital boot, since most of the easy debugging tools like
print are often not available.

> As far as I can tell, the i.MX6 chip from Freescale is about as open as you
> can get, I'm just trying to remember where someone said it had an over
> 1,000 page manual for the chip, and I'm hoping its not this very list,
> otherwise I will look like a fool! The i.MX6, for that "openness" reason
> has been a chip I've been meaning to get, and never gotten around to. The
> UDOO board has the chip, and integrates an Arduino Due along for the ride.
> Its reasonably cheap too, although availability is not something I've
> looked at in a little while, and being one of those Kickstarter things, I
> don't think availability is a priority past shipping them to backers.

i think you're right, but i've run across devices which shall remain nameless
which claim open source documentation, but when you check there docs
against the linux driver you see they have nothing in common.

cavet emptor.

- erik



  reply	other threads:[~2014-02-20  1:24 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-18 10:23 Ramakrishnan Muthukrishnan
2014-02-18 10:29 ` Richard Miller
2014-02-18 11:56   ` Ramakrishnan Muthukrishnan
2014-02-18 20:18   ` Grant R. Mather
2014-02-18 21:05     ` Richard Miller
2014-02-18 22:25       ` Yoann Padioleau
2014-02-19  0:13         ` Shane Morris
2014-02-19  0:19           ` Jacob Todd
2014-02-19 10:00           ` Richard Miller
2014-02-19 10:14             ` Shane Morris
2014-02-20  1:24               ` erik quanstrom [this message]
2014-02-20 15:47               ` Steven Stallion
2014-02-20 15:55                 ` erik quanstrom
2014-02-20 15:57                 ` David du Colombier
2014-02-20 15:57                 ` Charles Forsyth
2014-02-19 10:55             ` Ramakrishnan Muthukrishnan
2014-02-19  9:05         ` Richard Miller

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=48c0ee216ebb8a09d4a47532492753df@brasstown.quanstro.net \
    --to=quanstro@quanstro.net \
    --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).