linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Walt H <waltabbyh@comcast.net>
To: linux-fbdev-devel@lists.sourceforge.net
Subject: vesafb problem with 1GB Ram and possible fix
Date: Fri, 28 Mar 2003 12:59:55 -0800	[thread overview]
Message-ID: <3E84B7CB.1010604@comcast.net> (raw)
In-Reply-To: <3E837ADD.9080209@comcast.net>

I've got a Chaintech 7KDD dual processor 760MPX MB with 1 GB RAM. I had 
   problem getting vesafb or rivafb to work. I got ioremap errors during 
nitialization, which appear to be because vesafb tries to ioremap the 
entire 128MB framebuffer of my video card. It's a GeForce 4 Ti4600 with 
128MB Ram. Through correspondence on the general linux-kernel mailing 
list, I learned about changing the vmalloc reserved space from 128 to 
256MB, but that didn't work for me as it evidently blows away high-mem IO.

Well, here's what I've done. I've made a change in video/vesafb.c to
change __init vesafb_init to only allocate the amount of memory required 
  for the requested video mode of the framebuffer (I think). So far, it 
appears to work fine. I haven't tried many modes yet, but it's worked 
with what I've thrown at it. Thanks again,

The trivial change I made was changing this:

video_size	= screen_info.lfb_size * 65536;

to this:

video_size	= screen_info.lfb_width * screen_info.lfb_height * video_bpp;


I'm not a kernel hacker, so if I'm overlooking something please let me 
know. I've tested this a fair amount and it appears to be working on my 
end. Please CC me on any replies. Thanks,

-Walt




-------------------------------------------------------
This SF.net email is sponsored by:
The Definitive IT and Networking Event. Be There!
NetWorld+Interop Las Vegas 2003 -- Register today!
http://ads.sourceforge.net/cgi-bin/redirect.pl?keyn0001en

       reply	other threads:[~2003-03-28 21:00 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <3E8329D2.7040909@comcast.net>
     [not found] ` <20030327190222.GA4060@middle.of.nowhere>
     [not found]   ` <3E837ADD.9080209@comcast.net>
2003-03-28 20:59     ` Walt H [this message]
2003-03-29 10:41       ` vesafb problem with 1GB Ram and possible fix Antonino Daplas
2003-03-29 20:24         ` Walt H
2003-03-29 21:39           ` Antonino Daplas
2003-03-30 23:16             ` Walt H

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=3E84B7CB.1010604@comcast.net \
    --to=waltabbyh@comcast.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).