Re: Re: [PATCH 1/6] nvidiafb: ioremap and i2c fixes

[Miles Lane <miles.lane@gmail.com>]

On 4/24/05, Randy.Dunlap <rddunlap@osdl.org> wrote:
> On Mon, 25 Apr 2005 11:21:20 +0800 Antonino A. Daplas wrote:
> 
> | On Sunday 24 April 2005 08:40, Andrew Morton wrote:
> | > "Antonino A. Daplas" <adaplas@hotpop.com> wrote:
> | > > - Add 'vram' option to specify amount of video RAM to remap
> | > >  - Limit remap size to 128 MIB
> | >
> | > Am I right in believing that if someone has a 256MB card and doesn't know
> | > about the `vram' option, their card will fail to work, because the 128MB
> | > vmalloc() will fail?
> | >
> |
> | I thought that a 128MiB vmalloc will work.
> 
> The default vmalloc total size is 128 MB, but the kernel always
> requires a "guard page", which cannot be allocated, so the
> total allocation fails.
> 
> I tried to make a patch that sets the default vmalloc total size
> to 128 MB + PAGE_SIZE, but Miles reported that the driver's
> vmalloc() call still failed...

Which seems to beg a couple of questions:
How much memory is _really_ trying to get allocated when I boot
with no vmalloc argument.  Does this point to some problem in 
the nvidiafb code?  Does the fact that specifying vmalloc=128M
does not fix the problem indicate that something about my video
card won't work with less than 256Mb vmalloced, or is this a
driver issue?

Thanks,
        Miles


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_ide95&alloc_id\x14396&op=click