The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Arno Griffioen via TUHS <tuhs@tuhs.org>
To: "tuhs@tuhs.org" <tuhs@tuhs.org>
Subject: [TUHS] Re: Origins of the frame buffer device
Date: Wed, 8 Mar 2023 14:17:47 +0100	[thread overview]
Message-ID: <ZAiK+3AFcdlZT6os@ancienthardware.org> (raw)
In-Reply-To: <28C479A6-053A-4D95-B6CE-13254FBD8068@planet.nl>

On Wed, Mar 08, 2023 at 01:51:10PM +0100, Paul Ruizendaal via TUHS wrote:
> It is then surprising that Linux did not come up with /dev/fbdev until 1999, 
> especially in view of the importance of X to the early Linux developers. 

The PC/intel 'birthplace' of Linux had the advantage that the video hardware
always had an ASCII mode, so from that viewpoint there was no need for 
any fb interface initially to get things going.

If I remember correctly, things like SCO Unix also did not use any fb-style
interface for their X11.

> Maybe the reason was that the headache of video drivers was delegated to 
> the XFree community.

Correct. There was definitely a sense that keeping all the graphics bits out 
of the kernel and just letting Xfree open /dev/mem and do it's magic was the 
preferred way. Also meant that Xfree wasn't waiting on kernel bits and 
vice-versa and could keep going in parallel.

Unlike today where there's only a few cards/manufacturers left, we had 
hundreds of similar-but-not-quite-the-same PC videocards on the market,
so it was an understandable sentiment as change was fast and frequent
on the Xfree end.

The FBdev idea really started brewing because of the non-intel Linux ports 
that did not have the luxury of a built-in ASCII-capable 'console' so needed 
to get something going there (after initial porting with serial output).

Something was needed 'in kernel' even for a plain console on the framebuffer 
and to keep it from falling apart some sort of general interface for some sort 
of generic X11 (even un-accelerated) as well.

Most of the non-PC framebuffer hardware was too 'obscure' for Xfree to spend 
much time on as well..

The Linux/M68k port with Geert being very active here and really pushing to 
getting a more generalised display setup going that would work on the wildly 
different framebuffer hardware between all the m68k platforms but make 
basically use of 1 simple X server that didn't need to know that much
about the hardware. 

Ultimately this led to the general FBdev project for all platforms.

							Bye, Arno.

  parent reply	other threads:[~2023-03-08 13:18 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-05 15:01 [TUHS] " Paul Ruizendaal via TUHS
2023-03-05 17:29 ` [TUHS] " Grant Taylor via TUHS
2023-03-05 18:25 ` Kenneth Goodwin
2023-03-06  8:51   ` Paul Ruizendaal via TUHS
2023-03-06  8:57     ` Rob Pike
2023-03-06 11:09       ` Henry Bent
2023-03-06 16:02         ` Theodore Ts'o
2023-03-06 22:47       ` Paul Ruizendaal via TUHS
2023-03-06 23:10         ` Rob Pike
2023-03-08 12:53           ` Paul Ruizendaal
2023-03-08 14:23             ` Dan Cross
2023-03-08 15:06               ` Paul Ruizendaal
2023-03-08 19:35                 ` Dan Cross
2023-03-08 16:55               ` Theodore Ts'o
2023-03-08 17:46                 ` Clem Cole
2023-03-08 17:45               ` Clem Cole
2023-03-08 18:12                 ` segaloco via TUHS
2023-03-08 18:21                   ` Larry McVoy
2023-03-08 18:43                     ` Kenneth Goodwin
2023-03-08 18:45                     ` Steffen Nurpmeso
2023-03-08 22:44                     ` Clem Cole
2023-03-09 14:42                 ` Paul Winalski
2023-03-06 23:20         ` segaloco via TUHS
2023-03-07  1:24     ` Kenneth Goodwin
2023-03-08  3:07     ` Rob Gingell
2023-03-08 12:51       ` Paul Ruizendaal via TUHS
2023-03-08 13:05         ` Warner Losh
2023-03-08 13:17         ` Arno Griffioen via TUHS [this message]
2023-03-07  1:54 ` Kenneth Goodwin
2023-03-05 18:52 Noel Chiappa
2023-03-05 20:43 ` Rob Pike
2023-03-06 10:43   ` Jonathan Gray
2023-03-07  1:21 ` Kenneth Goodwin
2023-03-08  5:43 ` Lars Brinkhoff
2023-03-09 23:24   ` emanuel stiebler
2023-03-10  1:44     ` Lawrence Stewart
2023-03-06 23:16 Norman Wilson
2023-03-06 23:24 ` Larry McVoy
2023-03-07 12:08   ` arnold
2023-03-07 16:42   ` Theodore Ts'o

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=ZAiK+3AFcdlZT6os@ancienthardware.org \
    --to=tuhs@tuhs.org \
    --cc=arno.griffioen@ieee.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;
as well as URLs for NNTP newsgroup(s).