From: "Randy.Dunlap" <rddunlap@osdl.org>
To: linux-fbdev-devel@lists.sourceforge.net
Cc: Andrew Morton <akpm@osdl.org>, khali@linux-fr.org, adaplas@pol.net
Subject: [PATCH] nvidiafb: fix section references
Date: Tue, 29 Mar 2005 08:25:20 -0800 [thread overview]
Message-ID: <42498170.2050902@osdl.org> (raw)
In-Reply-To: <4248DAE3.9060604@osdl.org>
[-- Attachment #1: Type: text/plain, Size: 2264 bytes --]
Randy.Dunlap wrote:
> Miles Lane wrote:
>
>> On Thu, 24 Mar 2005 20:31:18 -0800, Andrew Morton <akpm@osdl.org> wrote:
>>
>>> (Added the mailing list - trust that's ok)
>>>
>>> Miles Lane <miles.lane@gmail.com> wrote:
>>>
>>>> Kernel command line: BOOT_IMAGE=Linux ro root=306 video=nvidiafb
>>>> init=/etc/init lang=us apm=power-off nomce
>>>> nvidiafb: nVidia device/chipset 10DE0312
>>>> nvidiafb: nVidia Corporation NV31 [GeForce FX 5600]
>>>> nvidiafb: CRTC0 found
>>>> nvidiafb: CRTC1 not found
>>>> nvidiafb: EDID found from BUS1
>>>> nvidiafb: CRTC 0 appears to have a CRT attached
>>>> nvidiafb: Using CRT on CRTC 0
>>>>
>>>>
>>>>>> I am wondering whether the following two lines point to the problem.
>>>>
>>>>
>>>> allocation failed: out of vmalloc space - use vmalloc=<size> to
>>>> increase size.
>>>> nvidiafb: cannot ioremap FB base
>>>
>>>
>>> Quite possibly.
>
>
> Sure, without the FB memory, video won't show up.
> And the 2 lines are directly related -- same error printed from
> 2 different places.
>
>>> I'll do rc2-mm3 tonight - please test that. It has fixes.
>>
>>
>>
>> Hello Andrew,
>>
>> mm3 did not fix the problem. I still get a blank framebuffer console.
>> I still get these two errors:
>> allocation failed: out of vmalloc space - use vmalloc=<size> to
>> increase size.
>> nvidiafb: cannot ioremap FB base
>> Also, I still get the /sys listing Oops when listing the i2c entries
>> for the nvidiafb.
>> Lastly, I get the Oops that halts booting if I include certain other
>> i2c drivers in the build.
>> Removing nvidiafb from the build allows me to get a completely usable
>> build of 2.6.12-rc1-mm3.
>>
>> I haven't heard anything from the author of the nvidiafb driver about
>> the various issues I have reported.
>
>
> Here's a tiny patch to get started. Hopefully it will show us
> why ioremap is failing...
>
> Another issue while looking at this code:
> there is some __initdata in nvidia.c that should be __devinitdata
> (deja vu)
>
> Miles, after using this patch, please also test by booting
> with "vmalloc=512M" (or "vmalloc=256M" if you don't have 512 MB
> to spare).
and here are the section usage fixes.
Miles, please apply and test with this also.
Andrew, I think you and Tony want this.
--
~Randy
[-- Attachment #2: nvid_sections.patch --]
[-- Type: text/x-patch, Size: 2026 bytes --]
linux-2612-rc1-mm3
Fix section usage in nvidiafb driver.
Signed-off-by: Randy Dunlap <rddunlap@osdl.org>
diffstat:=
drivers/video/nvidia/nvidia.c | 22 +++++++++++-----------
1 files changed, 11 insertions(+), 11 deletions(-)
diff -Naurp ./drivers/video/nvidia/nvidia.c~nvid_sections ./drivers/video/nvidia/nvidia.c
--- ./drivers/video/nvidia/nvidia.c~nvid_sections 2005-03-28 08:40:09.000000000 -0800
+++ ./drivers/video/nvidia/nvidia.c 2005-03-29 08:20:20.000000000 -0800
@@ -402,25 +402,25 @@ static struct pci_device_id nvidiafb_pci
MODULE_DEVICE_TABLE(pci, nvidiafb_pci_tbl);
/* command line data, set in nvidiafb_setup() */
-static int flatpanel __initdata = -1; /* Autodetect later */
-static int forceCRTC __initdata = -1;
-static int hwcur __initdata = 0;
-static int noaccel __initdata = 0;
-static int noscale __initdata = 0;
-static int paneltweak __initdata = 0;
+static int flatpanel __devinitdata = -1; /* Autodetect later */
+static int forceCRTC __devinitdata = -1;
+static int hwcur __devinitdata = 0;
+static int noaccel __devinitdata = 0;
+static int noscale __devinitdata = 0;
+static int paneltweak __devinitdata = 0;
#ifdef CONFIG_MTRR
-static int nomtrr __initdata = 0;
+static int nomtrr __devinitdata = 0;
#endif
-static char *mode_option __initdata = NULL;
+static char *mode_option __devinitdata = NULL;
-static struct fb_fix_screeninfo __initdata nvidiafb_fix = {
+static struct fb_fix_screeninfo __devinitdata nvidiafb_fix = {
.type = FB_TYPE_PACKED_PIXELS,
.xpanstep = 8,
.ypanstep = 1,
};
-static struct fb_var_screeninfo __initdata nvidiafb_default_var = {
+static struct fb_var_screeninfo __devinitdata nvidiafb_default_var = {
.xres = 640,
.yres = 480,
.xres_virtual = 640,
@@ -1617,7 +1617,7 @@ static void __exit nvidiafb_remove(struc
* ------------------------------------------------------------------------- */
#ifndef MODULE
-static int __init nvidiafb_setup(char *options)
+static int __devinit nvidiafb_setup(char *options)
{
char *this_opt;
next prev parent reply other threads:[~2005-03-29 16:25 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <a44ae5cd0503242023233dc23f@mail.gmail.com>
2005-03-25 4:31 ` 2.6.12-rc1-mm2 -- nvidiafb driver gives black screen Andrew Morton
2005-03-26 4:50 ` Miles Lane
2005-03-28 17:12 ` Randy.Dunlap
2005-03-29 0:22 ` Miles Lane
2005-03-29 0:37 ` Randy.Dunlap
2005-03-29 0:56 ` Miles Lane
2005-03-29 1:02 ` Randy.Dunlap
2005-03-29 1:12 ` Miles Lane
2005-03-29 3:01 ` Randy.Dunlap
2005-03-29 9:16 ` Jean Delvare
2005-03-29 1:13 ` Andrew Morton
2005-03-29 3:56 ` Miles Lane
2005-03-29 4:34 ` Randy.Dunlap
2005-03-29 16:25 ` Randy.Dunlap [this message]
2005-04-14 5:51 ` Antonino A. Daplas
2005-04-14 17:06 ` Jean Delvare
2005-04-15 3:07 ` Antonino A. Daplas
2005-04-14 5:51 ` Antonino A. Daplas
2005-04-14 17:13 ` Jean Delvare
2005-04-14 18:19 ` Miles Lane
2005-04-15 3:07 ` Antonino A. Daplas
2005-04-15 3:07 ` Antonino A. Daplas
2005-04-16 8:21 ` Miles Lane
2005-04-21 5:51 ` Miles Lane
2005-04-21 16:22 ` Randy.Dunlap
2005-04-21 18:36 ` Randy.Dunlap
2005-04-23 0:03 ` Miles Lane
2005-04-23 0:12 ` Miles Lane
2005-04-24 17:09 ` Miles Lane
2005-04-25 3:21 ` Antonino A. Daplas
2005-04-25 20:31 ` Miles Lane
2005-04-25 20:33 ` Miles Lane
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=42498170.2050902@osdl.org \
--to=rddunlap@osdl.org \
--cc=adaplas@pol.net \
--cc=akpm@osdl.org \
--cc=khali@linux-fr.org \
--cc=linux-fbdev-devel@lists.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).