From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on inbox.vuxu.org X-Spam-Level: X-Spam-Status: No, score=-0.8 required=5.0 tests=DKIM_ADSP_CUSTOM_MED, DKIM_INVALID,DKIM_SIGNED,FREEMAIL_FROM,HTML_MESSAGE,MAILING_LIST_MULTI autolearn=ham autolearn_force=no version=3.4.4 Received: (qmail 18130 invoked from network); 7 Mar 2023 01:54:39 -0000 Received: from minnie.tuhs.org (50.116.15.146) by inbox.vuxu.org with ESMTPUTF8; 7 Mar 2023 01:54:39 -0000 Received: from minnie.tuhs.org (localhost [IPv6:::1]) by minnie.tuhs.org (Postfix) with ESMTP id 757DB41214; Tue, 7 Mar 2023 11:54:34 +1000 (AEST) Received: from mail-wr1-x436.google.com (mail-wr1-x436.google.com [IPv6:2a00:1450:4864:20::436]) by minnie.tuhs.org (Postfix) with ESMTPS id 1DB05411EE for ; Tue, 7 Mar 2023 11:54:29 +1000 (AEST) Received: by mail-wr1-x436.google.com with SMTP id bw19so10669398wrb.13 for ; Mon, 06 Mar 2023 17:54:29 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; t=1678154067; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=YdA9/x8UB6+7muwzIZ8R+17pDxfit3XVDXh8pnFxc0k=; b=XkJRtWGTYipe6W1Pkp5vpmTOa6IQ51YTVBFAvNA3zxwxl088JfnUnPXvmyzd8sN8Gx 9af+VEST6IHazAwqNff3ho0uLTv+R46sepUtlbXiFWEW9syDHqcCTvM3DBRF75ze2Y0B 7Xazab1L2yk2tbx2EBmJRYmKTwt8PQ+azKgTg2rXRCRktphPJwSjeW8lLoWOAqMDL+4m F2Hyuy/1BiaK+9T8330An8KrfxrHLtA7OeHfLe5JUc22cTehTE+C+QGuOrymzDfjQ63d woJfctlykJh7NttndR63aOfVkF3MebWVxtI9ugJ+4meZ9J+KPFLNJycjgDdM/JyLEcFO jsJw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; t=1678154067; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=YdA9/x8UB6+7muwzIZ8R+17pDxfit3XVDXh8pnFxc0k=; b=Rjg25/EOD6ZdYbv1R4jUKR9/Sitnhtea0E9NElxzJ1rO+ZAe0osEo8q/yuaF9K5to1 FLPRZ+vFAhelpdJiXLH4FGL382o36sd7cQ+CyrF/EDt0ph9zAuMTlqb5X+uJTrXJibzQ nBVH1sAW8rhFzzqDdgijI1accK7wxt7iSFBRiAD0VAHIA+eMuiY6YvGK4sKfcOM4zcey M1eOkcJWFqscbosDUxwPSbbC+QC/Sz4PdPoUydem3WHEL7MdJFjgLNQARSNZFYp3HTdH DhbpFiciFC24gBZQ9Yu9sTuzp0m0Ydv3RERS0bcyN6yzRkV3ueoPxHKfo6GP/TwUPSgv netA== X-Gm-Message-State: AO0yUKVK2Q6zRHpfAYeP4jldokjmImnglVHHVTw5hfgEJI5uIk83vmJc gz73ZrTgQHmJXCRyUqQ8T/qFclmRQt3gjRBW9zcyKhgp X-Google-Smtp-Source: AK7set8VtV00RUU2Egc6rlYEfMyPhapLuoaVfQG6Y4+b+gEQcL+RXdXWFP8UIONzFveA2DL947veq0Vad74KnFe4Oaw= X-Received: by 2002:a5d:428c:0:b0:2c9:8a3c:9fa0 with SMTP id k12-20020a5d428c000000b002c98a3c9fa0mr2784640wrq.3.1678154067177; Mon, 06 Mar 2023 17:54:27 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: From: Kenneth Goodwin Date: Mon, 6 Mar 2023 20:54:16 -0500 Message-ID: To: Paul Ruizendaal Content-Type: multipart/alternative; boundary="0000000000000d739c05f645b1b6" Message-ID-Hash: THTKDQJUI4Z7HNL2RWRATRIEC2G3WSLL X-Message-ID-Hash: THTKDQJUI4Z7HNL2RWRATRIEC2G3WSLL X-MailFrom: kennethgoodwin56@gmail.com X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header CC: The Eunuchs Hysterical Society X-Mailman-Version: 3.3.6b1 Precedence: list Subject: [TUHS] Re: Origins of the frame buffer device List-Id: The Unix Heritage Society mailing list Archived-At: List-Archive: List-Help: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: --0000000000000d739c05f645b1b6 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable The NYIT setup had multiple Barcovision color CRT monitors connected to the frame buffers via multiple coax video cables I presume through some sort of video switch hardware. 8 bits per pixel. (Unsigned char) The numbers stored in the pixel frame buffer memory were used to index a color map that held the actual RGB or HSV values for the actual color. Cycling the color map array values was a cheap animation trick that Alex Schure had a particular fondness for. On Sun, Mar 5, 2023, 10:02 AM Paul Ruizendaal via TUHS wrote: > 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 natur= e > (a character device that could be mmap=E2=80=99ed to give access to the h= ardware > frame buffer, and ioctl=E2=80=99s to probe and configure the hardware). I= s that > correct, or were these entirely different in nature? > > Paul > > --0000000000000d739c05f645b1b6 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
The NYIT setup had multiple Barcovision color CRT monitor= s connected to the frame buffers via multiple coax video cables

I presume through some sort of video swi= tch hardware.

8 bits per= pixel. (Unsigned char)
The numbers stored in the pi= xel frame buffer memory were used to index a color map that held the actual= RGB or HSV values for the actual color.

<= div dir=3D"auto">Cycling the color map array values was a cheap animation = trick that Alex Schure had a particular fondness for.=C2=A0

=
On Sun, Ma= r 5, 2023, 10:02 AM Paul Ruizendaal via TUHS <tuhs@tuhs.org> wrote:
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=C2= =A0 Martin Schaller and=C2=A0 Geert Uytterhoeven (and some input from Fabri= ce Bellard?).

However, it would seem at first glance that early SunOS also had a frame bu= ffer device (/dev/cgoneX. /dev/bwoneX, etc.) which was similar in nature (a= character device that could be mmap=E2=80=99ed to give access to the hardw= are frame buffer, and ioctl=E2=80=99s to probe and configure the hardware).= Is that correct, or were these entirely different in nature?

Paul

--0000000000000d739c05f645b1b6--