From owner-freebsd-hackers Sun Nov 2 19:03:41 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id TAA29712 for hackers-outgoing; Sun, 2 Nov 1997 19:03:41 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from trojanhorse.ml.org (mdean.vip.best.com [206.86.94.101]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id TAA29669 for ; Sun, 2 Nov 1997 19:02:53 -0800 (PST) (envelope-from jamil@trojanhorse.ml.org) Received: from localhost (jamil@localhost) by trojanhorse.ml.org (8.8.7/8.8.5) with SMTP id TAA01300; Sun, 2 Nov 1997 19:02:16 -0800 (PST) Date: Sun, 2 Nov 1997 19:02:16 -0800 (PST) From: "Jamil J. Weatherbee" To: Mike Smith cc: =?iso-8859-1?Q?=DEor=F0ur?= Ivarsson , hackers@FreeBSD.ORG Subject: Re: 7400 gates effected by probe routine In-Reply-To: <199711030034.LAA00455@word.smith.net.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk There was one other thing with this board that I have thought about repeatedly. It has a jumper for tristated outputs, which would allow safe probing. However the way the tristate system works, it is either enabled or disabled for all outputs so when changing the mode of a port the outputs momentarily toggle to high impedance inputs, which defeats the purpose of having seperately controllable /dev/dio0? nodes. All in all I think it is just bad board design, nonetheless I think that anyone using one of these probably knows how it is set and doesn't need a probing routine. In other words the damn tristate bit shouldn't of been mapped over On Mon, 3 Nov 1997, Mike Smith wrote: > > I am not sure at the moment but I have been working with Rocwell 6522 > > PIA and I think it should be possible to probe 8255 in same manner as > > 6522, send byte to output ports and read back, if they are defined as > > output you should get the same back out from them. I think you can > > also with the control register. > > a) The 8255 defaults to all-ports-input at reset. > b) It is unacceptable to re-mode the 8255 and then write random garbage > into its output registers, as this may have undesirable or fatal > effects on attached hardware. > > > Do you have the 8255 datasheet ? it is available from Intel website > > I have (now) in front of me the Intel Peripheral Components databook. > This confirms that it is not possible to probe the 8255 in any useful > fashion without knowing what is connected on the other side. > > mike > > >