Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S262467AbVA0AQu (ORCPT ); Wed, 26 Jan 2005 19:16:50 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S262465AbVA0AQC (ORCPT ); Wed, 26 Jan 2005 19:16:02 -0500 Received: from lakermmtao03.cox.net ([68.230.240.36]:14214 "EHLO lakermmtao03.cox.net") by vger.kernel.org with ESMTP id S262472AbVAZWMS (ORCPT ); Wed, 26 Jan 2005 17:12:18 -0500 In-Reply-To: References: Mime-Version: 1.0 (Apple Message framework v619) Content-Type: text/plain; charset=US-ASCII; format=flowed Message-Id: <56B00E32-6FE7-11D9-A93E-000393ACC76E@mac.com> Content-Transfer-Encoding: 7bit Cc: linux-kernel@vger.kernel.org, Bryn Reeves , James Antill , Rik van Riel , Andrew Morton From: Kyle Moffett Subject: Re: don't let mmap allocate down to zero Date: Wed, 26 Jan 2005 17:12:16 -0500 To: linux-os@analogic.com X-Mailer: Apple Mail (2.619) Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 886 Lines: 26 On Jan 26, 2005, at 11:38, linux-os wrote: > Does this mean that we can't mmap the screen regen buffer at > 0x000b8000 anymore? I believe the point of this is to ensure that *non*-MAP_FIXED mmap calls won't use 0, IOW, it keeps things from accidentally being mapped at 0 when the user didn't intend to, like shared libs and such. Cheers, Kyle Moffett -----BEGIN GEEK CODE BLOCK----- Version: 3.12 GCM/CS/IT/U d- s++: a18 C++++>$ UB/L/X/*++++(+)>$ P+++(++++)>$ L++++(+++) E W++(+) N+++(++) o? K? w--- O? M++ V? PS+() PE+(-) Y+ PGP+++ t+(+++) 5 X R? tv-(--) b++++(++) DI+ D+ G e->++++$ h!*()>++$ r !y?(-) ------END GEEK CODE BLOCK------ - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/