From: ebiederm@xmission.com (Eric W. Biederman)
To: Luca Falavigna <dktrkranz@gmail.com>
Cc: rdunlap@osdl.org, fastboot@osdl.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: kexec and frame buffer
Date: Sat, 06 Aug 2005 10:50:25 -0600 [thread overview]
Message-ID: <m13bpnyppq.fsf@ebiederm.dsl.xmission.com> (raw)
In-Reply-To: <42F4C6E8.1050605@gmail.com> (Luca Falavigna's message of "Sat, 06 Aug 2005 14:19:20 +0000")
Luca Falavigna <dktrkranz@gmail.com> writes:
> Eric W. Biederman ha scritto:
>> So without doing passing --real-mode the vga= parameter currently
>> cannot work. The vga= parameter is processed by vga.S which
>> make BIOS calls and we bypass all of the BIOS calls.
> Actually that file is video.S
Oops. Anyway I believe you also want to look at include/linux/tty.h
at the screen_info structure. I believe that is where
all of that information is passed.
>> So you can try with the --real-mode option and you have
>> a chance of the code working. Or you can figure out which
>> information video.S passes to the kernel figure out how
>> to get that same information out of a running kernel
>> and then /sbin/kexec can be tweaked to pass the current
>> video mode. Changing frame buffer modes shouldn't work
>> but you should at least be able to preserve the existing
>> ones.
> I tried to pass --real-mode flag to kexec but my virtual machine doesn't like
> it. When I launch kexec -e, it tells me: "A strange behaviour occourred which
> crashed virtual machine".
Cool. I haven't used that code in a long time but it is pretty
trivial code to switches to real mode so I don't really doubt it :)
> I'll dig source code ASAP to figure out this matter.
> Meanwhile I'm going to follow your advice to inspect video.S in order to track
> down something useful.
Sounds good.
Eric
next prev parent reply other threads:[~2005-08-06 16:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-04 13:35 kexec and frame buffer Luca Falavigna
2005-08-04 18:43 ` Eric W. Biederman
2005-08-06 14:19 ` Luca Falavigna
2005-08-06 16:50 ` Eric W. Biederman [this message]
2005-08-07 15:19 ` Luca Falavigna
2005-08-12 18:53 ` Luca Falavigna
2005-08-12 17:10 ` Eric W. Biederman
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=m13bpnyppq.fsf@ebiederm.dsl.xmission.com \
--to=ebiederm@xmission.com \
--cc=dktrkranz@gmail.com \
--cc=fastboot@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@osdl.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