| 1 |
Hello, Wol. |
| 2 |
|
| 3 |
On Thu, Jan 21, 2021 at 09:32:13 +0000, Wols Lists wrote: |
| 4 |
> On 20/01/21 19:59, Alan Mackenzie wrote: |
| 5 |
> > I can understand the kernel maintainers not being enthusiastic about |
| 6 |
> > the existing code. But that dates from, I believe, the 1990s, when |
| 7 |
> > RAM was measured in megabytes, and processor speeds in megahertz. |
| 8 |
> > Optimisation for speed and store usage just isn't important any more. |
| 9 |
|
| 10 |
> I think you're being highly optimistic. Bear in mind that this is the |
| 11 |
> code that was responsible for Alan Cox ceasing linux development, it's |
| 12 |
> such a pile of steaming manure ... |
| 13 |
|
| 14 |
It is indeed a tortuous mess of code, with far too many abstractions, and |
| 15 |
far too little overview. |
| 16 |
|
| 17 |
> Don't ask me why it is, but I think it's got so much stuff wrong with it |
| 18 |
> that the entire system is marked "beware here be dragons". |
| 19 |
|
| 20 |
Over the weekend, I achieved the first part of my task, getting a |
| 21 |
transparent new driver into the kernel, which would merely pass through |
| 22 |
to and from /dev/sctty3 to and from /dev/tty3, etc. This works. |
| 23 |
|
| 24 |
Now I have to hook up with the /dev/vcs drivers to buffer the text |
| 25 |
written to the screen, so as to be able to output it again in the event |
| 26 |
of a <Ctrl>-<PageUp/Down>. |
| 27 |
|
| 28 |
I would guess I'm around 50% through the task (as in the first 50% takes |
| 29 |
the first 90% of the time, and the second 50% takes the second 90% of the |
| 30 |
time). |
| 31 |
|
| 32 |
> https://lwn.net/Articles/842415/ |
| 33 |
|
| 34 |
> Take a read, as it's mentioned in this article. |
| 35 |
|
| 36 |
The website said it would become freely available on 2021-01-28, so I'll |
| 37 |
read it then. |
| 38 |
|
| 39 |
> Cheers, |
| 40 |
> Wol |
| 41 |
|
| 42 |
-- |
| 43 |
Alan Mackenzie (Nuremberg, Germany). |
Archives