Hi Chris,
On Wed, Jun 03, 2009 at 01:59:41AM -0400, Chris Ball wrote:
> Hi Harald,
>
>> this means you need to boot with vmalloc=. The
>> framebuffer needs to be vmalloc'ed. So if you have a relatively
>> small amount of RAM, and the BIOS is configured for 256MB
>> framebuffer s
Hi Harald,
> this means you need to boot with vmalloc=. The
> framebuffer needs to be vmalloc'ed. So if you have a relatively
> small amount of RAM, and the BIOS is configured for 256MB
> framebuffer size, the kernel-selected vmalloc area is smaller
> than what we need for the fra
On Fri, May 29, 2009 at 03:01:02AM -0400, Chris Ball wrote:
> It can't, but I don't mind communicating by e-mail and updating the
> tracker afterwards if you'd prefer.
I'll respond by mail now, but will check out the tracker later. Just arrived
back from 4 days offline and have tons of backlog
>
Hi,
> Why is viafb trying to allocate 268 MB of memory ? That seems
> like a lot for a simple fb driver..
Answer: Because the BIOS told it to.
Question #2: What happens if you change the framebuffer size in the
BIOS to 32M?
Answer #2: It works. :)
There's some sort of corruption in th
Why is viafb trying to allocate 268 MB of memory ?
That seems like a lot for a simple fb driver..
wad
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel
Hi Harald,
> [ I hope your bug tracker can take email responses, please tell
> me if not ]
It can't, but I don't mind communicating by e-mail and updating the
tracker afterwards if you'd prefer.
> mh, the problem must be related to that particular board, as I've
> tested the code on
[ I hope your bug tracker can take email responses, please tell me if not ]
On Fri, May 29, 2009 at 02:30:58AM -, Zarro Boogs per Child wrote:
> Hi Harald, looks like the new viafb patches have some problems. I just
> pulled out a VX800 laptop with panel to try on that too, and the screen
