From: Remi Turk <remi@a2zis.com>
To: linux-kernel@vger.kernel.org
Cc: Axel Boldt <axel@uni-paderborn.de>,
Phil Blundell <Philip.Blundell@pobox.com>
Subject: [PATCH] Configure.help:
Date: Wed, 6 Jun 2001 12:24:34 +0200 [thread overview]
Message-ID: <20010606122434.B859@localhost.localdomain> (raw)
[-- Attachment #1: Type: text/plain, Size: 427 bytes --]
Hi,
it seems the Configure.help text for CONFIG_LP_CONSOLE
is incorrect: The default is to stall until the printer
is ready while the help text says the opposite.
(vi +540 drivers/char/lp.c)
Attached is a patch for 2.4.6-pre1 which fixes the help text.
Also, shouldn't CONFIG_LP_CONSOLE depend on CONFIG_PRINTER=y?
(it doesn't work when CONFIG_PRINTER=m, at least for me)
--
Linux 2.4.5-ac9 #3 Wed Jun 6 11:15:40 CEST 2001
[-- Attachment #2: Configure.help.patch --]
[-- Type: text/plain, Size: 982 bytes --]
diff -ur --new-file linux-2.4.6-pre1/Documentation/Configure.help linux-2.4.6-pre1.new/Documentation/Configure.help
--- linux-2.4.6-pre1/Documentation/Configure.help Wed Jun 6 11:54:24 2001
+++ linux-2.4.6-pre1.new/Documentation/Configure.help Wed Jun 6 11:54:32 2001
@@ -13014,10 +13014,12 @@
doing that; to actually get it to happen you need to pass the
option "console=lp0" to the kernel at boot time.
- Note that kernel messages can get lost if the printer is out of
- paper (or off, or unplugged, or too busy..), but this behaviour
- can be changed. See drivers/char/lp.c (do this at your own risk).
-
+ If the printer is out of paper (or off, or unplugged, or too
+ busy..) the kernel will stall until the printer is ready again.
+ By defining CONSOLE_LP_STRICT to 0 (at your own risk) you
+ can make the kernel continue when this happens,
+ but it'll lose the kernel messages.
+
If unsure, say N.
Support for user-space parallel port device drivers
next reply other threads:[~2001-06-06 10:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-06 10:24 Remi Turk [this message]
2001-06-06 10:46 ` [PATCH] Configure.help: Tim Waugh
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=20010606122434.B859@localhost.localdomain \
--to=remi@a2zis.com \
--cc=Philip.Blundell@pobox.com \
--cc=axel@uni-paderborn.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox