On Sat, Jan 16, 1999 at 06:49:25PM +0000, Doug Rabson wrote:
>
>On Sat, 16 Jan 1999, Nicolas Souchu wrote:
>
>> On Fri, Jan 15, 1999 at 11:13:09AM +0000, Doug Rabson wrote:
>> >
>> >On Fri, 15 Jan 1999, Nicolas Souchu wrote:
>> >
>> >> Hi there,
>> >> 
>> >> Currently, the ZIP+ probe is intrusive and sends char to the printer if
>> >> no ZIP+ is connected.
>> >> 
>> >> Here is a patch that corrects the problem for my printer, but I haven't
>> >> any ZIP+ :)
>> >> 
>> >> So, please check the ZIP+ is still detected.
>> >
>> >With this patch, I can *not* detect my ZIP+ (attached to a machine which
>> >detects it using the existing code).
>> 
>> Ok :(
>> 
>> Does the last ppbus committed code (with IEEE1284 support) detects your
>> ZIP+ at boot? Something like "IEEE1284 device found /NIBBLE..." with
>> its id 2 lines after? This may be another way to detect properly the ZIP+
>
>Afraid not :-(.  The ppb_1284_negociate fails with an error of
>PPB_NOT_IEEE1284.  I haven't tried using the PERIPH_1284 option which
>seems to affect the negotiation - is it worth trying?

No. PERIPH_1284 should allow a computer to act as a IEEE1284 compliant
peripheral when connected to another computer.

>
>P.S. The correct spelling is 'negotiate'.  I keep wanting to do a
>global-replace :-)

Now, everybody on -current knows it :) I'm burned, as we say here.

>
>--
>Doug Rabson                            Mail:  d...@nlsystems.com
>Nonlinear Systems Ltd.                 Phone: +44 181 442 9037
>
>
>

-- 
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

Reply via email to