mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Geert Uytterhoeven <geert@linux-m68k.org>
To: linux-fbdev-devel@lists.sourceforge.net
Cc: Alexey Dobriyan <adobriyan@gmail.com>,
	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>,
	Alan Cox <alan@lxorguk.ukuu.org.uk>
Subject: Re: [Linux-fbdev-devel] 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

  parent reply	other threads:[~2007-05-31  7:17 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-27  9:06 Tero Roponen
2007-05-28  7:22 ` Pekka Enberg
2007-05-28  7:47   ` Pekka Enberg
2007-05-28  8:08   ` Tero Roponen
2007-05-28  9:34   ` Pekka Enberg
2007-05-29 16:04     ` Tero Roponen
2007-05-29 18:57       ` Pekka Enberg
2007-05-30  3:43         ` Tero Roponen
2007-05-30  3:57         ` Tero Roponen
2007-05-30  5:54           ` Pekka Enberg
2007-05-30  5:59             ` Pekka Enberg
2007-05-30  6:00             ` Tero Roponen
2007-05-30 12:02             ` Tero Roponen
2007-05-30 15:39               ` Andrew Morton
2007-05-30 16:01                 ` Tero Roponen
2007-05-30 16:09                   ` 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                           ` [Linux-fbdev-devel] " Antonino A. Daplas
2007-05-30 18:13                   ` Pekka Enberg
2007-05-30 18:27                     ` Tero Roponen
2007-05-30 22:14                   ` Antonino A. Daplas
2007-05-30 23:17                   ` 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

all inboxes | Powered by JetHome®