mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: jbradford@dial.pipex.com
To: ken@kenmoffat.uklinux.net (Ken Moffat)
Cc: pommnitz@yahoo.com, linux-kernel@vger.kernel.org
Subject: Re: Framebuffer still "EXPERIMENTAL"?
Date: Sat, 28 Sep 2002 16:50:40 +0100 (BST)	[thread overview]
Message-ID: <200209281550.g8SFoeXx001215@darkstar.example.net> (raw)
In-Reply-To: <Pine.LNX.4.21.0209281558290.3427-100000@ppg_penguin.linux.bogus> from "Ken Moffat" at Sep 28, 2002 04:02:05 PM

> > > Hello Listees,
> > > yesterday I compiled 2.5.38 for the first time and noticed that the
> > > framebuffer option is still marked "EXPERIMENTAL". Well, I know for sure
> > > that I used the VESA-FB 3 years ago to get X running on a strange laptop
> > > graphic chip, so it is at least that long available (actually I think it
> > > got introduced for the Sparc port somewhen in 1995??). 
> > > 
> > > I think it's about time to promote the framebuffer code to a full fledged
> > > kernel feature. Comments?
> > 
> > I've noticed a bug with it, but haven't had time to investigate more fully,
> > infact it might not be a kernel bug, but I suspect that it is.  I don't
> > usually use the framebuffer, (I prefer the standard text mode).
> > 
> > On a standard Slackware 8.1 install, (kernel 2.4.18), on a machine with an
> > ATI graphics card, and with the framebuffer enabled, if you type clear, then
> > fill the screen with text so that it scrolls, (e.g. do a find /), the top
> > four lines where the penguin used to be do not scroll, they just keep the
> > text that is originally put there.  If you press shift-pageup, and then
> > shift-pagedown, it fixes it.
> > 
> > If anybody has got the time to look in to this, I'll post more details.
> > 
> > John.
> 
> Normal operation. Either switch to a different tty, or set a font.

Hmmm, if that's normal operation, surely it's a bug?

Infact, why not use the wasted space to the right of the penguin for something useful - I.E. a status line, like on old terminals, showing disk and serial port activity!?

> There does seem to be a bug in your mailer, though (excessive line
> length) :->

I guess maybe it's time for me to move away from using 'mail' from the command line for my day to day E-Mail needs :-(.  Already, I have to use elm when I need the quoting capabilities so lacking from my favourite mailer :-).

John.

  reply	other threads:[~2002-09-28 15:37 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-27  7:09 Joerg Pommnitz
2002-09-27 11:06 ` jbradford
2002-09-28 15:02   ` Ken Moffat
2002-09-28 15:50     ` jbradford [this message]
2002-09-28 22:20       ` Ken Moffat

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=200209281550.g8SFoeXx001215@darkstar.example.net \
    --to=jbradford@dial.pipex.com \
    --cc=ken@kenmoffat.uklinux.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pommnitz@yahoo.com \
    /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®