From: Andrew Morton <akpm@osdl.org>
To: adaplas@pol.net
Cc: adaplas@hotpop.com, linux-fbdev-devel@lists.sourceforge.net
Subject: Re: Re: [PATCH 1/6] nvidiafb: ioremap and i2c fixes
Date: Sun, 24 Apr 2005 22:00:58 -0700 [thread overview]
Message-ID: <20050424220058.0f95b392.akpm@osdl.org> (raw)
In-Reply-To: <200504251121.20530.adaplas@hotpop.com>
"Antonino A. Daplas" <adaplas@hotpop.com> wrote:
>
> > 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.
Well only if there are zero other current vmallocations and if we didn't
have the guard page.
unsigned int __VMALLOC_RESERVE = 128 << 20;
> > If so, that seems a bit user-hostile to me. Perhaps we should make it
> > 64MB?
>
> Okay, dropping maximum to 64 MiB.
Fair enough. I guess we should check the vmalloc max on all other
supported 32-bit architectures.
-------------------------------------------------------
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_id=6595&alloc_id=14396&op=click
next prev parent reply other threads:[~2005-04-25 5:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-16 5:13 [PATCH 1/6] nvidiafb: ioremap and i2c fixes Antonino A. Daplas
2005-04-24 0:40 ` Andrew Morton
2005-04-25 3:21 ` Antonino A. Daplas
2005-04-25 5:00 ` Andrew Morton [this message]
2005-04-25 5:03 ` Randy.Dunlap
2005-04-25 5:36 ` Miles Lane
2005-04-25 14:51 ` Randy.Dunlap
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20050424220058.0f95b392.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=adaplas@hotpop.com \
--cc=adaplas@pol.net \
--cc=linux-fbdev-devel@lists.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).