9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "Devon H. O'Dell" <devon.odell@gmail.com>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu>
Subject: Re: [9fans] it's live
Date: Wed, 26 Jul 2006 15:52:01 -0400	[thread overview]
Message-ID: <9ab217670607261252n14288f79x88e61cc6e6886af3@mail.gmail.com> (raw)
In-Reply-To: <44C7C6C1.7010201@lanl.gov>

That is hot. I must have one.

-D

2006/7/26, Ronald G Minnich <rminnich@lanl.gov>:
>
> ok, so it's trivial, but if you look at mbgokhale.org/bustracker today,
> you'll see a track of my wife's Honda Fit ... the arrow on the bus
> really does mean 'I am going this direction, as indicated by GPS'.
> Josiah built 36 different bus icons to make that go. I'll try to get a
> link for node pictures and setup info.
>
> Thanks to Google for Gooooogle maps. Thanks to everyone for Plan 9 :-)
>
> more later. We just built the machine into the toolbox. I gave it the
> 'drop kick' test (drop it, kick it, kick it, drop it) and it survived.
> For this embedded stuff, you need to be pitiless. My wife was kind of
> shocked at how mean I was to the hardware before I put it in the car.
>
> I wrote a basically working driver for the DoC Millenium for Plan 9
> yesterday, using linuxbios and linux sources. It has debug prints in it,
> and it has a problem in one sense, in that a 'busy' bit in a status
> register NEVER clear, so every op has to time out (but succeeds). I
> think it's a standard docmil hardware problem (doc hardware is a mess,
> even if it is cool). I did install an mbr, file system, etc. and it all
> works on this part.
>
> If anyone wants the driver to have a go at finishing it up, you're
> welcome to it. I was going to put it on sources but I can't get to
> sources just now (down?).
>
> I stopped doing it because the (AHEM) fuctory bios is SUPPOSED to treat
> doc mil as an IDE drive if the right bios settings are made. It does
> nothing of the sort (SURPRISE! a fuctory bios doesn't work). So, I have
> to do linuxbios for this node ... but ... it will boot plan 9 really
> fast when I'm done. But, the only way to have ONLY a docmil part on the
> node is to have linuxbios, as the fuctory bios just won't work.
>
> The docmil driver is small. It made me a big fan of copy and convert.
> The Linux doc driver is pretty general, and hence complicated, as it
> weaves around the various doc part bugs and 'features'. A simple docmil
> driver is ... simple. And, it can be copied and converted for standard
> doc. A good deal. I like copy and convert.
>
> oh yeah ...
> doc == disk on chip -- 32 pin DIP flash, looks like programmed I/O disk,
> up to 64 MB
> docmil == disk on chip millenium -- 32DIP, 8 MB
>
> all doc are proprietary, all neat, all full of bugs.
>
> ron
>


  reply	other threads:[~2006-07-26 19:52 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-26 19:47 Ronald G Minnich
2006-07-26 19:52 ` Devon H. O'Dell [this message]
2006-07-26 20:30 ` Anthony Sorace
2006-07-26 21:30   ` Ronald G Minnich

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=9ab217670607261252n14288f79x88e61cc6e6886af3@mail.gmail.com \
    --to=devon.odell@gmail.com \
    --cc=9fans@cse.psu.edu \
    /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).