From: Jon Smirl <jonsmirl@gmail.com>
To: dri-devel@lists.sf.net, lkml <linux-kernel@vger.kernel.org>
Subject: Merging DRM and fbdev
Date: Sat, 2 Oct 2004 23:55:55 -0400 [thread overview]
Message-ID: <9e47339104100220553c57624a@mail.gmail.com> (raw)
I've started on a merged fbdev and DRM driver model.
It doesn't work yet but here's what the modules look like:
Module Size Used by
fbcon 38080 0
radeon 123598 1
fb 34344 2 fbcon,radeon
drm 59044 1 radeon
fbcon and fb modules are almost unmodified from the kernel source.
radeonfb and radeondrm have been merged into a single driver. The
merged driver uses both the drm and fb modules as libraries. It wasn't
possible to build this model until drm supported drm-core.
The radeon and fb modules will get smaller, I'm just beginning to use
the delete key on them. There is still a lot of duplicated code inside
the radeon driver.
In this model a non-drm, fb only driver like cyber2000 could load only
the fb and fbcon modules. I need to do some work rearranging generic
library support functions to allow this.
This is the next phase in the work described in this email:
http://lkml.org/lkml/2004/8/2/111
--
Jon Smirl
jonsmirl@gmail.com
next reply other threads:[~2004-10-03 3:55 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-03 3:55 Jon Smirl [this message]
2004-10-03 7:26 ` Merging DRM and fbdev Dave Airlie
2004-10-03 15:33 ` Jon Smirl
2004-10-03 15:50 ` Vladimir Dergachev
2004-10-03 16:24 ` Jon Smirl
2004-10-03 16:59 ` Vladimir Dergachev
2004-10-03 17:55 ` Jon Smirl
2004-10-03 20:37 ` Vladimir Dergachev
2004-10-03 22:42 ` Jon Smirl
2004-10-03 22:16 ` Alan Cox
2004-10-03 22:19 ` Alan Cox
2004-10-04 1:56 ` Vladimir Dergachev
2004-10-03 18:38 ` Mike Mestnik
2004-10-03 18:56 ` Jon Smirl
2004-10-04 19:48 ` Bill Davidsen
2004-10-03 16:46 ` Jon Smirl
2004-10-04 17:47 ` Tonnerre
2004-10-04 18:42 ` Jon Smirl
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=9e47339104100220553c57624a@mail.gmail.com \
--to=jonsmirl@gmail.com \
--cc=dri-devel@lists.sf.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.