From: Petr Vandrovec <vandrove@vc.cvut.cz>
To: alan@lxorguk.ukuu.org.uk
Cc: linux-kernel@vger.kernel.org, mc@cs.Stanford.EDU,
engler@csl.stanford.edu
Subject: [PATCH] Re: [CHECKER] 2.4.5-ac4 non-init functions calling init functions
Date: Thu, 31 May 2001 01:08:55 +0200 [thread overview]
Message-ID: <20010531010855.A1765@vana.vc.cvut.cz> (raw)
In-Reply-To: <200105302008.NAA07710@csl.Stanford.EDU>
In-Reply-To: <200105302008.NAA07710@csl.Stanford.EDU>
On Wed, May 30, 2001 at 01:08:40PM -0700, Dawson Engler wrote:
> /u2/engler/mc/oses/linux/2.4.5-ac4/drivers/video/matrox/matroxfb_base.c
> :1785:initMatrox2: ERROR:INIT: non-init fn 'initMatrox2' calling init
> fn 'fb_find_mode'
Thanks for pointing this out. Code checks for init/noninit phase, but I somehow
forgot to set hotplug variable:
#ifndef MODULE
/* mode database is marked __init!!! */
if (!hotplug) {
fb_find_mode(&vesafb_defined, &ACCESS_FBINFO(fbcon), videomode[0]?videomode:NULL,
NULL, 0, &defaultmode, vesafb_defined.bits_per_pixel);
}
#endif /* !MODULE */
Alan, please apply following patch, it fixes this. It is for 2.4.5-ac5,
but should apply to any 2.4.x.
Thanks,
Petr Vandrovec
vandrove@vc.cvut.cz
diff -urdN linux/drivers/video/matrox/matroxfb_base.c linux/drivers/video/matrox/matroxfb_base.c
--- linux/drivers/video/matrox/matroxfb_base.c Wed May 30 20:27:28 2001
+++ linux/drivers/video/matrox/matroxfb_base.c Wed May 30 20:31:42 2001
@@ -2495,6 +2495,7 @@
initialized = 1;
matrox_init();
}
+ hotplug = 1;
/* never return failure, user can hotplug matrox later... */
return 0;
}
next prev parent reply other threads:[~2001-05-30 23:10 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-30 20:08 Dawson Engler
2001-05-30 21:33 ` David Woodhouse
2001-05-30 22:00 ` Oliver Xymoron
2001-05-30 23:01 ` Dawson Engler
2001-05-31 7:09 ` David Woodhouse
2001-05-30 21:40 ` Harald Welte
2001-05-30 23:08 ` Petr Vandrovec [this message]
2001-05-31 21:38 ` Kai Germaschewski
2001-05-31 22:06 ` Dawson Engler
2001-06-01 7:48 ` Geert Uytterhoeven
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=20010531010855.A1765@vana.vc.cvut.cz \
--to=vandrove@vc.cvut.cz \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=engler@csl.stanford.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=mc@cs.Stanford.EDU \
/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
all inboxes | Powered by JetHome®