From mint-bounce@lists.fishpool.fi Mon May 31 15:54:34 2010 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:subject:mime-version :content-type:from:in-reply-to:date:cc:content-transfer-encoding :message-id:references:to:x-mailer; bh=tu71K9v751LbUNl2/BuN1JB2LXoMHmbDeEM/NxSTjQI=; b=lxxeEfc086//fhx3JU4joj0YrVbyRb4FBNEq3b+Rs7K/at3jT9sP4cBN11GiY0WuJS zdevrMlOU+pqiLgsfd400Hc4rgtVU2gVOMSqCOXAYtL3cLQmbjo8FTThPPasOC14OHxM rcg57egbwDvBvSm20oyOTlmQHEy6ZpY/uJPRs= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=subject:mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer; b=ON/GoRixPOTHGUboCkpxbXeZikJUFBUxMRHJEXs2sBB/AxkULBbfyep7EsLibJUj5U OkuoqZqlIb3JdylkXPg3pIInRu7g9Zb/rcR4dUx6uG+EN9y5SYmwHoLRKQ6Ko/KavxBQ kbA5VG8A/QjCszBxjWEhHCHzMmfFhdXgNYux4= Subject: Re: [MiNT] Allocation of video RAM Mime-Version: 1.0 (Apple Message framework v1078) Content-Type: text/plain; charset=us-ascii From: Peter Persson In-Reply-To: <1275335133.11662.41.camel@jetpack.demon.co.uk> Date: Mon, 31 May 2010 21:52:06 +0200 Cc: MiNT Mailing List Message-Id: References: <1275335133.11662.41.camel@jetpack.demon.co.uk> To: Alan Hourihane X-Mailer: Apple Mail (2.1078) X-ecartis-version: Ecartis v1.0.0 Sender: mint-bounce@lists.fishpool.fi Errors-to: mint-bounce@lists.fishpool.fi X-original-sender: pep.fishmoose@gmail.com Precedence: bulk List-help: List-unsubscribe: List-Id: X-List-ID: List-subscribe: List-owner: List-post: Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by mail.sparemint.org id o4VJsXxo021655 31 maj 2010 kl. 21.45 skrev Alan Hourihane: > Video memory should be treated differently and a completely separate > video kernel memory manager should be used. Which means... what? :) To me, that sounds like I'll have to resort to some custom solution - i.e. I'll just go for the CT60_vmalloc() or whatever it's called... -- PeP