From owner-freebsd-hackers Thu Feb 4 04:19:33 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA06097 for freebsd-hackers-outgoing; Thu, 4 Feb 1999 04:19:33 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from fleming.cs.strath.ac.uk (fleming.cs.strath.ac.uk [130.159.196.126]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA06088 for ; Thu, 4 Feb 1999 04:19:28 -0800 (PST) (envelope-from roger@cs.strath.ac.uk) Received: from muir-10 (roger@muir-10.cs.strath.ac.uk [130.159.148.10]) by fleming.cs.strath.ac.uk (8.8.8/8.8.8) with SMTP id MAA03011 Thu, 4 Feb 1999 12:19:20 GMT Message-ID: <36B99047.59E2@cs.strath.ac.uk> Date: Thu, 04 Feb 1999 12:19:20 +0000 From: Roger Hardiman Organization: University of Strathclyde X-Mailer: Mozilla 3.04Gold (X11; I; OSF1 V4.0 alpha) MIME-Version: 1.0 To: hackers@FreeBSD.ORG Subject: contiguous memory allocation Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, With the recent VM code changes, is there a way to get a contiguous block of memory allocated after boot time? The bt848 driver is simplified if the frame buffer images are grabbed into is a contiguous block of memory. This is why the memory (768x576*3 bytes or 1.2 MegaBytes) is allocated at boot time. Porting of the bt848 driver to an LKM was abandoned, because there was no contiguous memory alloction once user programs were running and memory was fragmented. (Randall worked on this) Has this changed recently, or are we still in the same position? Thanks Roger p.s., I know the bt848 can write pixels to arbritary pages, but contiguous allocation is much simpler than having the driver know the details of many scattered memory pages. -- Roger Hardiman | Telepresence Research Group roger@cs.strath.ac.uk | DMEM, University of Strathclyde tel: 0141 548 2897 | Glasgow, Scotland, G1 1XJ, UK fax: 0141 552 0557 | http://telepresence.dmem.strath.ac.uk To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message