Bug 14135

Summary:	lpt1 nolonger exists after 3.2-RELEASE
Product:	Documentation	Reporter:	Jin Guojun <jin>
Component:	Books & Articles	Assignee:	freebsd-doc (Nobody) <doc>
Status:	Closed FIXED
Severity:	Affects Only Me
Priority:	Normal
Version:	Latest
Hardware:	Any
OS:	Any

Description Jin Guojun 1999-10-05 00:50:00 UTC

	3.2-RELEASE or later FreeBSD will no longer configure the lpt1.

How-To-Repeat: 
these configuration I have used:
(1)
controller      ppbus0
controller      vpo0    at ppbus?
device          lpt0    at ppbus?
device          plip0   at ppbus?
device          ppi0    at ppbus?
device          pps0    at ppbus?
device          lpbb0   at ppbus?
device          lpt1   at ppbus?

or (2)

controller      ppbus0  
controller      vpo0    at ppbus?
device          lpt0    at ppbus?
device          plip0   at ppbus?
device          ppi0    at ppbus?
device          pps0    at ppbus?
device          lpbb0   at ppbus?
controller      ppbus1
device          lpt1   at ppbus?

Comment 1 iedowse freebsd_committer

2001-06-07 01:48:33 UTC

State Changed
From-To: open->feedback


Is this still a problem in more recent releases?

Comment 2 Mike Barcroft freebsd_committer

2001-07-21 03:00:54 UTC

State Changed
From-To: feedback->closed


Timeout; no response from originator.

Comment 3 Mike Barcroft freebsd_committer

2001-07-21 23:45:36 UTC

State Changed
From-To: closed->suspended


Added originator's response.  This one should be a pretty easy doc 
fix.  Awaiting fix and committer.

Comment 4 Mike Barcroft freebsd_committer

2001-07-21 23:52:30 UTC

Adding to Audit-Trail.

On Sat, Jul 21, 2001 at 03:17:12PM -0700, Jin Guojun wrote:
> mike@FreeBSD.org wrote:
> 
> > Synopsis: lpt1 nolonger exists after 3.2-RELEASE
> >
> > State-Changed-From-To: feedback->closed
> > State-Changed-By: mike
> > State-Changed-When: Fri Jul 20 19:00:54 PDT 2001
> > State-Changed-Why:
> >
> > Timeout; no response from originator.
> >
> > http://www.FreeBSD.org/cgi/query-pr.cgi?pr=14135
> 
> I think you have missed the replied message --
> 
> ------------------ Response Message ------------------
> 
> > In message <200106101944.f5AJiN905505@portnoy.lbl.gov>, Jin Guojun writes:
> > >.
> > >If another ISA parallel board is installed, this new board becomes port0 at
> > >0x3BC, and the onboard becomes port-1 at 0x378.
> >
> > Ok, then I can partially understand why it might fail, because the
> > IRQ will almost certainly be wrong. The default line in the config
> > file says to use IRQ 7 for lpt0, but normally IRQ 7 is used by the
> > 0x378 port.
> >
> > To start with, make sure that the two ports are using different IRQs;
> > I'd suggest IRQ 7 for the 0x378 one, and IRQ 5 for 0x3bc. Then comment
> > out the existing 'ppc0' line in the kernel config, and add these two:
> >
> >         device            ppc0    at isa? port IO_LPT3 irq 5
> >         device            ppc1    at isa? port IO_LPT1 irq 7
> 
> This works.
> 
> >
> >
> > In FreeBSD, the names IO_LPT1, IO_LPT2, IO_LPT3 correspond to the
> > addresses 0x378, 0x278, 0x3bc respectively. The BIOS will choose
> > the port names according to which of 0x3bc, 0x378, 0x278 are present,
> > in that order, so there is some room for confusion!
> >
> > It does seem that FreeBSD's probe code is less than ideal in this
> > case, but the BIOS does not provide any IRQ hints so it may be
> > difficult to fix.
> 
> Add above configuration information with explaination into ppc(4) manpage
> will help users to build custom kernel for this case. The irq 5 may vary from
> case to case for IO_LPT3 line.
> 
> Thanks,
>

Comment 5 Johan Karlsson freebsd_committer

2002-11-27 19:31:26 UTC

Responsible Changed
From-To: freebsd-bugs->freebsd-doc

Over to the doc people. 

We are now using device.hints(5) to do this kind of stuff. 
It should, IMO,  be documented in a general way in the handbook 
how to solve this kind of thing.

Comment 6 Peter Pentchev freebsd_committer

2004-09-13 14:49:19 UTC

State Changed
From-To: suspended->closed

I think the hints example at the top of the ppc(4) manual page and 
the Handbook's Section 12.5, "Device Hints", do a pretty good job of 
describing the current situation now, so this PR ought to be closed. 
Thanks for bringing it up in the first place!