Re: Problem with ioremap which returns NULL in 2.6 kernel

[Zwane Mwaikambo]

On Wed, 2 Jun 2004, Markus Lidel wrote:

> Zwane Mwaikambo wrote:
> >>>probably too large an area to be remapping.  Try remapping only the
> >>>memory area needed, and not the entire area.
> >>Is there a way, to increase the size, which could be remapped, or is
> >>there a way, to find out what is the maximum size which could be remapped?
> >>Thank you very much for the fast answer!
> > You could try a 4G/4G enabled kernel, /proc/meminfo tells you how much
> > vmalloc (ioremap) space there is too.
>
> VmallocTotal:   245752 kB
> VmallocUsed:    137720 kB
> VmallocChunk:   107904 kB
>
> Okay, i see the problem now, the largest piece of memory which could be
> allocated is 107904 kB, right?
>
> Is the 4G/4G split already in the kernel? If yes, which entry activates it?

No it's not in the current kernel, you'd have to download the patch, the
most uptodate being the one in the Fedora/Redhat kernel tree.
-
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/