From mboxrd@z Thu Jan 1 00:00:00 1970 From: Miles Lane Subject: Re: Re: 2.6.12-rc1-mm2 -- nvidiafb driver gives black screen Date: Mon, 28 Mar 2005 17:12:04 -0800 Message-ID: References: <20050324203118.345c6004.akpm@osdl.org> <42483B11.6010203@osdl.org> <4248A92E.8080409@osdl.org> Reply-To: linux-fbdev-devel@lists.sourceforge.net Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Return-path: Received: from sc8-sf-mx1-b.sourceforge.net ([10.3.1.11] helo=sc8-sf-mx1.sourceforge.net) by sc8-sf-list1.sourceforge.net with esmtp (Exim 4.30) id 1DG5HA-0000mO-3C for linux-fbdev-devel@lists.sourceforge.net; Mon, 28 Mar 2005 17:12:12 -0800 Received: from wproxy.gmail.com ([64.233.184.200]) by sc8-sf-mx1.sourceforge.net with esmtp (Exim 4.41) id 1DG5H8-0004xz-Fl for linux-fbdev-devel@lists.sourceforge.net; Mon, 28 Mar 2005 17:12:12 -0800 Received: by wproxy.gmail.com with SMTP id 71so707113wra for ; Mon, 28 Mar 2005 17:12:04 -0800 (PST) In-Reply-To: <4248A92E.8080409@osdl.org> Sender: linux-fbdev-devel-admin@lists.sourceforge.net Errors-To: linux-fbdev-devel-admin@lists.sourceforge.net List-Unsubscribe: , List-Id: List-Post: List-Help: List-Subscribe: , List-Archive: Content-Type: text/plain; charset="us-ascii" To: "Randy.Dunlap" Cc: linux-fbdev-devel@lists.sourceforge.net, Andrew Morton , khali@linux-fr.org On Mon, 28 Mar 2005 17:02:38 -0800, Randy.Dunlap wrote: > Miles Lane wrote: > > On Mon, 28 Mar 2005 09:12:49 -0800, Randy.Dunlap wrote: > > > > By the why, I don't know why Andrew got dropped from my previous message list. > > Also, I thought you were asking these questions of the fbdev and > > vidiafb developers. > > > > > >>I guess that there is some chance that the io_remap_pfn* patches > >>are involved with this. > > > > > > I am a tester, so I don't have knowledge about this. > > Sure, it wasn't a question. :) > > > > >>Is there some way to determine exactly which > >>io remap kernel calls are involved in "nvidiafb: cannot ioremap FB > >>base" ? > > > > > > I don't know. Someone who does, please tell me. If someone > > will tell me how, I'll be happy to gather the information. > > > > > >>Is that in the exposed source code? > > > > > > I have no idea. How would I find out? > > > >>If so, where is that source code? > > > > > > I have no clue. > > Where did you get the nvidia wrapper? > Where can I find it? Perhaps you are thinking I am using the NVidia binary driver? This is not the case. nvidiafb is a recently added framebuffer driver (IIRC, first showing up in 2.6.12-rc1-mm2). I believe khali@linux-fr.org is the author. I have reproduced this problem with both mm2 and mm3. Do you need my .config file? > Where did you get the nvidia binary blob? If you had my .config file, couldn't you build the driver into the kernel, as I have? I don't know what a driver blob is. I haven't built the driver as a module. > Where can I get it? Build it? > >>If not, can we determine from the binary which calls > >>are being made? > > > > > > Uhhh. I have delivered the Oops info and a bunch of other > > information. I have given you whatever I thought might be helpful. I > > need guidance here. > > Sure, but the part that I really need to see is likely partially > hidden in some binary blob. We'll see. Blob? Well, I have some i2c built as modules. > > Your humble tester (remember me from the early USB days?), > > Sure I do. :) > I'll make a patch, probably tonight Pacific time. Great! Miles ------------------------------------------------------- This SF.net email is sponsored by Demarc: A global provider of Threat Management Solutions. Download our HomeAdmin security software for free today! http://www.demarc.com/info/Sentarus/hamr30