From: Paul Ruizendaal via TUHS <tuhs@tuhs.org>
To: "tuhs@tuhs.org" <tuhs@tuhs.org>
Subject: [TUHS] Origins of the frame buffer device
Date: Sun, 5 Mar 2023 16:01:57 +0100 [thread overview]
Message-ID: <A2FD3A10-A593-4A6E-8736-444D78F0CAD2@planet.nl> (raw)
I am confused on the history of the frame buffer device.
On Linux, it seems that /dev/fbdev originated in 1999 from work done by Martin Schaller and Geert Uytterhoeven (and some input from Fabrice Bellard?).
However, it would seem at first glance that early SunOS also had a frame buffer device (/dev/cgoneX. /dev/bwoneX, etc.) which was similar in nature (a character device that could be mmap’ed to give access to the hardware frame buffer, and ioctl’s to probe and configure the hardware). Is that correct, or were these entirely different in nature?
Paul
next reply other threads:[~2023-03-05 15:02 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-05 15:01 Paul Ruizendaal via TUHS [this message]
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
2023-03-07 1:54 ` Kenneth Goodwin
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=A2FD3A10-A593-4A6E-8736-444D78F0CAD2@planet.nl \
--to=tuhs@tuhs.org \
--cc=pnr@planet.nl \
/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).