From a718d9d893f06b995d01ccf3ac41f1a5c81d10f8 Mon Sep 17 00:00:00 2001 From: Miod Vallat Date: Sat, 12 May 2012 16:47:45 +0000 Subject: It turns out that, when the IRIX header files mention CTR/DCD/DTR/RTS wiring is inverted on Indigo, this just means that Indigo does not use the same values as the later models. It does not mean that the Indigo is using wrong values, which is how I first read this. In reality, Indigo systems use the expected values of these signals being active low, while later designs use active high signals. So yes, some systems have inverted values - but the ones which need compensating are not those I thought. Change the logic to do TRT, but keep the device flags check, to be able to force the other behaviour if the kernel guesses wrongly. Tested on Indigo, Indy and Indigo 2. --- sys/arch/sgi/include/z8530var.h | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) (limited to 'sys/arch/sgi/include') diff --git a/sys/arch/sgi/include/z8530var.h b/sys/arch/sgi/include/z8530var.h index a71726ddefb..487913357af 100644 --- a/sys/arch/sgi/include/z8530var.h +++ b/sys/arch/sgi/include/z8530var.h @@ -1,4 +1,4 @@ -/* $OpenBSD: z8530var.h,v 1.2 2012/04/29 08:59:12 miod Exp $ */ +/* $OpenBSD: z8530var.h,v 1.3 2012/05/12 16:47:44 miod Exp $ */ /* $NetBSD: z8530var.h,v 1.10 2011/07/01 21:00:21 dyoung Exp $ */ /* @@ -92,7 +92,7 @@ struct zs_channel { bus_space_tag_t cs_bustag; /* Machine-dependent */ bus_space_handle_t cs_regs; int cs_flags; -#define ZSCFL_INDIGO_WIRING 0x01 +#define ZSCFL_INVERT_WIRING 0x01 }; struct zsc_softc { -- cgit v1.2.3