Date: Tue, 15 Jun 1999 18:22:07 CDT From: Kent Vander Velden <graphix@iastate.edu> To: freebsd-current@freebsd.org Subject: lpbb Message-ID: <199906152322.SAA31703@isua1.iastate.edu>
next in thread | raw e-mail | index | archive | help
What does one have to do to get lpbb working on -current? I think these
are the relevant portions of the config file:
controller smbus0
device smb0 at smbus?
controller iicbus0
controller iicbb0
device ic0 at iicbus?
device iic0 at iicbus?
device iicsmb0 at iicbus?
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 ppc0 at isa? port? irq 7
There is no mention of the iic system in dmesg but lpt and ppi show up:
ppc: parallel port found at 0x378
ppc0: SMC registers CR1=0xbe CR4=0x0 SPP
ppc0 at port 0x378-0x37f irq 7 on isa0
ppc0: SMC FDC37C665GT chipset (PS2/NIBBLE) in COMPATIBLE mode
lpt0: <generic printer> on ppbus 0
lpt0: Interrupt-driven port
ppi0: <generic parallel i/o> on ppbus 0
The ppi device seems to work fine at least using a logic probe I can see
the values changing on the bus as new values are sent to the device.
One other related question: I used to be able to do the following to
send test data onto the parallel port:
cat /dev/kernel > /dev/lpt0
but I after a few second delay the following message comes back:
/dev/lpt0: Device busy.
and this is after killing lpd. Is this not allowed any longer with the
introduction of the new parallel port bus system?
Thanks.
---
Kent Vander Velden
kent@iastate.edu
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199906152322.SAA31703>