Chuck Robey wrote:
>
> If IO is generic, then printing the type of printer it finds is
> meaningless, right? It's going to announce "generic" no matter what,
> then it should stay silent, right? Better to say nothing than to get it
> wrong every time, especially with the correct info sitting mer
On Sun, Feb 14, 1999 at 01:33:24PM -0500, Brian Feldman wrote:
>
>It says "generic" every time, whther or not there's a printer attached.
Yes, fun isn't it?
>lpt0: on ppbus 0
>lpt0: Interrupt-driven port
>should be
>lpt0: generic printer port on ppbus 0
>lpt0: Interrupt-driven port
You certainl
On Sun, Feb 14, 1999 at 01:16:11PM -0500, Chuck Robey wrote:
>> >ppc0 at 0x378 irq 7 drq 3 on isa
>> >ppc0: SMC FDC37C665GT chipset (ECP/PS2/NIBBLE) in COMPATIBLE mode
>> >ppc0: FIFO with 16/16/15 bytes threshold
>> >ppb0: IEEE1284 device found /NIBBLE/ECP
>> >Probing for PnP devices on ppbus0:
>>
> If IO is generic, then printing the type of printer it finds is
> meaningless, right? It's going to announce "generic" no matter what,
> then it should stay silent, right? Better to say nothing than to get it
> wrong every time, especially with the correct info sitting mere lines
> above, adver
It says "generic" every time, whther or not there's a printer attached.
lpt0: on ppbus 0
lpt0: Interrupt-driven port
should be
lpt0: generic printer port on ppbus 0
lpt0: Interrupt-driven port
Brian Feldman_ __ ___ ___ ___
gr...@unixhelp.org
On Sun, 14 Feb 1999, Nicolas Souchu wrote:
> >There are a couple of things that have happened that strike me as worthy
> >of comment. Here's my relevant dmesg part:
> >
> >ppc0 at 0x378 irq 7 drq 3 on isa
> >ppc0: SMC FDC37C665GT chipset (ECP/PS2/NIBBLE) in COMPATIBLE mode
> >ppc0: FIFO with 16/1
On Sun, Feb 14, 1999 at 12:48:56PM -0500, Chuck Robey wrote:
>> But there's at least FIFO+DMA support in the nlpt driver. Try 'lptcontrol -e'
>> with you BIOS configured to ECP. Recompile with the appropriate
>> drq on the 'device ppc at isa?...' line.
>
>Experimentation mode (on a machine I can cr
On Sun, Feb 14, 1999 at 11:52:04AM -0500, Chuck Robey wrote:
>
>On Sun, 14 Feb 1999, Nicolas Souchu wrote:
>
>> >I *never* expected to see the PNP functions actually pick up the name of
>> >my printer. I was economically bushwacked by the Windows corps into
>> >buying the 693C (the version with th
On Sun, 14 Feb 1999, Nicolas Souchu wrote:
> >I *never* expected to see the PNP functions actually pick up the name of
> >my printer. I was economically bushwacked by the Windows corps into
> >buying the 693C (the version with the Windows software floppies tacked
> >on) so I was actually pleased
On Sun, 14 Feb 1999, Nicolas Souchu wrote:
> >I *never* expected to see the PNP functions actually pick up the name of
> >my printer. I was economically bushwacked by the Windows corps into
> >buying the 693C (the version with the Windows software floppies tacked
> >on) so I was actually pleased
On Sat, Feb 13, 1999 at 10:03:41PM -0500, Chuck Robey wrote:
>
>I have to add an addendum here, to my previous question about the new
>config file setup for a simple printer. I was looking forward to seeing
>the probing come back to my dmesg, when I finally got it right, but
>seeing this:
>
>Feb 1
On Sat, Feb 13, 1999 at 10:03:41PM -0500, Chuck Robey wrote:
>
>I have to add an addendum here, to my previous question about the new
>config file setup for a simple printer. I was looking forward to seeing
>the probing come back to my dmesg, when I finally got it right, but
>seeing this:
>
>Feb 1
12 matches
Mail list logo
