mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@ucw.cz>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: kernel list <linux-kernel@vger.kernel.org>,
	jikos@jikos.cz, "Rafael J. Wysocki" <rjw@sisk.pl>
Subject: Re: video resume stuff
Date: Fri, 5 Oct 2007 09:32:38 +0200	[thread overview]
Message-ID: <20071005073238.GA19065@atrey.karlin.mff.cuni.cz> (raw)
In-Reply-To: <470511A9.4060705@zytor.com>

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 guess major change is to rename conflicting symbols, so that it is
possible to link it twice. That would mean boot_memset() instead of
memset() etc... Is that acceptable?

> I suggest we tackle this *after* the x86 merge.

Well, we still have the regression on jikos' strange system, and I
would like to understand what is going on there.
									Pavel
-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

  reply	other threads:[~2007-10-05  7:32 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-04 13:05 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
2007-10-05  7:32   ` Pavel Machek [this message]
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=20071005073238.GA19065@atrey.karlin.mff.cuni.cz \
    --to=pavel@ucw.cz \
    --cc=hpa@zytor.com \
    --cc=jikos@jikos.cz \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rjw@sisk.pl \
    /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

all inboxes | Powered by JetHome®