Calling EISA experts

Calling EISA experts

[Eric S. Raymond]

Does anything in /proc or elswhere reliably register the presence of EISA?  

Failing that, have any motherboards existed that had both PCI and EISA slots?

(Yes, I have RTFD.  That's why I'm asking.)
-- 
		<a href="http://www.tuxedo.org/~esr/">Eric S. Raymond</a>

Certainly one of the chief guarantees of freedom under any government,
no matter how popular and respected, is the right of the citizens to
keep and bear arms.  [...] the right of the citizens to bear arms is
just one guarantee against arbitrary government and one more safeguard
against a tyranny which now appears remote in America, but which
historically has proved to be always possible.
        -- Hubert H. Humphrey, 1960

Re: Calling EISA experts

[Marc ZYNGIER]

>>>>> "Eric" == Eric S Raymond <esr@thyrsus.com> writes:

Eric> Does anything in /proc or elswhere reliably register the
Eric> presence of EISA?

On my dual PPro, /proc/pci shows :

  Bus  0, device   2, function  0:
    Non-VGA unclassified device: Intel Corp. 82375EB (rev 21).
      Master Capable.  Latency=248.  

This is a PCI-EISA bridge.

Eric> Failing that, have any motherboards existed that had both PCI
Eric> and EISA slots?

I have two of this kind : This dual Pentium Pro (Nec motherboard), and
a Digital AlphaServer 1000.

Most high-end Pentium-Pro motherboard had both PCI and EISA slots.

Regards,

        Marc.
-- 
Places change, faces change. Life is so very strange.

Re: Calling EISA experts

[Chris Wedgwood]

Compaq Deskpro 466's had both... these were 486/66s



  --cw

On Thu, Jan 17, 2002 at 02:19:41AM -0800, Alan Olsen wrote:

   On 17 Jan 2002, Marc ZYNGIER wrote:

    > Most high-end Pentium-Pro motherboard had both PCI and EISA slots.

    I think that depends on when it was made and by whom.  My Micron Millenia
    pro2 with dual Pentium-pro 200s does not have EISA at all.

Re: Calling EISA experts

[Alan Olsen]

On 17 Jan 2002, Marc ZYNGIER wrote:

> Most high-end Pentium-Pro motherboard had both PCI and EISA slots.

I think that depends on when it was made and by whom.  My Micron Millenia 
pro2 with dual Pentium-pro 200s does not have EISA at all.

-- 
alan@ctrl-alt-del.com | Note to AOL users: for a quick shortcut to reply
Alan Olsen            | to my mail, just hit the ctrl, alt and del keys.
 "All power is derived from the barrel of a gnu." - Mao Tse Stallman

Re: Calling EISA experts

[Dave Jones]

On Thu, Jan 17, 2002 at 01:54:56AM -0500, Eric S. Raymond wrote:
 > Does anything in /proc or elswhere reliably register the presence of EISA?  

 Not afaik. I'm tempted to hack support for it into driverfs.

-- 
| Dave Jones.        http://www.codemonkey.org.uk
| SuSE Labs

Re: Calling EISA experts

[Jeff Garzik]

Dave Jones wrote:
> 
> On Thu, Jan 17, 2002 at 01:54:56AM -0500, Eric S. Raymond wrote:
>  > Does anything in /proc or elswhere reliably register the presence of EISA?
> 
>  Not afaik. I'm tempted to hack support for it into driverfs.

The EISA_bus global variable indicates presence...

-- 
Jeff Garzik      | Alternate titles for LOTR:
Building 1024    | Fast Times at Uruk-Hai
MandrakeSoft     | The Took, the Elf, His Daughter and Her Lover
                 | Samwise Gamgee: International Hobbit of Mystery

Re: Calling EISA experts

[Dave Jones]

On Thu, Jan 17, 2002 at 06:35:52AM -0500, Jeff Garzik wrote:
 > >  > Does anything in /proc or elswhere reliably register the presence of EISA?
 > >  Not afaik. I'm tempted to hack support for it into driverfs.
 > The EISA_bus global variable indicates presence...

 *nod*, though you can almost guarantee this isn't what Eric wants.
 I'm assuming he wants something a'la /proc/pci
 Hacking the EISA code to register a driver in driverfs should be
 fairly trivial. I'll wait and see what Pat does with the
 busdriver reworking that he's up to right now before doing anything
 on this though.

-- 
| Dave Jones.        http://www.codemonkey.org.uk
| SuSE Labs

Re: Calling EISA experts

[Eric S. Raymond]

Dave Jones <davej@suse.de>:
>  > >  Not afaik. I'm tempted to hack support for it into driverfs.
>  > The EISA_bus global variable indicates presence...
> 
>  *nod*, though you can almost guarantee this isn't what Eric wants.
>  I'm assuming he wants something a'la /proc/pci

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.
-- 
		<a href="http://www.tuxedo.org/~esr/">Eric S. Raymond</a>

The biggest hypocrites on gun control are those who live in upscale
developments with armed security guards -- and who want to keep other
people from having guns to defend themselves.  But what about
lower-income people living in high-crime, inner city neighborhoods?
Should such people be kept unarmed and helpless, so that limousine
liberals can 'make a statement' by adding to the thousands of gun laws
already on the books?"
	--Thomas Sowell

Re: Calling EISA experts

[Dennis Boylan]

I've got a Micronics M54Pe dual Pentium EISA/PCI board.  It is the one
that I'm sending this message from.  I've also got some 486 motherboards
which have PCI and VLB.  I got rid of my EISA only 486 board.

