From: Geert Uytterhoeven <geert@linux-m68k.org>
To: James Simmons <jsimmons@suse.com>
Cc: Samuel Rydh <samuel@ibrium.se>,
Linux Frame Buffer Device Development
<linux-fbdev@vuser.vu.union.edu>,
Linux/PPC Development <linuxppc-dev@lists.linuxppc.org>,
olh@suse.de
Subject: Re: [linux-fbdev] Re: Video driver bug
Date: Tue, 10 Oct 2000 21:53:48 +0200 (CEST) [thread overview]
Message-ID: <Pine.LNX.4.10.10010102150540.375-100000@cassiopeia.home> (raw)
In-Reply-To: <Pine.LNX.4.21.0010101702000.2113-100000@euclid.oak.suse.com>
On Tue, 10 Oct 2000, James Simmons wrote:
> > > I have some ideas but it would requires some changes to the fbcon layer.
> > > Also it would move palette handling from fbdev to the console layer.
> > > Would these changes be included with the 2.4.0-testX kernels?
> >
> > I think we must do something in 2.4.0-testX, since you can abuse the bug to
> > panic the box.
>
> We really should design a cursor api. A api independent of the console so
> X servers can take advantage of it. IMHO fbcon-cfbX and freinds should
> go away. What I purpose is it be replaced by 3 standard functions:
>
> fillrect
> copyarea
> drawimage
>
> This with a clean cursor api woudl allow display_switch to go away.
100% agreed. But that should wait for 2.5.0. Now we have to hunt for
release-critical bugs in the current version.
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
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2000-10-10 19:53 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-10-07 11:38 Video driver bug Samuel Rydh
2000-10-07 17:56 ` Geert Uytterhoeven
2000-10-07 18:50 ` Takashi Oe
2000-10-07 23:34 ` Samuel Rydh
2000-10-10 1:43 ` [linux-fbdev] " James Simmons
2000-10-10 8:04 ` Geert Uytterhoeven
2000-10-10 13:45 ` Geert Uytterhoeven
2000-10-11 3:18 ` James Simmons
2000-10-13 20:43 ` Benjamin Herrenschmidt
2000-10-13 22:42 ` Takashi Oe
2000-10-14 16:41 ` Geert Uytterhoeven
2000-10-17 0:22 ` James Simmons
2000-10-16 22:20 ` Samuel Rydh
2000-10-17 11:37 ` Geert Uytterhoeven
2000-10-18 4:09 ` James Simmons
2000-10-21 13:22 ` Samuel Rydh
2000-10-14 6:36 ` James Simmons
2000-10-14 10:09 ` Geert Uytterhoeven
2000-10-14 12:24 ` Samuel Rydh
2000-10-11 0:05 ` James Simmons
2000-10-10 19:53 ` Geert Uytterhoeven [this message]
2000-10-11 5:23 ` James Simmons
2000-10-14 16:21 ` Geert Uytterhoeven
2000-10-14 17:18 ` Benjamin Herrenschmidt
2000-10-15 11:38 ` Geert Uytterhoeven
2000-10-17 0:03 ` James Simmons
-- strict thread matches above, loose matches on Subject: below --
2000-10-16 18:21 Brad Douglas
2000-10-17 1:31 ` James Simmons
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.10.10010102150540.375-100000@cassiopeia.home \
--to=geert@linux-m68k.org \
--cc=jsimmons@suse.com \
--cc=linux-fbdev@vuser.vu.union.edu \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=olh@suse.de \
--cc=samuel@ibrium.se \
/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).