From: DervishD <raul@pleyades.net>
To: Linux-kernel <linux-kernel@vger.kernel.org>
Subject: [SOLVED] parport problems, thanks to Dino Klein
Date: Mon, 2 Aug 2004 18:41:16 +0200 [thread overview]
Message-ID: <20040802164116.GB1102@DervishD> (raw)
Hi all :)
Finally I got ECP working. The solution: activate
CONFIG_EXPERIMENTAL and CONFIG_PARPORT_PC_FIFO (in 2.4.26, at least),
and get rid of EPP+ECP mode in BIOS. Now I have only ECP in BIOS (I
tested more modes, anyway) and the kernel detects correctly the
parallel port as long as I provide the irq, dma, io and io_hi
settings to the module.
My other problem was lack of IEEE1284 support, and, once ECP
detected, I went to solve this. The problem was related to cabling
and one digital printer sharing device. The device detects
automatically which input wants the printer, so you don't need to
manually turn the knob ;). That device was eating the IEEE1284
signalling, and once removed all works ok.
The parport module still does weird things when the BIOS mode is
not EPP nor ECP, or when I want it to autodetect the parallel port,
but at least now prints correctly, fast and tells me when I'm out of
paper ;))
I want to thank Dino Klein for his highly valuable help, trying
to solve my problem. He has helped me to find the cause of the
problem, even backporting his 2.6 ACPI patch to my 2.4.26 kernel. Is
people like him that makes free software the way it is, and really no
money could buy such a good and friendly support. Thanks a lot, Dino.
Raúl Núñez de Arenas Coronado
--
Linux Registered User 88736
http://www.pleyades.net & http://raul.pleyades.net/
reply other threads:[~2004-08-02 16:54 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20040802164116.GB1102@DervishD \
--to=raul@pleyades.net \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.