From: Alan Mackenzie <acm@muc.de>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Console scrollback
Date: Mon, 25 Jan 2021 12:42:53 +0000 [thread overview]
Message-ID: <YA68zV+9AhMEkoWf@ACM> (raw)
In-Reply-To: <60094A1D.3020505@youngman.org.uk>
Hello, Wol.
On Thu, Jan 21, 2021 at 09:32:13 +0000, Wols Lists wrote:
> On 20/01/21 19:59, Alan Mackenzie wrote:
> > I can understand the kernel maintainers not being enthusiastic about
> > the existing code. But that dates from, I believe, the 1990s, when
> > RAM was measured in megabytes, and processor speeds in megahertz.
> > Optimisation for speed and store usage just isn't important any more.
> I think you're being highly optimistic. Bear in mind that this is the
> code that was responsible for Alan Cox ceasing linux development, it's
> such a pile of steaming manure ...
It is indeed a tortuous mess of code, with far too many abstractions, and
far too little overview.
> Don't ask me why it is, but I think it's got so much stuff wrong with it
> that the entire system is marked "beware here be dragons".
Over the weekend, I achieved the first part of my task, getting a
transparent new driver into the kernel, which would merely pass through
to and from /dev/sctty3 to and from /dev/tty3, etc. This works.
Now I have to hook up with the /dev/vcs drivers to buffer the text
written to the screen, so as to be able to output it again in the event
of a <Ctrl>-<PageUp/Down>.
I would guess I'm around 50% through the task (as in the first 50% takes
the first 90% of the time, and the second 50% takes the second 90% of the
time).
> https://lwn.net/Articles/842415/
> Take a read, as it's mentioned in this article.
The website said it would become freely available on 2021-01-28, so I'll
read it then.
> Cheers,
> Wol
--
Alan Mackenzie (Nuremberg, Germany).
next prev parent reply other threads:[~2021-01-25 21:43 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-13 10:30 [gentoo-user] Console scrollback Peter Humphrey
2021-01-13 10:38 ` Michael
2021-01-13 10:55 ` Peter Humphrey
2021-01-13 11:21 ` Andreas Fink
2021-01-13 11:46 ` Peter Humphrey
2021-01-13 18:14 ` Alan Mackenzie
2021-01-13 18:44 ` Neil Bothwick
2021-01-14 16:00 ` Alan Mackenzie
2021-01-13 19:14 ` Peter Humphrey
2021-01-13 19:32 ` Grant Taylor
2021-01-13 21:56 ` Alan Mackenzie
2021-01-13 22:14 ` Grant Taylor
2021-01-14 16:39 ` karl
2021-01-13 22:15 ` [gentoo-user] " Grant Edwards
2021-01-13 23:01 ` Neil Bothwick
2021-01-13 23:06 ` Grant Edwards
2021-01-14 0:00 ` Grant Taylor
2021-01-14 1:25 ` Grant Edwards
2021-01-14 17:10 ` Grant Taylor
2021-01-14 0:12 ` Neil Bothwick
2021-01-14 16:06 ` Alan Mackenzie
2021-01-16 12:01 ` Alan Mackenzie
2021-01-17 5:17 ` [gentoo-user] " Thomas Mueller
[not found] ` <20210117051748.E3239E0869@pigeon.gentoo.org>
2021-01-17 9:16 ` Philip Webb
[not found] ` <20210117051748.B8178E0863@pigeon.gentoo.org>
2021-01-19 17:09 ` Laurence Perkins
2021-01-20 19:59 ` Alan Mackenzie
2021-01-21 9:32 ` Wols Lists
2021-01-21 8:58 ` Jorge Almeida
2021-01-21 12:40 ` Remco Rijnders
2021-01-21 13:00 ` Jorge Almeida
2021-01-25 12:42 ` Alan Mackenzie [this message]
2021-04-02 18:30 ` Alan Mackenzie
2021-04-02 19:32 ` karl
2021-04-02 20:49 ` Alan Mackenzie
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=YA68zV+9AhMEkoWf@ACM \
--to=acm@muc.de \
--cc=gentoo-user@lists.gentoo.org \
/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