From owner-freebsd-current Wed May 7 15:42:05 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id PAA22569 for current-outgoing; Wed, 7 May 1997 15:42:05 -0700 (PDT) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id PAA22564 for ; Wed, 7 May 1997 15:42:00 -0700 (PDT) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.5/8.6.9) id IAA22017; Thu, 8 May 1997 08:36:21 +1000 Date: Thu, 8 May 1997 08:36:21 +1000 From: Bruce Evans Message-Id: <199705072236.IAA22017@godzilla.zeta.org.au> To: bde@zeta.org.au, gibbs@plutotech.com Subject: Re: Problems using remote gdb Cc: current@freebsd.org Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >>No, you must have 0x10 to get console support. 0x40 is optional. It >>makes debugging work better at a cost of breaking ordinary serial console >>support. See LINT. > >Well, it looked like 0x40 was a no-op without 0x10. Debugging wouldn't >work for me without setting the flags, so I'd say that the flags "make >debugging work better" is an understatement. 8-) Correct, but 0x10 is not a no-op without 0x40. It gives backwards compatible behaviour. (I couldn't figure out a good way to make flags 0 give backwards compatible behaviour without breaking the new feature of setting the console device by setting flags on it.) Bruce