From: erik quanstrom <quanstro@labs.coraid.com>
To: 9fans@9fans.net
Subject: Re: [9fans] Plan9 on QNAP TS-212 NAS (kw)
Date: Tue, 12 Jul 2011 11:32:03 -0400 [thread overview]
Message-ID: <0e856dc1ce35b2b51ee55663f381c45d@coraid.com> (raw)
In-Reply-To: <20110712115537.6574d0f3@lahti.ethans.dre.am>
On Tue Jul 12 06:57:22 EDT 2011, eekee57@fastmail.fm wrote:
> On Sat, 9 Jul 2011 18:40:49 -0400 erik quanstrom
> <quanstro@quanstro.net> wrote:
>
> > there are assumptions about the memory size in many devices,
> >
> Ouch. Couldn't the kernel probe the memory size at boot time and use
> that? Or at least have it set in a constant for a single point of
> change?
sadly no. often, probling is not possible. and assumptions about
memory sizes and layouts are typically not possible.
while you can view this as an advantage, i think this tilts toward
disavantage in little systems that have a ddr2/3 slot. you can't
probe it, and you can't boot unless you have exactly the correct
memory module.
- erik
next prev parent reply other threads:[~2011-07-12 15:32 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CACXGR2Q0bf3dkWGrVT=rkqYrNERe5xdzPuh836CJsbo84A6jVA@mail.gmail.c>
2011-07-09 15:55 ` erik quanstrom
2011-07-09 20:59 ` Jared Jennings
2011-07-09 22:33 ` Jared Jennings
2011-07-10 0:32 ` Jared Jennings
[not found] ` <CACXGR2QsfEkHkfUVu8df+4KeosOLOSVMuAE99ohb-tzY+x9kUQ@mail.gmail.c>
2011-07-10 0:49 ` erik quanstrom
[not found] ` <CACXGR2SCEkWaqEPRZqe7tLgDni6BiEc09MVC-v8puJtUPO7iVQ@mail.gmail.c>
2011-07-09 22:40 ` erik quanstrom
2011-07-12 10:55 ` Ethan Grammatikidis
2011-07-12 15:32 ` erik quanstrom [this message]
2011-07-12 15:41 ` Ethan Grammatikidis
2011-07-12 15:49 ` ron minnich
[not found] ` <CAP6exYJ+4HE4K=axuNcjgiocJKnGy8Kk4V+xjRtf_MO2djzytw@mail.gmail.c>
2011-07-12 16:09 ` erik quanstrom
[not found] ` <CACXGR2QQx=8dxFbJ0Y6eiS5dTgRA2AjpNvzQZOaVOEgt-MFnsw@mail.gmail.c>
2011-07-09 22:31 ` erik quanstrom
2011-07-09 4:38 Jared Jennings
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=0e856dc1ce35b2b51ee55663f381c45d@coraid.com \
--to=quanstro@labs.coraid.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).