From mboxrd@z Thu Jan 1 00:00:00 1970 Date: Tue, 12 Jul 2011 16:41:41 +0100 From: Ethan Grammatikidis To: 9fans@9fans.net Message-ID: <20110712164141.4461bbe1@lahti.ethans.dre.am> In-Reply-To: <0e856dc1ce35b2b51ee55663f381c45d@coraid.com> References: <08e97c0e92bc3a82cc2e6746b657a113@ladd.quanstro.net> <20110712115537.6574d0f3@lahti.ethans.dre.am> <0e856dc1ce35b2b51ee55663f381c45d@coraid.com> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: Re: [9fans] Plan9 on QNAP TS-212 NAS (kw) Topicbox-Message-UUID: ffd2c0d8-ead6-11e9-9d60-3106f5b1d025 On Tue, 12 Jul 2011 11:32:03 -0400 erik quanstrom wrote: > On Tue Jul 12 06:57:22 EDT 2011, eekee57@fastmail.fm wrote: > > On Sat, 9 Jul 2011 18:40:49 -0400 erik quanstrom > > 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. Ouch. :( At least with the 640K split you knew where the split was.