[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <47F13E13.7090608@keyaccess.nl>
Date: Mon, 31 Mar 2008 21:40:03 +0200
From: Rene Herman <rene.herman@...access.nl>
To: Bjorn Helgaas <bjorn.helgaas@...com>
CC: Len Brown <lenb@...nel.org>, linux-acpi@...r.kernel.org,
linux-kernel@...r.kernel.org, Adam Belay <ambx1@....rr.com>,
Li Shaohua <shaohua.li@...el.com>,
Matthieu Castet <castet.matthieu@...e.fr>,
Thomas Renninger <trenn@...e.de>,
Jaroslav Kysela <perex@...ex.cz>,
Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: [patch 00/37] PNP resource_table cleanups
On 27-03-08 18:50, Bjorn Helgaas wrote:
> Are any ISAPNP devices at all found?
Yes, but at most 100 * 10^4 / 2^16 percent of them. Trouble is in 04/37:
http://lkml.org/lkml/2008/3/26/273
The numeric part of the ID is a 4-digit hexadecimal value, not just decimal,
so '0'+ don't work. Unfortunately, that one has a few dependents, so you'll
probably want to restructure things yourself. If I just place the attached
on top, the card's found again.
Not too much avail unfortunately, as I then get a resource assignment
problem with your patches:
pnp: the driver 'cs4236_isapnp' has been registered
cs4236_isapnp 01:01.00: driver attached
cs4236_isapnp 01:01.02: driver attached
cs4236_isapnp 01:01.03: driver attached
cs4236_isapnp 01:01.00: unable to assign resources
CS4236+ WSS PnP configure failed for WSS (out of resources?)
isapnp detection failed and probing for CS4236+ is not supported
(and exact same thing for snd-es18xx) which I'll try to look at next, but
this ID thing will certainly need a fix first.
Rene.
View attachment "isapnp_to_pnpid.diff" of type "text/plain" (915 bytes)
Powered by blists - more mailing lists