From: Brantley Coile <brantley@coraid.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] nvram for plan 9
Date: Sun, 9 Jan 2005 11:08:27 -0500 [thread overview]
Message-ID: <B2921D5A-6258-11D9-8E1A-000D933DFE16@coraid.com> (raw)
In-Reply-To: <87449adcce9e0795f2873ef528ae85f5@plan9.ucalgary.ca>
Two problems there. One, this thing is really tiny and getting a couple
of hundred K would push it's size for our needs. Second, the bios
can't read
it. It doesn't look like an ide--we just used the ide as an io port.
On Jan 9, 2005, at 11:06 AM, andrey mirtchovski wrote:
>
>> When we go into production on our device, would
>> anyone like some of the little goodies?
>
> mmm, goodies :)
>
> isn't there any way to make it slightly larger so it'll fit 9load as
> well as the nvram?
>
> 9load currently sits at 200K...
>
next prev parent reply other threads:[~2005-01-09 16:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-09 15:55 Brantley Coile
2005-01-09 16:06 ` andrey mirtchovski
2005-01-09 16:08 ` Brantley Coile [this message]
2005-01-09 16:08 ` Ronald G. Minnich
2005-01-09 16:20 ` Brantley Coile
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=B2921D5A-6258-11D9-8E1A-000D933DFE16@coraid.com \
--to=brantley@coraid.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).