Date: Sun, 30 Jan 2000 17:51:57 +0800 From: Peter Wemm <peter@netplex.com.au> To: Matthew Dillon <dillon@apollo.backplane.com> Cc: David Gilbert <dgilbert@velocet.ca>, freebsd-current@FreeBSD.ORG Subject: Re: Printer fiascos. Message-ID: <20000130095157.A606D1CD7@overcee.netplex.com.au> In-Reply-To: Message from Matthew Dillon <dillon@apollo.backplane.com> of "Sat, 29 Jan 2000 20:21:33 PST." <200001300421.UAA28556@apollo.backplane.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Matthew Dillon wrote:
> When the new parallel port stuff was put several months ago, my
> machine stopped working. I had to set flags to 0x40 to make it
> work again. Flags of 0x40 force the driver to use the most
> basic probes possible. It was put in because a number of people's
> machines stopped working.
>
> It looks like Peter removed the flags 0x40 in rev 1.228 of GENERIC
> on Jan 14.
>
> At the time I had an argument with the author who insisted that
> the correct way to force 'basic' probing of the printer was to
> set the flags field in GENERIC rather then make the default a basic
> probe.
>
> * Peter, the comment in your log message makes no mention of the reason
> * for removing the flags. If you did this by accident could you please
> * set the flags back to 0x40?
The reason I did that was because flags 0x40 only does something if you
activate the PPC_PROBE_CHIPSET option. By default you get flags 0x40
type behavior and the intrusive probes are simply not even compiled into
the driver. If you activate the option, then you can also specify
flags 0x40 to disable the code you compiled in. In other words, GENERIC
does not require the flag any more as it doesn't have the option active.
#ifdef PPC_PROBE_CHIPSET
/* we have to differenciate available chipset modes,
* chipset running modes and IEEE-1284 operating modes
*
* after detection, the port must support running in compatible mode
*/
if (ppc->ppc_flags & 0x40) {
if (bootverbose)
printf("ppc: chipset forced to generic\n");
#endif
> Now, a huge number of changes have been made since the original problem
> was reported, so I could be puffing smoke here. I didn't see anything
> in the CVS logs, though, so I am assuming that the removal of the
> flags field was a mistake.
>
> David, try putting flags 0x40 back in and see if that fixes your
> problem.
>
> -Matt
> Matthew Dillon
> <dillon@backplane.com>
>
> :Why is it that a properly functioning printer is such a moving target
> :in FreeBSD?
> :
> :I don't mean to be argumentative, but under 3.x, the magic cookie to
> :make printers work (it appeared to be a flow control problem) was to
> :change
> :
> :device ppc0 at isa? port? flags 0x40 net irq 7
> :
> :to
> :
> :device ppc0 at isa? port? flags 0x40 tty irq 7
> :
> :Now... I've upgraded to -CURRENT, and it has a much more serious
> :problem. The line now reads
> :
> :device ppc0 at isa? port? irq 7
> :
> :... so I havn't tried putting net or tty in it, but I have a printer
> :with a particular problem --- it will often fail to pick up a sheet of
> :paper. I suspect that this sets the paper out sense line of the
> :parallel port (?).
> :
> :When this happens, the entire machine freezes until someone feeds the
> :printer --- the momment it starts printing again, the computer
> :unfreezes.
> :
> :Printer-port related things probe as:
> :
> :ppc0: <Parallel port> at port 0x378-0x37f irq 7 on isa0
> :ppc0: Generic chipset (EPP/NIBBLE) in COMPATIBLE mode
> :ppbus0: IEEE1284 device found /NIBBLE/PS2/ECP
> :Probing for PnP devices on ppbus0:
> :ppbus0: <HEWLETT-PACKARD DESKJET 870C> PCL,MLC,PML
> :lpt0: <Printer> on ppbus0
> :lpt0: Interrupt-driven port
> :plip0: <PLIP network interface> on ppbus0
> :ppi0: <Parallel I/O> on ppbus0
> :
> :(I have tried putting the BIOS in different parallel port modes.)
> :
> :Dave.
> :
> :--
> :============================================================================
> :|David Gilbert, Velocet Communications. | Two things can only be |
> :|Mail: dgilbert@velocet.net | equal if and only if they |
> :|http://www.velocet.net/~dgilbert | are precisely opposite. |
> :=========================================================GLO================
>
>
Cheers,
-Peter
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?20000130095157.A606D1CD7>