Re: lpt0
On Tue, Feb 16, 1999 at 10:16:05PM -0700, Warner Losh wrote: > >In message <199902141331.faa27...@hub.freebsd.org> "Jonathan M. Bresler" >writes: >: how much information about this should be included in >: /usr/src/UPDATING? the entry there talks about the change but does >: not provide enough information to successfully upgrade (ppc0 is not >: mentioned, nor does it provide a pointer to where to go for more >: information.) ;( > >I'm about to commit a change to UPDATING to point to this URL and man >page. I'm just now catching up from being gone for a week. Thanks, I've update the web page since you refer to it in UPDATING. > >Warner > -- nso...@teaser.fr / nso...@freebsd.org FreeBSD - Turning PCs into workstations - http://www.FreeBSD.org To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: lpt0
In message <199902141331.faa27...@hub.freebsd.org> "Jonathan M. Bresler" writes: : how much information about this should be included in : /usr/src/UPDATING? the entry there talks about the change but does : not provide enough information to successfully upgrade (ppc0 is not : mentioned, nor does it provide a pointer to where to go for more : information.) ;( I'm about to commit a change to UPDATING to point to this URL and man page. I'm just now catching up from being gone for a week. Warner To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: lpt0
On Sun, 14 Feb 1999, Jordan K. Hubbard wrote: > > On Sat, Feb 13, 1999 at 07:36:37PM -0800, Jordan K. Hubbard wrote: > > > > > >FWIW, I would also like to see this happen. > > > > What's the deadline? I did it for -current this day. I'm waiting for > > some feedback before the 3.1 replica. > > Actually, subsequent discussions with Dag-Erling have sort of shown > this to have been rather too ambitious of me and now I've major second > thoughts. :( My initial comment was based on my MISperception that the old lpt driver had been removed from RELENG_3 when, in fact, it had only been removed from -current. Realizing my blunder, I retract the suggestion. -john To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: lpt0
On Sun, Feb 14, 1999 at 11:58:48AM -0800, Jordan K. Hubbard wrote: > >> The alternative is to just update GENERIC, LINT et al to use ppbus >> instead of the old lpt driver, and throw in a warning in the probe >> messages in src/sys/i386/lpt.c telling people to move to ppbus. It >> should be pretty safe. > >Now that I could live with. Are you up for that? Not better than the actual state, since I renamed nlpt to lpt today in -current, as wished by most of you. So, we should let it as is (nlpt+lpt) in 3.1. Anyway, 3.1 is stable and what is more stable than the old-lpt? > >- Jordan > -- nso...@teaser.fr / nso...@freebsd.org FreeBSD - Turning PCs into workstations - http://www.FreeBSD.org To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: lpt0
> The alternative is to just update GENERIC, LINT et al to use ppbus > instead of the old lpt driver, and throw in a warning in the probe > messages in src/sys/i386/lpt.c telling people to move to ppbus. It > should be pretty safe. Now that I could live with. Are you up for that? - Jordan To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: lpt0
"Jordan K. Hubbard" writes: > Actually, subsequent discussions with Dag-Erling have sort of shown > this to have been rather too ambitious of me and now I've major second > thoughts. :( I *can* do it if you want. It's pretty straightforward, it's just that there are a lot of things to do, and the short deadline means I'll have to handle pc98 and src/UPDATING myself rather than rely on Kato and Warner to do it themselves. It'll take me an hour or two to go through every file that needs to be changed, and two or three hours more to test things and fix loose ends. The alternative is to just update GENERIC, LINT et al to use ppbus instead of the old lpt driver, and throw in a warning in the probe messages in src/sys/i386/lpt.c telling people to move to ppbus. It should be pretty safe. DES -- Dag-Erling Smorgrav - d...@flood.ping.uio.no To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: lpt0
On Sun, Feb 14, 1999 at 11:43:36AM -0800, Jordan K. Hubbard wrote: > >> Ok, we should keep lpt, but I'll need to sync ppbus before the release >> just to fix some bugs discovered by all these new testers. > >OK, better do it soon then! :) > >> BTW, I really don't know when 3.1 will be released. > >The tag goes down tonite (in approximately 7 hours) and the release is >tomorrow afternoon. Arg! I'll do the best and most wise. > >- Jordan > -- nso...@teaser.fr / nso...@freebsd.org FreeBSD - Turning PCs into workstations - http://www.FreeBSD.org To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: lpt0
> Ok, we should keep lpt, but I'll need to sync ppbus before the release > just to fix some bugs discovered by all these new testers. OK, better do it soon then! :) > BTW, I really don't know when 3.1 will be released. The tag goes down tonite (in approximately 7 hours) and the release is tomorrow afternoon. - Jordan To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: lpt0
On Sun, Feb 14, 1999 at 09:58:39AM -0800, Jordan K. Hubbard wrote: > >> On Sat, Feb 13, 1999 at 07:36:37PM -0800, Jordan K. Hubbard wrote: >> > >> >FWIW, I would also like to see this happen. >> >> What's the deadline? I did it for -current this day. I'm waiting for >> some feedback before the 3.1 replica. > >Actually, subsequent discussions with Dag-Erling have sort of shown >this to have been rather too ambitious of me and now I've major second >thoughts. :( > >I think the number of changes involved in making the cut-over are just >too likely to hang us at the last minute, and that's nothing any of us >want. Any there any last cosmetic tie-ups of a less scary nature, or >are we good to go as-is in the 3.0 branch? Ok, we should keep lpt, but I'll need to sync ppbus before the release just to fix some bugs discovered by all these new testers. BTW, I really don't know when 3.1 will be released. > >- Jordan > >To Unsubscribe: send mail to majord...@freebsd.org >with "unsubscribe freebsd-current" in the body of the message > -- nso...@teaser.fr / nso...@freebsd.org FreeBSD - Turning PCs into workstations - http://www.FreeBSD.org To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: lpt0
On Sun, 14 Feb 1999, Jordan K. Hubbard wrote: > > On Sat, Feb 13, 1999 at 07:36:37PM -0800, Jordan K. Hubbard wrote: > > > > > >FWIW, I would also like to see this happen. > > > > What's the deadline? I did it for -current this day. I'm waiting for > > some feedback before the 3.1 replica. > > Actually, subsequent discussions with Dag-Erling have sort of shown > this to have been rather too ambitious of me and now I've major second > thoughts. :( > > I think the number of changes involved in making the cut-over are just > too likely to hang us at the last minute, and that's nothing any of us > want. Any there any last cosmetic tie-ups of a less scary nature, or > are we good to go as-is in the 3.0 branch? ICMP_BANDLIM by default in GENERIC? And maybe perhaps a note that there is a much improved parallel port driver that everyone should use? Putting nlpt, ppbus, ppc etc in there should be fine, considering nlpt wouldn't collide with anyone trying to configure an old kernel... > > - Jordan > > To Unsubscribe: send mail to majord...@freebsd.org > with "unsubscribe freebsd-current" in the body of the message > Brian Feldman_ __ ___ ___ ___ gr...@unixhelp.org _ __ ___ | _ ) __| \ http://www.freebsd.org/ _ __ ___ | _ \__ \ |) | FreeBSD: The Power to Serve! _ __ ___ _ |___/___/___/ To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: lpt0
> On Sat, Feb 13, 1999 at 07:36:37PM -0800, Jordan K. Hubbard wrote: > > > >FWIW, I would also like to see this happen. > > What's the deadline? I did it for -current this day. I'm waiting for > some feedback before the 3.1 replica. Actually, subsequent discussions with Dag-Erling have sort of shown this to have been rather too ambitious of me and now I've major second thoughts. :( I think the number of changes involved in making the cut-over are just too likely to hang us at the last minute, and that's nothing any of us want. Any there any last cosmetic tie-ups of a less scary nature, or are we good to go as-is in the 3.0 branch? - Jordan To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: lpt0
On Sat, Feb 13, 1999 at 07:36:37PM -0800, Jordan K. Hubbard wrote: > >FWIW, I would also like to see this happen. What's the deadline? I did it for -current this day. I'm waiting for some feedback before the 3.1 replica. > >> On 13 Feb 1999, Dag-Erling Smorgrav wrote: >> >> > Nicolas Souchu writes: >> > > controller ppbus0 # The ppbus system >> > > device nlpt0 at ppbus? # The printer driver >> > >> > OBTW, when are you planning to rename nlpt0 to lpt0? >> >> Hopefully before 3.1 goes out...it would be a bummer to have one >> release with a different name than the rest; it confuses >> documentation that tries to cover multiple versions. >> >> -john >> I agree. -- nso...@teaser.fr / nso...@freebsd.org FreeBSD - Turning PCs into workstations - http://www.FreeBSD.org To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: lpt0
On Sun, Feb 14, 1999 at 05:31:08AM -0800, Jonathan M. Bresler wrote: > >> Date: Sat, 13 Feb 1999 19:17:14 +0100 >> From: Nicolas Souchu >> >> You need: >> >> controller ppbus0 # The ppbus system >> device nlpt0 at ppbus? # The printer driver >> >> And finally the parallel port chipset interface, >> >> controller ppc0at isa? port? tty irq 7 drq 3 >> >> See ppbus(4) and/or http://www.freebsd.org/~nsouch/ppbus.html for more info >> about the ppbus architecture. > > how much information about this should be included in > /usr/src/UPDATING? the entry there talks about the change but does > not provide enough information to successfully upgrade (ppc0 is not > mentioned, nor does it provide a pointer to where to go for more > information.) ;( Sorry, your efforts are lost. I've just renamed nlpt to lpt. But I've properly updated lpt.4, I think. You may just add, the minimal configuration and point to the manpage for further details. Something like: >>> Now the lpt driver, previously named nlpt in the ppbus system not to collide with the original isa/lpt.c functions, shall be declared with: controller ppbus0 device lpt0 at ppbus? controller ppc0 at isa? port "IO_LPT1" tty irq 7 The ppc(4) driver is the ISA parallel port interface driver. The ppbus(4) controller stands for the whole ppbus system code. And finally, you have lpt(4). <<< > >jmb > -- nso...@teaser.fr / nso...@freebsd.org FreeBSD - Turning PCs into workstations - http://www.FreeBSD.org To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: lpt0
> Date: Sat, 13 Feb 1999 19:17:14 +0100 > From: Nicolas Souchu > > You need: > > controllerppbus0 # The ppbus system > devicenlpt0 at ppbus? # The printer driver > > And finally the parallel port chipset interface, > > controllerppc0at isa? port? tty irq 7 drq 3 > > See ppbus(4) and/or http://www.freebsd.org/~nsouch/ppbus.html for more info > about the ppbus architecture. how much information about this should be included in /usr/src/UPDATING? the entry there talks about the change but does not provide enough information to successfully upgrade (ppc0 is not mentioned, nor does it provide a pointer to where to go for more information.) ;( jmb To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: lpt0 Not Found
On Sat, 13 Feb 1999, Thomas Dean wrote: > I changed to the new nlpt. No luck. > > It appears that the parallel port is not found. > > I am running SMP-current, as of this afternoon. From uname -a: > ... FreeBSD 4.0-CURRENT #0: Sat Feb 13 16:11:56 PST 1999 > > In my config, I changed to include ppbus0, nlpt0, and ppc0, exactly as > in LINT: > > > # Parallel-Port Bus > # nlpt Parallel Printer > controller ppbus0 > # devicelpt0at isa? port? tty irq 7 vector lptintr > controller ppc0at isa? disable port ? tty irq 7 > device nlpt0 at ppbus? > Take out the 'disable' from the ppc0 line. Thats got me a few times too :-). -- Doug Rabson Mail: d...@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: lpt0
On Sat, Feb 13, 1999 at 08:04:12PM +0100, Dag-Erling Smorgrav wrote: > >Nicolas Souchu writes: >> controller ppbus0 # The ppbus system >> device nlpt0 at ppbus? # The printer driver > >OBTW, when are you planning to rename nlpt0 to lpt0? Today. > >DES >-- >Dag-Erling Smorgrav - d...@flood.ping.uio.no > -- nso...@teaser.fr / nso...@freebsd.org FreeBSD - Turning PCs into workstations - http://www.FreeBSD.org To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: lpt0
FWIW, I would also like to see this happen. > On 13 Feb 1999, Dag-Erling Smorgrav wrote: > > > Nicolas Souchu writes: > > > controllerppbus0 # The ppbus system > > > devicenlpt0 at ppbus? # The printer driver > > > > OBTW, when are you planning to rename nlpt0 to lpt0? > > Hopefully before 3.1 goes out...it would be a bummer to have one > release with a different name than the rest; it confuses > documentation that tries to cover multiple versions. > > -john > > > > To Unsubscribe: send mail to majord...@freebsd.org > with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: lpt0 Not Found -- FOUND IT
I found my problem. I did a cut-paste from LINT. # Parallel-Port Bus # nlpt Parallel Printer controller ppbus0 # devicelpt0at isa? port? tty irq 7 vector lptintr device nlpt0 at ppbus? controller ppc0at isa? disable port ? tty irq 7 ^^^ | Should LINT be changed? Most machines using this will have printers. tomdean To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
lpt0 Not Found
I changed to the new nlpt. No luck. It appears that the parallel port is not found. I am running SMP-current, as of this afternoon. From uname -a: ... FreeBSD 4.0-CURRENT #0: Sat Feb 13 16:11:56 PST 1999 In my config, I changed to include ppbus0, nlpt0, and ppc0, exactly as in LINT: # Parallel-Port Bus # nlpt Parallel Printer controller ppbus0 # devicelpt0at isa? port? tty irq 7 vector lptintr controller ppc0at isa? disable port ? tty irq 7 device nlpt0 at ppbus? tomdean == dmesg == Copyright (c) 1992-1999 FreeBSD Inc. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 4.0-CURRENT #0: Sat Feb 13 16:11:56 PST 1999 tomd...@celebris:/usr/src/sys/compile/CELEBRIS-SMP Timecounter "i8254" frequency 1193025 Hz CPU: Pentium/P54C (586-class CPU) Origin = "GenuineIntel" Id = 0x525 Stepping=5 Features=0x3bf real memory = 100663296 (98304K bytes) avail memory = 95055872 (92828K bytes) Programming 16 pins in IOAPIC #0 FreeBSD/SMP: Multiprocessor motherboard cpu0 (BSP): apic id: 0, version: 0x00030010, at 0xfee0 cpu1 (AP): apic id: 1, version: 0x00030010, at 0xfee0 io0 (APIC): apic id: 2, version: 0x000f0011, at 0xfec0 Preloaded elf kernel "kernel" at 0xf02b. Probing for devices on PCI bus 0: chip0: rev 0x11 on pci0.0.0 ncr0: rev 0x02 int a irq 11 on pci0.1.0 chip1: rev 0x88 on pci0.2.0 vga0: rev 0x01 int a irq 9 on pci0.6.0 de0: rev 0x11 int a irq 10 on pci0.8.0 de0: DEC DE450-CA 21041 [10Mb/s] pass 1.1 de0: address 00:00:f8:02:76:db Probing for devices on the ISA bus: sc0 on isa sc0: VGA color <16 virtual consoles, flags=0x0> atkbdc0 at 0x60-0x6f on motherboard atkbd0 irq 1 on isa psm0 irq 12 on isa psm0: model Generic PS/2 mouse, device ID 0 sio0 at 0x3f8-0x3ff irq 4 on isa sio0: type 16550A sio1 at 0x2f8-0x2ff irq 3 on isa sio1: type 16550A fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa fdc0: NEC 72065B fdc0: FIFO enabled, 8 bytes threshold fd0: 1.44MB 3.5in fd0: 1.44MB 3.5in vga0 at 0x3b0-0x3df maddr 0xa msize 131072 on isa npx0 on motherboard npx0: INT 16 interface stray irq 7 Intel Pentium detected, installing workaround for F00F bug APIC_IO: Testing 8254 interrupt delivery APIC_IO: routing 8254 via pin 2 de0 XXX: driver didn't set ifq_maxlen lo0 XXX: driver didn't set ifq_maxlen Waiting 5 seconds for SCSI devices to settle (probe3:ncr0:0:3:0): COMMAND FAILED (6 ff) @0xf09dc000. (probe2:ncr0:0:2:0): COMMAND FAILED (6 ff) @0xf09dc600. (probe1:ncr0:0:1:0): COMMAND FAILED (6 ff) @0xf09dcc00. (probe0:ncr0:0:0:0): COMMAND FAILED (6 ff) @0xf09ba200. SMP: AP CPU #1 Launched! da0 at ncr0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-2 device da0: 10.0MB/s transfers (10.0MHz, offset 8) da0: 1042MB (2134305 512 byte sectors: 255H 63S/T 132C) da2 at ncr0 bus 0 target 2 lun 0 da2: Fixed Direct Access SCSI-2 device da2: 10.0MB/s transfers (10.0MHz, offset 8), Tagged Queueing Enabled da2: 1029MB (2109376 512 byte sectors: 255H 63S/T 131C) da1 at ncr0 bus 0 target 1 lun 0 da1: Fixed Direct Access SCSI-2 device da1: 10.0MB/s transfers (10.0MHz, offset 8), Tagged Queueing Enabled da1: 3090MB (6328861 512 byte sectors: 255H 63S/T 393C) changing root device to da1s1a cd0 at ncr0 bus 0 target 5 lun 0 cd0: Removable CD-ROM SCSI-2 device cd0: 4.237MB/s transfers (4.237MHz, offset 8) cd0: Attempt to query device size failed: NOT READY, Medium not present (da1:ncr0:0:1:0): tagged openings now 8 To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: lpt0
On 13 Feb 1999, Dag-Erling Smorgrav wrote: > Nicolas Souchu writes: > > controller ppbus0 # The ppbus system > > device nlpt0 at ppbus? # The printer driver > > OBTW, when are you planning to rename nlpt0 to lpt0? Hopefully before 3.1 goes out...it would be a bummer to have one release with a different name than the rest; it confuses documentation that tries to cover multiple versions. -john To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: lpt0
Nicolas Souchu writes: > controllerppbus0 # The ppbus system > devicenlpt0 at ppbus? # The printer driver OBTW, when are you planning to rename nlpt0 to lpt0? DES -- Dag-Erling Smorgrav - d...@flood.ping.uio.no To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: lpt0
On Sat, 13 Feb 1999, Chuck Robey wrote: > Recently I noticed that lpt0 has been replaced by the ppbus stuff, in > LINT. The problem is, I can't find any example as to how to set it up > for a plain, vanilla printer ppbus has so many more capabilities > than lp, I think it's embarrassed about it's dowdy origins. I don't > know what controller to use (ppbus0 or maybe ppc0?) and the old device, > lpt0, doesn't even exist in LINT anymore. > > I tried picking up the lines for ppbus0 and nlpt, which I guessed might > be right, from LINT, and dropping them into my config file. They > compile fine, but nothing is probed (my dmesg shows no printer) and I > can't print. > > What's the right setup for a plain, ordinary IRQ 7 printer port? > Please, don't answer if you're going to talk about connecting some > parallel interfaced thing like a zip drive. I can't seem to find any > docs on this, nor any mail messages (nothing in UPDATING either). There > is much discussion about things like zip drive connecting, though ... The following works great for me: controller ppbus0 device nlpt0 at ppbus? device plip0 at ppbus? device ppi0at ppbus? device pps0at ppbus? controller ppc0at isa? port ? tty irq 7 > > +--- > Chuck Robey | Interests include any kind of voice or data > chu...@glue.umd.edu | communications topic, C programming, and Unix. > 213 Lakeside Drive Apt T-1 | > Greenbelt, MD 20770 | I run picnic (FreeBSD-current) > (301) 220-2114 | and jaunt (Solaris7). > +--- > > > > > > To Unsubscribe: send mail to majord...@freebsd.org > with "unsubscribe freebsd-current" in the body of the message > Brian Feldman_ __ ___ ___ ___ gr...@unixhelp.org _ __ ___ | _ ) __| \ http://www.freebsd.org/ _ __ ___ | _ \__ \ |) | FreeBSD: The Power to Serve! _ __ ___ _ |___/___/___/ To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: lpt0
You need: controller ppbus0 # The ppbus system device nlpt0 at ppbus? # The printer driver And finally the parallel port chipset interface, controller ppc0at isa? port? tty irq 7 drq 3 See ppbus(4) and/or http://www.freebsd.org/~nsouch/ppbus.html for more info about the ppbus architecture. On Sat, Feb 13, 1999 at 01:11:25PM -0500, Chuck Robey wrote: > >Recently I noticed that lpt0 has been replaced by the ppbus stuff, in >LINT. The problem is, I can't find any example as to how to set it up >for a plain, vanilla printer ppbus has so many more capabilities >than lp, I think it's embarrassed about it's dowdy origins. I don't >know what controller to use (ppbus0 or maybe ppc0?) and the old device, >lpt0, doesn't even exist in LINT anymore. > >I tried picking up the lines for ppbus0 and nlpt, which I guessed might >be right, from LINT, and dropping them into my config file. They >compile fine, but nothing is probed (my dmesg shows no printer) and I >can't print. > >What's the right setup for a plain, ordinary IRQ 7 printer port? >Please, don't answer if you're going to talk about connecting some >parallel interfaced thing like a zip drive. I can't seem to find any >docs on this, nor any mail messages (nothing in UPDATING either). There >is much discussion about things like zip drive connecting, though ... > >+--- >Chuck Robey | Interests include any kind of voice or data >chu...@glue.umd.edu | communications topic, C programming, and Unix. >213 Lakeside Drive Apt T-1 | >Greenbelt, MD 20770 | I run picnic (FreeBSD-current) >(301) 220-2114 | and jaunt (Solaris7). >+--- > > > > > >To Unsubscribe: send mail to majord...@freebsd.org >with "unsubscribe freebsd-current" in the body of the message > -- nso...@teaser.fr / nso...@freebsd.org FreeBSD - Turning PCs into workstations - http://www.FreeBSD.org To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
lpt0
Recently I noticed that lpt0 has been replaced by the ppbus stuff, in LINT. The problem is, I can't find any example as to how to set it up for a plain, vanilla printer ppbus has so many more capabilities than lp, I think it's embarrassed about it's dowdy origins. I don't know what controller to use (ppbus0 or maybe ppc0?) and the old device, lpt0, doesn't even exist in LINT anymore. I tried picking up the lines for ppbus0 and nlpt, which I guessed might be right, from LINT, and dropping them into my config file. They compile fine, but nothing is probed (my dmesg shows no printer) and I can't print. What's the right setup for a plain, ordinary IRQ 7 printer port? Please, don't answer if you're going to talk about connecting some parallel interfaced thing like a zip drive. I can't seem to find any docs on this, nor any mail messages (nothing in UPDATING either). There is much discussion about things like zip drive connecting, though ... +--- Chuck Robey | Interests include any kind of voice or data chu...@glue.umd.edu | communications topic, C programming, and Unix. 213 Lakeside Drive Apt T-1 | Greenbelt, MD 20770 | I run picnic (FreeBSD-current) (301) 220-2114 | and jaunt (Solaris7). +--- To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
