From: matthieu castet <castet.matthieu@free.fr>
To: Meelis Roos <mroos@linux.ee>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH - Resend] PNPACPI: only parse device that have CRS method
Date: Sun, 11 Sep 2005 19:06:24 +0200 [thread overview]
Message-ID: <43246410.9000803@free.fr> (raw)
In-Reply-To: <20050911165410.6383314168@rhn.tartu-labor>
Hi Meelis
Meelis Roos wrote:
> mc> this patch blacklist device that don't have CRS method as there are
> mc> useless for pnp layer as they don't provide any resource.
>
> I tried it on my laptop (Toshiba Satellite 1800-314). It removed one
> device from PNP bus, 00:0c, id = TOS6200, no options (as shown by 2.6.13).
>
> I hoped it will notice something different about my SMCf010. It's
> onboard IRDA that is disabled by BIOS. But the device is still there
> with your patch and still does not work.
>
> The background: it's disabled by BIOS. PNPBIOS could activate it
> (haven't tried since PNPACPI came). PNPACPI could not activate it -
> activate worked, resources showed resources but smsc-ircc2 got still no
> configuration (chip itself was not reprogrammed?). The speculation was
> that it's because of missing CRS in ACPI tables but this device did not
> disappear with your current patch.
>
> Any ideas about getting it to work with PNPACPI - or should I just
You could try
http://marc.theaimsgroup.com/?l=linux-kernel&m=111827568001255&w=2 if
you haven't yet tried it ?
> declare my ACPI BIOS broken and revert to PNPBIOS on this laptop? Do you
> want seome more ACPI debug info than last time?
>
You could always use pnpacpi=no (or something like that) to disable
pnpacpi and use pnpbios (IIRC this one worked).
cheers,
Matthieu
next prev parent reply other threads:[~2005-09-11 17:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-11 10:12 [PATCH - Resend] PNPACPI: only parse device that have CRS method matthieu castet
2005-09-11 16:54 ` Meelis Roos
2005-09-11 17:06 ` matthieu castet [this message]
2005-09-11 18:44 ` Meelis Roos
2005-09-12 14:39 ` 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=43246410.9000803@free.fr \
--to=castet.matthieu@free.fr \
--cc=linux-kernel@vger.kernel.org \
--cc=mroos@linux.ee \
/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