From owner-freebsd-current  Sat Dec 27 19:17:04 1997
Return-Path: <owner-freebsd-current>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.7/8.8.7) id TAA10953
          for current-outgoing; Sat, 27 Dec 1997 19:17:04 -0800 (PST)
          (envelope-from owner-freebsd-current)
Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19])
          by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id TAA10913
          for <freebsd-current@FreeBSD.ORG>; Sat, 27 Dec 1997 19:16:47 -0800 (PST)
          (envelope-from bde@godzilla.zeta.org.au)
Received: (from bde@localhost)
	by godzilla.zeta.org.au (8.8.7/8.8.7) id OAA03628;
	Sun, 28 Dec 1997 14:13:45 +1100
Date: Sun, 28 Dec 1997 14:13:45 +1100
From: Bruce Evans <bde@zeta.org.au>
Message-Id: <199712280313.OAA03628@godzilla.zeta.org.au>
To: bde@zeta.org.au, grog@lemis.com
Subject: Re: Remote gdb (was: no boot: config -g and options DDB)
Cc: freebsd-current@FreeBSD.ORG, skynyrd@opus.cts.cwu.edu
Sender: owner-freebsd-current@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

>> Just like fopen() doesn't set the speed.  It knows nothing of
>> devices.
>
>Yes, but fwrite() doesn't go on and talk to the device registers.  ddb

Sure it does, if the output stream is a device.

>does, without first setting them.

Same.  It calls the device driver which writes to the registers.

>ddb doesn't use the device driver.  It talks directly to the device
>with functions like:
>
>void
>siocnputc(dev, c)

These functions are part of the device driver.

Bruce