From: Geert Uytterhoeven <geert@linux-m68k.org>
To: linux-fbdev-devel@lists.sourceforge.net
Cc: linux-kernel@vger.kernel.org,
Pekka Enberg <penberg@cs.helsinki.fi>,
Tero Roponen <teanropo@jyu.fi>, Andy Whitcroft <apw@shadowen.org>,
Andrew Morton <akpm@linux-foundation.org>,
Alexey Dobriyan <adobriyan@gmail.com>,
Alan Cox <alan@lxorguk.ukuu.org.uk>
Subject: Re: tty-related oops in latest kernel(s)?
Date: Thu, 31 May 2007 09:17:30 +0200 (CEST) [thread overview]
Message-ID: <Pine.LNX.4.64.0705310916240.17047@anakin> (raw)
In-Reply-To: <1180566886.4570.14.camel@daplas>
On Thu, 31 May 2007, Antonino A. Daplas wrote:
> On Wed, 2007-05-30 at 22:04 +0400, Alexey Dobriyan wrote:
> > 2) palette in neofb_par is "u32 palette[16];" which is 4x16 = 64 bytes.
> > struct fb_info::pseudo_palette is assigned to it in neo_alloc_fb_info().
> > Yet, we check at the beginning of neofb_setcolreg() for color map
> > length which neofb advertises as 256 which seems too many.
> >
>
> Yes, 256 is too many. the pseudo_palette is used for the 16-color
> console only.
>
> I'm impressed that this bug has escaped notice for this long. That bug
> is present since the 2.5.x era.
>
> Probably, the best thing to do is hide the pseudo_palette from the
> drivers and move it to the console layer where it belongs to spare
> future driver writers from palette usage confusion. That will be a
> thankless job.
The console layer doesn't know how to fill in the pseudo palette in all
cases, that's why the driver have to do it.
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
next prev parent reply other threads:[~2007-05-31 7:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.64.0705271200360.4955@jalava.cc.jyu.fi>
[not found] ` <84144f020705280022lf3902caj1def02ed56e0bff@mail.gmail.com>
[not found] ` <84144f020705280234g39aa04b3hfe369f4477e6043d@mail.gmail.com>
[not found] ` <Pine.LNX.4.64.0705291900001.32656@jalava.cc.jyu.fi>
[not found] ` <84144f020705291157k465ec6c4sb81081844bb57514@mail.gmail.com>
[not found] ` <Pine.LNX.4.64.0705300654493.5241@jalava.cc.jyu.fi>
[not found] ` <84144f020705292254o319f6619m787bf29491c92509@mail.gmail.com>
[not found] ` <Pine.LNX.4.64.0705301458400.4634@jalava.cc.jyu.fi>
[not found] ` <20070530083953.9909bcef.akpm@linux-foundation.org>
[not found] ` <Pine.LNX.4.64.0705301857370.29485@jalava.cc.jyu.fi>
2007-05-30 16:09 ` tty-related oops in latest kernel(s)? Andrew Morton
2007-05-30 18:04 ` Alexey Dobriyan
2007-05-30 23:14 ` Antonino A. Daplas
2007-05-30 23:18 ` David Miller
2007-05-30 23:28 ` Antonino A. Daplas
2007-05-31 7:17 ` Geert Uytterhoeven [this message]
2007-05-31 9:04 ` Antonino A. Daplas
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=Pine.LNX.4.64.0705310916240.17047@anakin \
--to=geert@linux-m68k.org \
--cc=adobriyan@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=apw@shadowen.org \
--cc=linux-fbdev-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=penberg@cs.helsinki.fi \
--cc=teanropo@jyu.fi \
/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