From: Noah Evans <noah.evans@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] gar nix!
Date: Fri, 16 Sep 2011 07:44:30 +0200 [thread overview]
Message-ID: <4EB85DAF-B9A6-4A2E-993B-72F4447BF14F@gmail.com> (raw)
In-Reply-To: <103b012cdb5c55bca54c751bb88fb57c@brasstown.quanstro.net>
Submit these changes as code reviews. See /PROCESS if anything is unclear about how to do that.
Sent from my iPad
On Sep 16, 2011, at 3:19 AM, erik quanstrom <quanstro@quanstro.net> wrote:
> well, after a bit of a time resembling /sys/src/cmd/aux/vga/adventure
> i currently have my atom box running nix. unfortunately, only one
> core is recognized. but i'll just have to leave one or two things till
> tomorrow.
>
> here are a list of a few things i tripped on
>
> 1. unfortunately, ppxeload isn't ready to load a .gz. i added a bit of
> code to at least not jump unconditionally to an x86 binary, but that's
> just not enough. need to revisit this.
>
> 2. ppxeload accepts only the old-and-wierd serial baud setting and
> not the kernel-standard, e.g. "0 b115200". i did fix this.
>
> 3. the 8169 driver wasn't working. i just dropped the one from 9load
> on top. inelegant, but effective.
>
> (i did have a 82563 chip going for a while that wasn't recognized. also
> needed to drop in a new driver for this, but since then the hardware has
> died.)
>
> 4. panic on memory init. this was caused because the only page color was
> 6, thus when starting in the array of page colors at 0, you won't find any.
> . i worked around this with this bit of code.
>
> ; diffy -c physalloc.c
> /n/dump/2011/0915/sys/src/nix/k10/physalloc.c:236,242 - physalloc.c:236,244
> uintmem m;
>
> DBG("physalloc\n");
> - assert(b->size > 0);
> + if(b->size == 0)
> + return 0;
> + // assert(b->size > 0);
>
> avail = b->avail;
> blocks = b->blocks;
>
> i need to go back and investigate if this is a problem with memory recognition
> or what.
>
> 5. needed to update 8169 and 82563 in the kernel.
>
> 6. had an old version of 6l that expected to make 4k pages. by the way,
> (won't we pay a heavy price for forking and/or execing small programs
> with 2mb pages? this means that each fork/exec is going to be at least
> 6mb worth of messing around.)
>
> it looks like my processors aren't recognized, and i'm pretty sure that the
> atom supports 1gb pages, but they aren't recognized either.
>
> - erik
>
next prev parent reply other threads:[~2011-09-16 5:44 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-16 1:19 erik quanstrom
2011-09-16 5:44 ` Noah Evans [this message]
2011-09-17 19:41 ` erik quanstrom
2011-09-17 20:03 ` Noah Evans
2011-09-16 5:56 ` ron minnich
[not found] ` <CAP6exYLuD6ZeOwCfY9TcgSWEYp-2QH-7qUO713GL0cravJ2FzA@mail.gmail.c>
2011-09-16 6:46 ` erik quanstrom
2011-09-16 7:02 ` Nemo
2011-09-16 7:52 ` dexen deVries
2011-09-16 13:36 ` Charles Forsyth
2011-09-16 14:39 ` ron minnich
[not found] ` <CAP6exYLy6sicg42A+7D=bmpWtv=p_an3c5=OQw9YB2oxPXhR2A@mail.gmail.c>
2011-09-16 14:57 ` erik quanstrom
2011-09-16 15:28 ` ron minnich
2011-09-16 15:31 ` Francisco J Ballesteros
[not found] ` <CA+N-5bbt92zqNpt0KW4prykyTxjYNHJJ7LuUCj4n3EACyC5GvQ@mail.gmail.c>
2011-09-16 15:33 ` erik quanstrom
2011-09-16 15:36 ` Francisco J Ballesteros
2011-09-16 15:44 ` ron minnich
2011-09-16 16:07 ` Francisco J Ballesteros
[not found] ` <CA+N-5bYJ1VBpqQENUy5fZirE_Joa9E6RE8rJbvaFwh065zd2TA@mail.gmail.c>
2011-09-16 15:37 ` erik quanstrom
2011-09-16 18:24 ` ron minnich
2011-09-16 22:23 ` Charles Forsyth
2011-09-16 22:27 ` erik quanstrom
2011-09-17 3:39 ` Bruce Ellis
2011-09-17 7:35 ` Charles Forsyth
2011-09-17 7:44 ` Charles Forsyth
2011-09-17 8:45 ` Charles Forsyth
[not found] ` <CAP6exYK+aoYcaC+LLo4XdPmZ1jvPQ0dAgZuUkmX7_xZQ+h3+gQ@mail.gmail.c>
2011-09-16 18:32 ` erik quanstrom
2011-09-16 18:44 ` Francisco J Ballesteros
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=4EB85DAF-B9A6-4A2E-993B-72F4447BF14F@gmail.com \
--to=noah.evans@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).