From owner-freebsd-hackers@FreeBSD.ORG Tue Feb 10 11:42:06 2009 Return-Path: Delivered-To: freebsd-hackers@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5EFA5106566B for ; Tue, 10 Feb 2009 11:42:06 +0000 (UTC) (envelope-from avg@icyb.net.ua) Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id 814C68FC0C for ; Tue, 10 Feb 2009 11:42:05 +0000 (UTC) (envelope-from avg@icyb.net.ua) Received: from odyssey.starpoint.kiev.ua (alpha-e.starpoint.kiev.ua [212.40.38.101]) by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id NAA01162 for ; Tue, 10 Feb 2009 13:42:03 +0200 (EET) (envelope-from avg@icyb.net.ua) Message-ID: <4991680A.5010905@icyb.net.ua> Date: Tue, 10 Feb 2009 13:42:02 +0200 From: Andriy Gapon User-Agent: Thunderbird 2.0.0.19 (X11/20090110) MIME-Version: 1.0 To: freebsd-hackers@FreeBSD.org Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Cc: Subject: superio and "shared" io port X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 10 Feb 2009 11:42:06 -0000 Here I am with Super I/O question again. There is a certain Super I/O that is configured to use the same port for entering/exiting configuration mode as the one that is used by fdc in the same Super I/O. This is port 0x3f0. I guess the hardware works by examining a value written to this port and forwarding non-magic accesses to the fdc. I wonder what is the best way to handle this double-use of an io port with newbus isa code. -- Andriy Gapon