From: Adam Baker <linux@baker-net.org.uk>
To: "Matwey V. Kornilov" <matwey@sai.msu.ru>, gregkh@linuxfoundation.org
Cc: hsommer@eso.org, matwey.kornilov@gmail.com,
linux-kernel@vger.kernel.org, linux-parport@lists.infradead.org
Subject: Re: [Linux-parport] [PATCH 2/2] parport: parport_pc: Add force_epp module option for parport_pc.
Date: Mon, 30 Jun 2014 23:47:01 +0100 [thread overview]
Message-ID: <53B1E8E5.6080808@baker-net.org.uk> (raw)
In-Reply-To: <alpine.LRH.2.00.1406301248200.15067@lnfm1.sai.msu.ru>
On 30/06/14 09:48, Matwey V. Kornilov wrote:
>
> The detection of Intel EPP bug is known to produce much false positives.
> The new option is introduced to force enable EPP in spite of the test
> result.
I can confirm that this check produces false positives on a range of
hardware - I no longer have the machine that I experienced the problem
with but when I posted about the issue in the past I had several
responses from other users suffering from the problem.
>
> Tested-by: Heiko Andreas Sommer <hsommer@eso.org>
> Signed-off-by: Matwey V. Kornilov <matwey@sai.msu.ru>
> ---
> drivers/parport/parport_pc.c | 9 ++++++++-
> 1 file changed, 8 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/parport/parport_pc.c b/drivers/parport/parport_pc.c
> index 4b851bb..1a15b9c 100644
> --- a/drivers/parport/parport_pc.c
> +++ b/drivers/parport/parport_pc.c
> @@ -105,6 +105,9 @@ static int user_specified;
> (defined(CONFIG_PARPORT_1284) && defined(CONFIG_PARPORT_PC_FIFO))
> static int verbose_probing;
> #endif
> +#ifdef CONFIG_PARPORT_1284
> +static int force_epp;
> +#endif
> static int pci_registered_parport;
> static int pnp_registered_parport;
>
> @@ -1765,7 +1768,7 @@ static int parport_EPP_supported(struct parport *pb)
> return 0; /* No way to clear timeout */
>
> /* Check for Intel bug. */
> - if (intel_bug_present(pb))
> + if (!force_epp && intel_bug_present(pb))
> return 0;
>
> pb->modes |= PARPORT_MODE_EPP;
> @@ -3148,6 +3151,10 @@ module_param_array(dma, charp, NULL, 0);
> MODULE_PARM_DESC(verbose_probing, "Log chit-chat during initialisation");
> module_param(verbose_probing, int, 0644);
> #endif
> +#ifdef CONFIG_PARPORT_1284
> +MODULE_PARM_DESC(force_epp, "Do not disable EPP when it is detected to
> be broken (default is false)");
I think this needs some more explanation - how about
"Disable check for broken Intel EPP hardware that gives false positives
on 2002 and newer hardware"
The 2002 date is based upon
http://thread.gmane.org/gmane.linux.parport/322/focus=326
Last time fixing this was discussed Jonathan Nieder did some digging in
the history and technical details and posted at the tail of the thread at
https://groups.google.com/forum/?_escaped_fragment_=topic/linux.debian.bugs.dist/nhK1ZU4x0Ok#!topic/linux.debian.bugs.dist/nhK1ZU4x0Ok
> +module_param(force_epp, int, 0);
> +#endif
> #ifdef CONFIG_PCI
> static char *init_mode;
> MODULE_PARM_DESC(init_mode,
next prev parent reply other threads:[~2014-06-30 22:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-30 8:48 Matwey V. Kornilov
2014-06-30 22:47 ` Adam Baker [this message]
2014-07-01 7:27 ` [Linux-parport] " Matwey V. Kornilov
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=53B1E8E5.6080808@baker-net.org.uk \
--to=linux@baker-net.org.uk \
--cc=gregkh@linuxfoundation.org \
--cc=hsommer@eso.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-parport@lists.infradead.org \
--cc=matwey.kornilov@gmail.com \
--cc=matwey@sai.msu.ru \
/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
all inboxes | Powered by JetHome®