From owner-freebsd-bugs@FreeBSD.ORG  Sun Apr 17 23:07:20 2005
Return-Path: <owner-freebsd-bugs@FreeBSD.ORG>
Delivered-To: freebsd-bugs@hub.freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP
	id 4107416A4CE; Sun, 17 Apr 2005 23:07:20 +0000 (GMT)
Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21])
	by mx1.FreeBSD.org (Postfix) with ESMTP
	id 1A02043D31; Sun, 17 Apr 2005 23:07:20 +0000 (GMT)
	(envelope-from iedowse@FreeBSD.org)
Received: from freefall.freebsd.org (iedowse@localhost [127.0.0.1])
	by freefall.freebsd.org (8.13.3/8.13.3) with ESMTP id j3HN7JRL072947;
	Sun, 17 Apr 2005 23:07:19 GMT
	(envelope-from iedowse@freefall.freebsd.org)
Received: (from iedowse@localhost)
	by freefall.freebsd.org (8.13.3/8.13.1/Submit) id j3HN7JRe072943;
	Sun, 17 Apr 2005 23:07:19 GMT
	(envelope-from iedowse)
Date: Sun, 17 Apr 2005 23:07:19 GMT
From: Ian Dowse <iedowse@FreeBSD.org>
Message-Id: <200504172307.j3HN7JRe072943@freefall.freebsd.org>
To: aa8vb@nc.rr.com, iedowse@FreeBSD.org, freebsd-bugs@FreeBSD.org
Subject: 
	Re: kern/26277: ppc driver doesn't work with port 0x3BC printer port
X-BeenThere: freebsd-bugs@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Bug reports <freebsd-bugs.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-bugs>,
	<mailto:freebsd-bugs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-bugs>
List-Post: <mailto:freebsd-bugs@freebsd.org>
List-Help: <mailto:freebsd-bugs-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-bugs>,
	<mailto:freebsd-bugs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sun, 17 Apr 2005 23:07:20 -0000

Synopsis: ppc driver doesn't work with port 0x3BC printer port

State-Changed-From-To: open->feedback
State-Changed-By: iedowse
State-Changed-When: Sun Apr 17 23:05:28 GMT 2005
State-Changed-Why: 

Does this still occur with more recent releases? It does sound like
a hardware conflict or misconfiguration rather than a driver bug
though.

http://www.freebsd.org/cgi/query-pr.cgi?pr=26277