Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S261174AbVBZBTo (ORCPT ); Fri, 25 Feb 2005 20:19:44 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S262824AbVBZBTn (ORCPT ); Fri, 25 Feb 2005 20:19:43 -0500 Received: from gate.crashing.org ([63.228.1.57]:57753 "EHLO gate.crashing.org") by vger.kernel.org with ESMTP id S262806AbVBZBSr (ORCPT ); Fri, 25 Feb 2005 20:18:47 -0500 Subject: Re: [Linux-fbdev-devel] Re: 2.6.11-rc5 From: Benjamin Herrenschmidt To: Linux Fbdev development list Cc: Olaf Hering , Kernel Mailing List In-Reply-To: <421FCBF9.1020003@XLsigned.net> References: <20050224145049.GA21313@suse.de> <20050226004137.GA25539@suse.de> <421FCBF9.1020003@XLsigned.net> Content-Type: text/plain Date: Sat, 26 Feb 2005 12:17:46 +1100 Message-Id: <1109380667.14993.118.camel@gaston> Mime-Version: 1.0 X-Mailer: Evolution 2.0.3 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 937 Lines: 24 > This patch has already been posted to linux-fbdev on 2005-02-10 by David Vrabel > and made me ask > Is there any reason why this has been originally flagged "__init"? > "vesa_modes" is not "__init". That's why I changed "intelfb" to > use "vesa_modes". > > Maybe time has come to decide, if availability of "modedb" outside > of init functions is more important than freeing (unused) kernel memory. Well, I wonder why we need that mode db at all ... We should probably use VESA modes and calculate using the standard formula if the user requests a mode that isn't in the vesa table... Most monitors will provide additional detailed timings for non-vesa modes they may support. Ben. - 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/