All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@ucw.cz>
To: James Simmons <jsimmons@infradead.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux console project <linuxconsole-dev@lists.sourceforge.net>,
	Linux Fbdev development list
	<linux-fbdev-devel@lists.sourceforge.net>
Subject: Re: [BK console] console updates.
Date: Fri, 1 Nov 2002 22:11:54 +0100	[thread overview]
Message-ID: <20021101211153.GA171@elf.ucw.cz> (raw)
In-Reply-To: <Pine.LNX.4.33.0210301343580.1392-100000@maxwell.earthlink.net>

Hi!

>    Along with the new fbdev api I also have rewritten the console layer.
> The goals are:

Current 2.5.45 (and previous 2.5's) has funny problems on my vesafb
machines [like half of letters appearing during emacs session, to the
point you do ^L to repaint]. I hope this fixes it....
								Pavel
-- 
When do you have heart between your knees?

  parent reply	other threads:[~2002-11-01 21:11 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-30 21:56 [BK console] console updates James Simmons
2002-10-30 21:56 ` James Simmons
2002-10-30 21:52 ` Christoph Hellwig
2002-11-01  1:37   ` [Linux-fbdev-devel] " James Simmons
2002-11-01 11:06     ` Skip Ford
2002-11-01 17:13       ` James Simmons
2002-11-01 17:40   ` James Simmons
2003-01-02 12:32     ` 2.5.54: radeonfb almost works Helge Hafting
2003-01-07 21:34       ` James Simmons
2002-10-30 22:12 ` [BK console] console updates Andreas Schuldei
2002-10-31 10:38   ` Svetoslav Slavtchev
2002-11-01  1:38   ` [Linux-fbdev-devel] " James Simmons
2002-10-30 23:32 ` Skip Ford
2002-10-30 23:00   ` M. R. Brown
2002-10-30 23:08     ` Martin J. Bligh
2002-11-01 15:06   ` Petr Baudis
2002-11-01 21:11 ` Pavel Machek [this message]
2002-11-09  1:02   ` [Linux-fbdev-devel] " James Simmons
  -- strict thread matches above, loose matches on Subject: below --
2002-11-04  9:40 Aivils Stoss

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=20021101211153.GA171@elf.ucw.cz \
    --to=pavel@ucw.cz \
    --cc=jsimmons@infradead.org \
    --cc=linux-fbdev-devel@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxconsole-dev@lists.sourceforge.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.