All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Gortmaker <p_gortmaker@yahoo.com>
To: esr@thyrsus.com
Cc: Dave Jones <davej@suse.de>,
	Jeff Garzik <jgarzik@mandrakesoft.com>,
	Linux Kernel List <linux-kernel@vger.kernel.org>
Subject: Re: Calling EISA experts
Date: Mon, 21 Jan 2002 06:49:42 -0500	[thread overview]
Message-ID: <3C4C0056.4F50C3D6@yahoo.com> (raw)
In-Reply-To: <20020117015456.A628@thyrsus.com> <20020117121723.B22171@suse.de> <3C46B718.26F52BD5@mandrakesoft.com> <20020117124849.F22171@suse.de> <20020117085056.B7299@thyrsus.com>

Eric S. Raymond wrote:

> Bingo.  I've got reliable /proc tests for ISAPNP, PCI, and MCA.  Previous
> discussion indicates I can't get one for ISA classic.  An EISA test would,
> as ever, allow me to cut the number of questions about ancient dead
> hardware that users have to see.

Minimal approach: Register motherboard EISA ID (i.e. slot zero) ports in
/proc/ioports.  Works on all kernel versions.  See $0.02 patch below.

This is probably the least intrusive way to get what you want.  It doesn't
add Yet Another Proc File, and costs zero bloat to the 99.9% of us who 
have a better chance of meeting Aunt Tillie than an EISA box. 

Possible alternative: Create something like /proc/bus/eisa/devices which
lists the EISA ID (e.g. abc0123) found in each EISA slot.   This might
have been worthwhile some 8 years ago, but now? ....

Paul.


--- arch/i386/kernel/setup.c~	Tue Nov  6 19:14:03 2001
+++ arch/i386/kernel/setup.c	Mon Jan 21 06:22:15 2002
@@ -122,6 +122,7 @@
  */
 #ifdef CONFIG_EISA
 int EISA_bus;
+struct resource eisa_id = { "EISA ID", 0xc80, 0xc83, IORESOURCE_BUSY };
 #endif
 int MCA_bus;
 
@@ -1020,6 +1021,11 @@
 	/* request I/O space for devices used on all i[345]86 PCs */
 	for (i = 0; i < STANDARD_IO_RESOURCES; i++)
 		request_resource(&ioport_resource, standard_io_resources+i);
+
+#ifdef CONFIG_EISA
+	if (EISA_bus)
+		request_resource(&ioport_resource, &eisa_id);
+#endif
 
 	/* Tell the PCI layer not to allocate too close to the RAM area.. */
 	low_mem_size = ((max_low_pfn << PAGE_SHIFT) + 0xfffff) & ~0xfffff;


  reply	other threads:[~2002-01-21 11:49 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-17  6:54 Calling EISA experts Eric S. Raymond
2002-01-17  8:54 ` Marc ZYNGIER
2002-01-17 10:19   ` Alan Olsen
2002-01-17  9:46     ` Chris Wedgwood
2002-01-17 11:17 ` Dave Jones
2002-01-17 11:35   ` Jeff Garzik
2002-01-17 11:48     ` Dave Jones
2002-01-17 13:50       ` Eric S. Raymond
2002-01-21 11:49         ` Paul Gortmaker [this message]
2002-01-21 13:08           ` Jeff Garzik
2002-01-22  5:52             ` Eric S. Raymond
2002-01-22  6:39               ` William Stearns
2002-01-22 18:57           ` Eric S. Raymond
2002-01-22 19:59             ` Dave Jones
2002-01-17 17:30 ` Dennis Boylan
2002-01-18  7:02 ` Jeremy Jackson

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3C4C0056.4F50C3D6@yahoo.com \
    --to=p_gortmaker@yahoo.com \
    --cc=davej@suse.de \
    --cc=esr@thyrsus.com \
    --cc=jgarzik@mandrakesoft.com \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.