From: Antonino Daplas <adaplas@pol.net>
To: James Simmons <jsimmons@infradead.org>
Cc: Linux Fbdev development list
<linux-fbdev-devel@lists.sourceforge.net>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [Linux-fbdev-devel] [PATCH 1/3: FBDEV: VGA State Save/Restore module
Date: 06 Dec 2002 20:27:16 +0500 [thread overview]
Message-ID: <1039188475.1405.0.camel@localhost.localdomain> (raw)
In-Reply-To: <Pine.LNX.4.44.0212060051080.31967-100000@phoenix.infradead.org>
On Fri, 2002-12-06 at 05:53, James Simmons wrote:
> >
> > Only the structure definition of fb_vgastate is in fb.h. For drivers
> > without a vga core, they'll just won't link to it and it won't be
> > compiled. Plus, vga.h is not a common header (not located in
> > include/asm or include/linux) and it contains a lot of declarations and
> > definitions which are irrelevant to most drivers or are already
> > duplicated. This will be messier, I think.
>
> I like to move vga.h to include/video. And yes I like to clean it up. The
> reason is I like to implement the function in vga.h and some in vgastate
> into vgacon.c. It would be nice if vgacon could support different hardware
> states per VC instead of changing every virtual console for everything.
> The other dream is I like to see vgacon become firmware independent.
>
OK.
Tony
prev parent reply other threads:[~2002-12-06 15:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-04 17:26 [PATCH 1/3: FBDEV: VGA State Save/Restore module Antonino Daplas
2002-12-05 17:31 ` [Linux-fbdev-devel] " James Simmons
2002-12-06 0:47 ` Antonino Daplas
2002-12-06 0:53 ` James Simmons
2002-12-06 15:27 ` Antonino Daplas [this message]
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=1039188475.1405.0.camel@localhost.localdomain \
--to=adaplas@pol.net \
--cc=jsimmons@infradead.org \
--cc=linux-fbdev-devel@lists.sourceforge.net \
--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;
as well as URLs for NNTP newsgroup(s).