From owner-freebsd-current  Tue Dec 29 14:28:03 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id OAA21529
          for freebsd-current-outgoing; Tue, 29 Dec 1998 14:28:03 -0800 (PST)
          (envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from mail.atl.bellsouth.net (mail.atl.bellsouth.net [205.152.0.21])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA21476
          for <FreeBSD-current@FreeBSD.ORG>; Tue, 29 Dec 1998 14:28:00 -0800 (PST)
          (envelope-from wghicks@bellsouth.net)
Received: from bellsouth.net (host-209-214-69-223.atl.bellsouth.net [209.214.69.223])
	by mail.atl.bellsouth.net (8.8.8-spamdog/8.8.5) with ESMTP id QAA10484;
	Tue, 29 Dec 1998 16:45:22 -0500 (EST)
Message-ID: <36895118.E8C57354@bellsouth.net>
Date: Tue, 29 Dec 1998 17:00:56 -0500
From: W Gerald Hicks <wghicks@bellsouth.net>
Organization: Fair Play, Uninc.
X-Mailer: Mozilla 4.5 [en] (X11; I; FreeBSD 3.0-CURRENT i386)
X-Accept-Language: en
MIME-Version: 1.0
To: FreeBSD-current@FreeBSD.ORG
CC: jkh@zippy.cdrom.com
Subject: Re: How do I build an a.out kld?
Content-Type: multipart/mixed;
 boundary="------------78624E7EE9410BFCC358DF80"
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

This is a multi-part message in MIME format.
--------------78624E7EE9410BFCC358DF80
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

[snips]
> /boot/boot.conf is supposed to contain any boot commands you'd like to
> have run (boot.conf is actually a bad name, now that I think about it,
> since it implies configuration variables rather than actions - boot.rc
> would have been better, oh well!).  After the forth system initializes,
> it also looks for a /boot/boot.4th which contains straight forth code
> to run.  Andrzej Bialecki has done some really neat stuff where this
> is concerned, giving the forth environment a screen emulator and
> standard ANSI graphics capability.  He shows it off in the example
> code, which you can enable by simply doing a:
> 
>       cp /usr/share/examples/bootforth/*.4th /boot
> 

We've been having loads of fun with BootForth too.  Thanks Andrzej!

I tried generating console beeps (7 emit) and noticed them going to the
screen.  Patch attached  :)

Cheers,

Jerry Hicks
wghicks@bellsouth.net
--------------78624E7EE9410BFCC358DF80
Content-Type: text/plain; charset=us-ascii;
 name="diffs"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline;
 filename="diffs"

Index: src/sys/boot/i386/libi386/vidconsole.c
===================================================================
RCS file: /home/ncvs/src/sys/boot/i386/libi386/vidconsole.c,v
retrieving revision 1.9
diff -u -r1.9 vidconsole.c
--- vidconsole.c	1998/12/22 11:51:25	1.9
+++ vidconsole.c	1998/12/29 21:37:31
@@ -119,7 +119,19 @@
     return(0);	/* XXX reinit? */
 }
 
+#ifdef TERM_EMU
 static void
+vidc_biosrawputchar(int c)
+{
+    v86.ctl = 0;
+    v86.addr = 0x10;
+    v86.eax = 0xe00 | c;
+    v86.ebx = 0x7;
+    v86int();
+}
+#endif
+
+static void
 vidc_rawputchar(int c)
 {
     int		i;
@@ -138,6 +150,9 @@
 #else
 	/* Emulate AH=0eh (teletype output) */
 	switch(c) {
+	case '\a':
+		vidc_biosrawputchar(c);
+		return;
 	case '\r':
 		curx=0;
 		curs_move(curx,cury);

--------------78624E7EE9410BFCC358DF80--


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message