Re: [patch 00/37] PNP resource_table cleanups

[Bjorn Helgaas]

On Monday 31 March 2008 01:40:03 pm Rene Herman wrote:
> 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.

Ah, right.  Thanks for tracking that down.  I forgot to factor out
isapnp_to_pnpid() and pnpid32_to_pnpid() (and acpi_ex_eisa_id_to_string()
for that matter, though that's buried in the ACPI CA)-- they're really
doing the same thing and we should only need one copy (plus the CA
one).

> 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.

Hmmm...  that sounds harder.  I'll read over it again and see if I
can figure anything out.

Bjorn

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/