From mint-bounce@lists.fishpool.fi Mon May 31 08:21:30 2010 Message-ID: <9054FE70A0BD42D29D3958A81392C234@mercatus.local> From: "Jo Even Skarstein" To: "MiNT Mailing List" References: In-Reply-To: Subject: Re: [MiNT] Allocation of video RAM Date: Mon, 31 May 2010 14:19:21 +0200 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=original Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal Importance: Normal X-Mailer: Microsoft Windows Live Mail 14.0.8089.726 X-MimeOLE: Produced By Microsoft MimeOLE V14.0.8089.726 X-ecartis-version: Ecartis v1.0.0 Sender: mint-bounce@lists.fishpool.fi Errors-to: mint-bounce@lists.fishpool.fi X-original-sender: joska@online.no Precedence: bulk List-help: List-unsubscribe: List-Id: X-List-ID: List-subscribe: List-owner: List-post: -------------------------------------------------- From: "Peter Persson" Sent: Monday, May 31, 2010 1:30 PM To: "MiNT Mailing List" Subject: [MiNT] Allocation of video RAM > My question is about video RAM (VRAM). Right now there is no functionality > for this in the kernel, except Screalloc(). This means that the driver > has to implement that stuff internally, which has several drawbacks. For > example - if an application exits prematurely or doesn't do mfree() on > allocated VRAM, the memory won't be freed. Furthermore, there will be no > memory protection for this additional class of RAM if it isn't > implemented in the kernel. The correct place for this would IMO be the VDI, e.g. to use the offscreen bitmap facility. Or do you want the VRAM to be available for other uses than video? Jo Even