Re: [PATCH] Allocate pnp resources dynamically via krealloc - working version

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 28-01-08 15:21, Thomas Renninger wrote:

I think I know what is going on.
While pnpbios and pnpacpi theoretically do not have limits, isapnp has
spec restrictions (AFAIK, I have not read this up, but taken over from
previous implementation...).
Therefore in isapnp I wanted to stay with:
#define PNP_MAX_PORT            8
#define PNP_MAX_MEM             4
#define PNP_MAX_IRQ             2
#define PNP_MAX_DMA             2
but I have forgotten to malloc one portion for each at init time, or
even better one portion as soon as one is needed.

Yup.

As said, isapnp is more or less untested, thanks a lot for trying out.
I will send an updated version soon.

I"m not sure of the flow of things by the way but if it makes better/nicer code to just pretend that ISAPnP is also unlimited then I'd say to simply do so. ISAPnP is getting obsolete anyway, not anything to optimise for...

Rene.
-
To unsubscribe from this list: send the line "unsubscribe linux-acpi" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Linux IBM ACPI]     [Linux Power Management]     [Linux Kernel]     [Linux Laptop]     [Kernel Newbies]     [Share Photos]     [Security]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Samba]     [Video 4 Linux]     [Device Mapper]     [Linux Resources]

  Powered by Linux