From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S263895AbTLXVOV (ORCPT ); Wed, 24 Dec 2003 16:14:21 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S263902AbTLXVOV (ORCPT ); Wed, 24 Dec 2003 16:14:21 -0500 Received: from fw.osdl.org ([65.172.181.6]:16822 "EHLO mail.osdl.org") by vger.kernel.org with ESMTP id S263895AbTLXVOU (ORCPT ); Wed, 24 Dec 2003 16:14:20 -0500 Date: Wed, 24 Dec 2003 13:12:23 -0800 From: "Randy.Dunlap" To: Ben Srour Cc: linux-kernel@vger.kernel.org Subject: Re: Safe ISA port probing? Message-Id: <20031224131223.2c3f497c.rddunlap@osdl.org> In-Reply-To: References: <20031224200433.GC6577@kroah.com> Organization: OSDL X-Mailer: Sylpheed version 0.9.4 (GTK+ 1.2.10; i686-pc-linux-gnu) X-Face: +5V?h'hZQPB9kW Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org On Wed, 24 Dec 2003 14:33:54 -0600 (CST) Ben Srour wrote: | Hello, | | What is the safest way to go about probing for non-pnp ISA devices on a | system? To be very safe, use a parameter and don't do probing, except to verify that the device is where you have been told it is. | Is the only solution to start at a base address and increment until you | find something interesting? Won't this put devices along the way in an | unsafe state? It could. | Any advice/suggestions would be appreciated, There's not a method that's always safe AFAIK. It's better to use reads instead of writes if possible. It's better to begin at the least-used addresses of other known devices as much as possible (but you know that). -- ~Randy MOTD: Always include version info.