From owner-freebsd-current@FreeBSD.ORG  Mon Jun 14 08:06:55 2004
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP
	id 9149E16A4D0; Mon, 14 Jun 2004 08:06:55 +0000 (GMT)
Received: from hetzner.co.za (lfw.hetzner.co.za [196.7.18.226])
	by mx1.FreeBSD.org (Postfix) with ESMTP
	id BF4AC43D1D; Mon, 14 Jun 2004 08:06:54 +0000 (GMT)
	(envelope-from ianf@hetzner.co.za)
Received: from localhost ([127.0.0.1])
	by hetzner.co.za with esmtp (Exim 3.36 #1)
	id 1BZmUW-0005eX-00; Mon, 14 Jun 2004 10:06:52 +0200
To: Stefan =?iso-8859-1?Q?E=DFer?= <se@FreeBSD.org>
From: Ian FREISLICH <if@hetzner.co.za>
In-Reply-To: Message from Stefan =?iso-8859-1?Q?E=DFer?= <se@FreeBSD.org> 
	<20040611194328.GA4945@StefanEsser.FreeBSD.org> 
Date: Mon, 14 Jun 2004 10:06:52 +0200
Sender: ianf@hetzner.co.za
Message-Id: <E1BZmUW-0005eX-00@hetzner.co.za>
cc: current@freebsd.org
Subject: Re: Interrupt storm detection 
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 14 Jun 2004 08:06:55 -0000

> On 2004-06-11 16:01 +0200, Ian FREISLICH <if@hetzner.co.za> wrote:
> 
> Hmmm, maybe I'm missing something obvious, but I thought that polling 
> was more efficient than the silly one-byte-per-interrupt mode that is
> causing the interrupt storm detection to slow down the parallel port
> (and it was more efficient before!).

How do you turn polling on and does the driver support polling?

> And then, there are ECP and EPP modes (should be enabled in the BIOS
> setup) which even go as far as to allow DMA to the parallel port ...
> 
> Just try
> 
> 	lptcontrol -p
> 
> for polled mode on /dev/lpt0 (or use -d /dev/lptX), or 
> 
> 	lptcontrol -e

[brane-dead] ~ # lptcontrol -p
lptcontrol: open: Device busy
[brane-dead] ~ # lptcontrol -e
lptcontrol: open: Device busy
[brane-dead] ~ # lpc down all
lp:
        printer and queuing disabled
        status message is now: printing disabled
[brane-dead] ~ # lptcontrol -e
lptcontrol: open: Device busy
[brane-dead] ~ # killall lpd
[brane-dead] ~ # lptcontrol -e
lptcontrol: open: Device busy
[brane-dead] ~ # lptcontrol -p
lptcontrol: open: Device busy

:/ ?

> for extendend mode (may need to have an ISA interrupt assigned to the
> printer port in the BIOS, for best results ;-)

The port is set as ECP/EPP in the BIOS with an IRQ assigned to it.

ppc0: <Parallel port> at port 0x378-0x37f irq 7 on isa0
ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode
ppc0: FIFO with 16/16/16 bytes threshold
ppbus0: <Parallel port bus> on ppc0
ppbus0: IEEE1284 device found /NIBBLE/PS2/ECP

And it seems to plug and play:

Probing for PnP devices on ppbus0:
ppbus0: <Lexmark International Lexmark Optra E312> PRINTER PCL 6 Emulation, PostScript Level 2 Emulation, NPAP, PJL
plip0: <PLIP network interface> on ppbus0
lpt0: <Printer> on ppbus0
lpt0: Interrupt-driven port
ppi0: <Parallel I/O> on ppbus0

Ian

--
Ian Freislich