I was looking at the pci.ids stuff, and haven't figured out how to modify
the entry for the Intel 82375EB to make it a PCI to EISA bridge and have
it discovered correctly in /proc/pci.

Let me know if there is anything I can do to help.

Thanks,
	Dennis Boylan
	dennis@lan.com
On Thu, Jan 17, 2002 at 01:54:56AM -0500, Eric S. Raymond wrote:
> Does anything in /proc or elswhere reliably register the presence of EISA?  
> 
> Failing that, have any motherboards existed that had both PCI and EISA slots?
> 
> (Yes, I have RTFD.  That's why I'm asking.)
> -- 
> 		<a href="http://www.tuxedo.org/~esr/">Eric S. Raymond</a>
> 
> Certainly one of the chief guarantees of freedom under any government,
> no matter how popular and respected, is the right of the citizens to
> keep and bear arms.  [...] the right of the citizens to bear arms is
> just one guarantee against arbitrary government and one more safeguard
> against a tyranny which now appears remote in America, but which
> historically has proved to be always possible.
>         -- Hubert H. Humphrey, 1960
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/

Re: Calling EISA experts

[Jeremy Jackson]

Eric S. Raymond wrote:

>Does anything in /proc or elswhere reliably register the presence of EISA?  
>
>Failing that, have any motherboards existed that had both PCI and EISA slots?
>
>(Yes, I have RTFD.  That's why I'm asking.)
>
I own a Compaq Proliant thus endowed.  I vaguely remember reading about 
certain configuration registers present on all EISA systems.

Re: Calling EISA experts

[Paul Gortmaker]

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;

Re: Calling EISA experts

[Jeff Garzik]

Paul Gortmaker wrote:
> 
> 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? ....

Actually, "lsescd" should list the EISA (and ISAPNP) configuration data,
which includes EISA id, etc.

	Jeff



-- 
Jeff Garzik      | Alternate titles for LOTR:
Building 1024    | Fast Times at Uruk-Hai
MandrakeSoft     | The Took, the Elf, His Daughter and Her Lover
                 | Samwise Gamgee: International Hobbit of Mystery

Re: Calling EISA experts

[Eric S. Raymond]

Jeff Garzik <jgarzik@mandrakesoft.com>:
> > 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? ....
> 
> Actually, "lsescd" should list the EISA (and ISAPNP) configuration data,
> which includes EISA id, etc.

I do not find this command on my RH7.2 system.  Can you tell me more about it?

I like the /proc/ioports approach and agree that /proc/bus/eisa/ seems like
overkill at this late date.
-- 
		<a href="http://www.tuxedo.org/~esr/">Eric S. Raymond</a>

He who joyfully marches to music in rank and file has already earned my
contempt.  He has been given a large brain by mistake, since for him the
spinal cord would fully suffice.
	-- Albert Einstein

Re: Calling EISA experts

[William Stearns]

Good day, Eric,

On Tue, 22 Jan 2002, Eric S. Raymond wrote:

> Jeff Garzik <jgarzik@mandrakesoft.com>:
> > > 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? ....
> > 
> > Actually, "lsescd" should list the EISA (and ISAPNP) configuration data,
> > which includes EISA id, etc.
> 
> I do not find this command on my RH7.2 system.  Can you tell me more about it?
> 
> I like the /proc/ioports approach and agree that /proc/bus/eisa/ seems like
> overkill at this late date.

	http://www.uwsg.iu.edu/hypermail/linux/kernel/0107.1/0052.html
	http://home.t-online.de/home/gunther.mayer/lsescd-0.10.tar.bz2 
	Cheers,
	- Bill

---------------------------------------------------------------------------
        "Anyone can be a critic, its rather harder and much more
valuable to be a critic that actually has positive impacts on what you
criticize"
        -- Alan Cox <alan@lxorguk.ukuu.org.uk>
--------------------------------------------------------------------------
William Stearns (wstearns@pobox.com).  Mason, Buildkernel, named2hosts, 
and ipfwadm2ipchains are at:                http://www.pobox.com/~wstearns
LinuxMonth; articles for Linux Enthusiasts! http://www.linuxmonth.com
--------------------------------------------------------------------------

Re: Calling EISA experts

[Eric S. Raymond]

Paul Gortmaker <p_gortmaker@yahoo.com>:
> 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. 

Yup.  This is the first, and so far the only, C-level kernel patch that
I've added to the CML2 kit.
-- 
		<a href="http://www.tuxedo.org/~esr/">Eric S. Raymond</a>

Let us hope our weapons are never needed --but do not forget what 
the common people knew when they demanded the Bill of Rights: An 
armed citizenry is the first defense, the best defense, and the 
final defense against tyranny.
   If guns are outlawed, only the government will have guns. Only 
the police, the secret police, the military, the hired servants of 
our rulers.  Only the government -- and a few outlaws.  I intend to 
be among the outlaws.
        -- Edward Abbey, "Abbey's Road", 1979

Re: Calling EISA experts

[Dave Jones]

On Tue, Jan 22, 2002 at 01:57:14PM -0500, Eric S. Raymond wrote:
 > Yup.  This is the first, and so far the only, C-level kernel patch that
 > I've added to the CML2 kit.

 How about just forwarding that bit along to Linus instead ?
 Given how small and non-intrusive it is, inclusion in 2.4
 isn't such a bad idea either.

 This way, at least when your magical autoconfigurator is
 finished, there's a higher chance that the patches it relies
 on are in everyday use.

-- 
| Dave Jones.        http://www.codemonkey.org.uk
| SuSE Labs