From owner-freebsd-hackers  Thu Aug  7 21:40:32 1997
Return-Path: <owner-freebsd-hackers>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.5/8.8.5) id VAA21332
          for hackers-outgoing; Thu, 7 Aug 1997 21:40:32 -0700 (PDT)
Received: from misery.sdf.com (misery.sdf.com [204.244.210.193])
          by hub.freebsd.org (8.8.5/8.8.5) with SMTP id VAA21096
          for <hackers@freebsd.org>; Thu, 7 Aug 1997 21:35:44 -0700 (PDT)
Received: from tom by misery.sdf.com with smtp (Exim 1.62 #1)
	id 0wwg21-00003A-00; Thu, 7 Aug 1997 20:48:05 -0700
Date: Thu, 7 Aug 1997 20:48:05 -0700 (PDT)
From: Tom Samplonius <tom@sdf.com>
To: John-Mark Gurney <gurney_j@resnet.uoregon.edu>
cc: hackers@freebsd.org
Subject: Re: AUTO_EOI_* ?
In-Reply-To: <19970807194336.27057@hydrogen.nike.efn.org>
Message-ID: <Pine.BSF.3.95q.970807204645.187A-100000@misery.sdf.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk


On Thu, 7 Aug 1997, John-Mark Gurney wrote:

> Tom Samplonius scribbled this message on Aug 7:
> > 
> >   It seems that the AUTO_EOI_* options might speed interupt handling.
> > I've tried them on some motherboards, and they seem to work ok.  Are these
> > options recommended?  I've seen some talk that these options should be
> > eliminated?
> 
> well... don't make AUTO_EOI_2 enabled by default... I have a motherboard
> that dies when this option is enabled... though I haven't found one yet
> when AUTO_EOI_1 is enabled... the comments say that AUTO_EOI_1 will
> break suspend/resume on some notebooks...  so it looks like we can't
> enable both by default...

  Every motherboard I've tried it on works fine, even an old EISA 486
motherboard, but all the boards I tested were made by ASUS...

> -- 
>   John-Mark Gurney                          Modem/FAX: +1 541 683 6954
>   Cu Networking
> 
>   Live in Peace, destroy Micro$oft, support free software, run FreeBSD
> 
> 

Tom