From: matthieu castet <castet.matthieu@free.fr>
To: Bjorn Helgaas <bjorn.helgaas@hp.com>
Cc: Martin Doucha <next_ghost@quick.cz>,
Linux Kernel list <linux-kernel@vger.kernel.org>,
bugme-daemon@bugzilla.kernel.org
Subject: Re: [Bug 11603] Re: ACPI PnP on Intel MU440EX
Date: Thu, 25 Sep 2008 20:52:22 +0200 [thread overview]
Message-ID: <48DBDDE6.3060301@free.fr> (raw)
In-Reply-To: <200809241705.13410.bjorn.helgaas@hp.com>
Bjorn Helgaas wrote:
>> If you want you could try to run the attached program on your pc in
>> "auto/bidirectional" or "auto/EPP" mode.
>>
>> This program does what _STA methods do.
>
> I'm just curious -- what do you hope to learn from this program?
> Do you think it will tell us more than what actually running _STA
> did?
>
Yes I was curious of the value before the mask : some of the mask and
comparaison look strange.
> The best solution I can think of would be to have a parameter like
> "parport.nopnp" that made parport just probe the legacy addresses,
> and document that you might need that on machines with broken ACPI
> firmware. But I'm a little afraid to touch parport_pc.c.
Aren't parport still probing it's own port if pnp failed ?
Matthieu
next prev parent reply other threads:[~2008-09-25 18:52 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-31 13:22 ACPI PnP on Intel MU440EX Martin Doucha
2008-09-09 16:34 ` Bjorn Helgaas
2008-09-14 19:28 ` Martin Doucha
2008-09-17 5:39 ` Bjorn Helgaas
2008-09-20 22:59 ` [Bug 11603] " Bjorn Helgaas
2008-09-22 23:01 ` Bjorn Helgaas
2008-09-23 21:29 ` matthieu castet
2008-09-24 23:05 ` Bjorn Helgaas
2008-09-25 18:52 ` matthieu castet [this message]
2008-09-25 19:53 ` Bjorn Helgaas
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=48DBDDE6.3060301@free.fr \
--to=castet.matthieu@free.fr \
--cc=bjorn.helgaas@hp.com \
--cc=bugme-daemon@bugzilla.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=next_ghost@quick.cz \
/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.