linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jon Smirl <jonsmirl@yahoo.com>
To: fbdev <linux-fbdev-devel@lists.sourceforge.net>
Subject: video dir reorg
Date: Mon, 13 Jan 2003 18:02:07 -0800 (PST)	[thread overview]
Message-ID: <20030114020207.84068.qmail@web14910.mail.yahoo.com> (raw)

Does it make sense to try merging the DRM drivers into
the video directory? Maybe something like this:

video -- empty except for Kconfig file
video/console -- generic fbconsole code
video/DRM -- generic DRM code
video/ati -- ati drivers (drm & fb)
video/i810 -- i810 drivers (drm & fb)
etc.....

This would allow the merging of the DRM and FB
hardware device drivers over time. Switching VTs
should be coordinated with saving 3D state.

Even with out merging DRM should the console driver be
split out from the hardware drivers?

=====
Jon Smirl
jonsmirl@yahoo.com

__________________________________________________
Do you Yahoo!?
Yahoo! Mail Plus - Powerful. Affordable. Sign up now.
http://mailplus.yahoo.com


-------------------------------------------------------
This SF.NET email is sponsored by: FREE  SSL Guide from Thawte
are you planning your Web Server Security? Click here to get a FREE
Thawte SSL guide and find the answers to all your  SSL security issues.
http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0026en

             reply	other threads:[~2003-01-14  2:02 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-14  2:02 Jon Smirl [this message]
2003-01-14  9:13 ` video dir reorg Sven Luther
2003-01-14 17:22   ` Jon Smirl
2003-01-14 21:26     ` Sven Luther
2003-01-15  0:37       ` James Simmons
2003-01-15  9:39         ` Geert Uytterhoeven
2003-01-15 21:38         ` Michel Dänzer
     [not found]           ` <20030116035231.36507.qmail@web14910.mail.yahoo.com>
2003-01-16 10:38             ` Sven Luther
2003-01-16 20:14             ` Michel Dänzer

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=20030114020207.84068.qmail@web14910.mail.yahoo.com \
    --to=jonsmirl@yahoo.com \
    --cc=linux-fbdev-devel@lists.sourceforge.net \
    /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).