From: Wichert Akkerman <wichert@wiggy.net>
To: linux-kernel@vger.kernel.org
Cc: bert hubert <ahu@ds9a.nl>, James Simmons <jsimmons@infradead.org>
Subject: Re: [FIX] Re: 2.5.66 new fbcon oops while loading X
Date: Wed, 26 Mar 2003 15:54:12 +0100 [thread overview]
Message-ID: <20030326145412.GI2078@wiggy.net> (raw)
In-Reply-To: <20030326105840.GA10201@outpost.ds9a.nl>
Previously bert hubert wrote:
> On Debian, ls /dev/fb[67] results in:
> crw--w--w- 1 root tty 29, 192 Nov 30 2000 /dev/fb6
> crw--w--w- 1 root tty 29, 224 Nov 30 2000 /dev/fb7
Documentation/devices.txt (at least in 2.5.64) states that those
devices should be fully supported:
For backwards compatibility {2.6} the following
progression is also handled by current kernels:
0 = /dev/fb0
32 = /dev/fb1
...
224 = /dev/fb7
So perhaps the patch should look something like:
if (fbidx >= FB_MAX) {
/* Support older device minor numbering */
if (fbidx%32!=0)
return -ENODEV;
else
fbidx/=32;
/* Check if it is still too large */
if (fbidx >= FB_MAX)
return -ENODEV;
}
Wichert.
--
Wichert Akkerman <wichert@wiggy.net> http://www.wiggy.net/
A random hacker
next prev parent reply other threads:[~2003-03-26 14:43 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-25 12:31 2.5.66 new fbcon oops while loading X / possible gcc bug? bert hubert
2003-03-25 17:23 ` James Simmons
2003-03-25 22:15 ` bert hubert
2003-03-26 10:58 ` [FIX] Re: 2.5.66 new fbcon oops while loading X bert hubert
2003-03-26 14:54 ` Wichert Akkerman [this message]
2003-03-26 20:10 ` James Simmons
2003-03-26 22:42 ` Wichert Akkerman
2003-03-27 0:23 ` James Simmons
2003-03-27 9:56 ` Wichert Akkerman
2003-03-26 20:05 ` James Simmons
2003-03-27 9:11 ` [Linux-fbdev-devel] " Geert Uytterhoeven
-- strict thread matches above, loose matches on Subject: below --
2003-03-27 10:49 Petr Vandrovec
[not found] ` <BKEGKPICNAKILKJKMHCAIEFBCGAA.Riley@Williams.Name>
2003-04-12 9:39 ` Wichert Akkerman
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=20030326145412.GI2078@wiggy.net \
--to=wichert@wiggy.net \
--cc=ahu@ds9a.nl \
--cc=jsimmons@infradead.org \
--cc=linux-kernel@vger.kernel.org \
/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