public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Gerd Hoffmann <kraxel@suse.de>
To: "Antonino A. Daplas" <adaplas@gmail.com>
Cc: Kalev Lember <kalev@smartlink.ee>, linux-kernel@vger.kernel.org
Subject: Re: kexec and framebuffer
Date: Fri, 21 Jul 2006 08:54:49 +0200	[thread overview]
Message-ID: <44C07A39.9040309@suse.de> (raw)
In-Reply-To: <44C011B3.3060900@gmail.com>

Antonino A. Daplas wrote:
> Kalev Lember wrote:
>> Thank you, this was really helpful.
>>> +	if (0 != strcmp(fix.id, "vesafb"))
>>> +		goto out;
>> I think this check should be removed so that other framebuffer drivers
>> besides vesafb would also work.
> 
> I think having the check is correct, only vesafb relies totally on
> screen_info. If you remove the check, you can get the wrong information
> from other framebuffer drivers.

Exactly.

>> +	/* fixme: better get size from /proc/iomem */
>> +	real_mode->lfb_size       = (fix.smem_len + 65535) / 65536;
>> +	real_mode->pages          = (fix.smem_len + 4095) / 4096;
> 
> Note that fix.smem_len is the size of the remapped memory which can be
> smaller than the actual framebuffer length. But there's a fixme comment
> there so you probably know about this.

Yep, that is the reason for the fixme.  kexec-tools already parse
/proc/iomem, but keep the info private in some other source file, so I
decided to solve it this way for the first cut.  Shouln't be that hard
to fix it up though.

I've mailed it some time ago to the maintainer, no feedback.  Feel free
to polish the patch a bit and try submitting it again ...

cheers,

  Gerd

-- 
Gerd Hoffmann <kraxel@suse.de>
http://www.suse.de/~kraxel/julika-dora.jpeg

      reply	other threads:[~2006-07-21  6:54 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-17 14:11 kexec and framebuffer Kalev Lember
2006-07-17 14:29 ` Gerd Hoffmann
2006-07-20 20:42   ` Kalev Lember
2006-07-20 23:28     ` Antonino A. Daplas
2006-07-21  6:54       ` Gerd Hoffmann [this message]

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=44C07A39.9040309@suse.de \
    --to=kraxel@suse.de \
    --cc=adaplas@gmail.com \
    --cc=kalev@smartlink.ee \
    --cc=linux-kernel@vger.kernel.org \
    /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