From: Kalev Lember <kalev@smartlink.ee>
To: Gerd Hoffmann <kraxel@suse.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: kexec and framebuffer
Date: Thu, 20 Jul 2006 23:42:13 +0300 [thread overview]
Message-ID: <44BFEAA5.5030703@smartlink.ee> (raw)
In-Reply-To: <44BB9EB3.9020101@suse.de>
Gerd Hoffmann wrote:
>> I am wondering what would be the preferred method to extract screen_info
>> from running kernel. Should this be made available from sysfs or maybe a
>> new system call be created?
>>
>
> Simply ask /dev/fb0?
> Patch for kexec tools attached.
>
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. Additionally the fix.id is "VESA VGA",
not "vesafb".
Could you please submit this for inclusion in kexec-tools or do you want
me to do it?
--
Kalev Lember
next prev parent reply other threads:[~2006-07-20 20:42 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 [this message]
2006-07-20 23:28 ` Antonino A. Daplas
2006-07-21 6:54 ` Gerd Hoffmann
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=44BFEAA5.5030703@smartlink.ee \
--to=kalev@smartlink.ee \
--cc=kraxel@suse.de \
--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