From owner-freebsd-hackers  Thu Dec 26 09:37:13 1996
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.4/8.8.4) id JAA28344
          for hackers-outgoing; Thu, 26 Dec 1996 09:37:13 -0800 (PST)
Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19])
          by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id JAA28339
          for <freebsd-hackers@freebsd.org>; Thu, 26 Dec 1996 09:37:10 -0800 (PST)
Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.3/8.6.9) id EAA24737; Fri, 27 Dec 1996 04:35:19 +1100
Date: Fri, 27 Dec 1996 04:35:19 +1100
From: Bruce Evans <bde@zeta.org.au>
Message-Id: <199612261735.EAA24737@godzilla.zeta.org.au>
To: freebsd-hackers@freebsd.org, j@uriah.heep.sax.de
Subject: Re: Help with sb
Cc: peter@clari.net.au
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

>> Does it take a kernel recompile to move it?
>
>No, you can change it by booting with -c.

`lptcontrol -p' can be used to stop the printer generating interrupts,
but there is no way to connect the sb or lpt to the interrupt if it
isn't already - the first one configured grabs the interrupt vector
and the error for the other not being able to allocate the vector is
silently ignored.

>> jumper anything. What if I just set the printer driver into polled mode?
>> (actually I think that's how I had it)
>
>It will burn many CPU cycles in tight loops then.

The driver was so braindamaged that this was required for many printers
with working interrupts anyway.  Joerg improved the driver, but it's not
clear if the polling code is still useful since no one complains about
working code :-).

Bruce