public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: ebiederm@xmission.com (Eric W. Biederman)
To: Pavel Machek <pavel@suse.cz>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2.5.12] x86 Boot enhancements, boot params 1/11
Date: 06 May 2002 11:55:51 -0600	[thread overview]
Message-ID: <m1pu0917q0.fsf@frodo.biederman.org> (raw)
In-Reply-To: <m11ycuzk4q.fsf@frodo.biederman.org> <20020427025642.E413@toy.ucw.cz> <m1u1pl1t4h.fsf@frodo.biederman.org> <20020506151939.GE12131@atrey.karlin.mff.cuni.cz>

Pavel Machek <pavel@suse.cz> writes:

> Hi!
> 
> > > > #5  boot.heap
> > > > ============================================================
> > > > Modify video.S so that mode_list is also allocated from
> > > > the boot time heap.  This probably saves a little memory,
> > > > and makes a compiled in command line a sane thing to implement.
> > > 
> > > Do you see easy way to pass video mode used to kernel? S3 suspend support
> > > is going to need that..
> > 
> > Do you mean something other than the vga= command line option?
> > Which actually just sets a 16bit mode in the kernel parameter structure.
> 
> In case of vga=ask, it is kernel that gets number from the user,
> right?

Right.
 
> I'd need to know what mode was actually selected, so I can restore it
> after S3 resume.

I guess that works.  In this case it makes sense for the kernel to
store it in the same variable the video mode is specified in.  This
may require an extra store but it should be trivial to implement.

How are you handling the case of X and friends?  Are you making
certain to switch to kernel controlled vt?

My hunch is that this is a decent argument for real framebuffer drivers
in the kernel.  But that is a separate problem.

Eric

  reply	other threads:[~2002-05-06 18:03 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-02 14:42 [PATCH 2.5.12] x86 Boot enhancements, boot params 1/11 Eric W. Biederman
2002-04-27  2:56 ` Pavel Machek
2002-05-06 10:13   ` Eric W. Biederman
2002-05-06 15:19     ` Pavel Machek
2002-05-06 17:55       ` Eric W. Biederman [this message]
2002-05-06 20:20         ` Pavel Machek
2002-05-02 14:45 ` [PATCH 2.5.12] x86 Boot enhancements, linker fixes 2/11 Eric W. Biederman
2002-05-02 14:48   ` [PATCH 2.5.12] x86 Boot enhancements, bzImage/zImage code differentiation 3/11 Eric W. Biederman
2002-05-02 14:51     ` [PATCH 2.5.12] x86 Boot enhancements, constants 4/11 Eric W. Biederman
2002-05-02 14:55       ` [PATCH 2.5.12] x86 Boot enhancements, heap 5/11 Eric W. Biederman
2002-05-02 15:00         ` [PATCH 2.5.12] x86 Boot enhancements, 32bit entries 6/11 Eric W. Biederman
2002-04-27  4:53           ` Pavel Machek
2002-05-02 15:05           ` [PATCH 2.5.12] x86 Boot enhancements, footprint reduction 7/11 Eric W. Biederman
2002-05-02 15:07             ` [PATCH 2.5.12] x86 Boot enhancements, build beancounting 8/11 Eric W. Biederman
2002-05-02 15:11               ` [PATCH 2.5.12] x86 Boot enhancements, boot protocol 2.04 9/11 Eric W. Biederman
2002-05-02 15:13                 ` [PATCH 2.5.12] x86 Boot enhancements, LinuxBIOS support 10/11 Eric W. Biederman
2002-05-02 15:15                   ` [PATCH 2.5.12] x86 Boot enhancements, bzElf support 11/11 Eric W. Biederman
2002-05-02 20:45                     ` H. Peter Anvin
2002-05-02 20:39                 ` [PATCH 2.5.12] x86 Boot enhancements, boot protocol 2.04 9/11 H. Peter Anvin
2002-05-02 20:45                 ` 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=m1pu0917q0.fsf@frodo.biederman.org \
    --to=ebiederm@xmission.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pavel@suse.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