From: "H. Peter Anvin" <hpa@zytor.com>
To: Pavel Machek <pavel@ucw.cz>
Cc: kernel list <linux-kernel@vger.kernel.org>, jikos@jikos.cz
Subject: Re: video resume stuff
Date: Thu, 04 Oct 2007 09:15:37 -0700 [thread overview]
Message-ID: <470511A9.4060705@zytor.com> (raw)
In-Reply-To: <20071004130513.GA16076@elf.ucw.cz>
Pavel Machek wrote:
> Hi!
>
> I'm thinking about how to clean up video resume/how to get it to work
> for non-VESA video modes (jikos' case).
>
> I guess the cleanest solution would be to just call set_mode from
> wakeup.S.... but that is not as easy as I imagined, because bootup
> code seems to be compiled separately.
>
> Is there some easy way to retain bootup code in memory, so that wakeup
> can use it? Or is there some easy solution I'm missing?
No, not really. The setup code is not even part of the kernel binary
proper, and may not even have been run under certain circumstances.
The "easy" solution is to link it in again, which seems to be what
you're doing. Now, currently the boot code is compiled after vmlinux is
complete, so some of the build ordering would have to be changed and/or
some of the code rearranged.
I suggest we tackle this *after* the x86 merge.
-hpa
next prev parent reply other threads:[~2007-10-04 16:16 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-04 13:05 video resume stuff Pavel Machek
2007-10-04 13:28 ` Arjan van de Ven
2007-10-04 14:24 ` Pavel Machek
2007-10-04 16:29 ` H. Peter Anvin
2007-10-04 16:15 ` H. Peter Anvin [this message]
2007-10-05 7:32 ` Pavel Machek
2007-10-05 14:59 ` Jiri Kosina
2007-10-05 18:34 ` H. Peter Anvin
2007-10-05 21:06 ` Jiri Kosina
2007-10-05 21:29 ` H. Peter Anvin
2007-10-05 21:42 ` H. Peter Anvin
2007-10-08 8:26 ` Jiri Kosina
2007-10-05 15:14 ` H. Peter Anvin
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=470511A9.4060705@zytor.com \
--to=hpa@zytor.com \
--cc=jikos@jikos.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@ucw.cz \
/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