From: Arvid Picciani <aep@exys.org>
To: linux-fbdev@vger.kernel.org
Subject: Relation of FBDev and DRM/KMS
Date: Fri, 18 Jun 2010 02:59:58 +0000 [thread overview]
Message-ID: <87sk4l82q9.fsf@exys.org> (raw)
Hi,
I'm trying to crowbar some extra VMemory into fbdev devices to abuse
them in a similar fashion to what DRM does. I'm trying to avoid DRM for
various reasons, but it seems all of the new stuff _only_ goes in DRM.
Specifically, the intel/nvidia drivers seems to be only useful in
combination with DRM. I need KMS for laziness, but that needs DRM?
No way to get kms without running DRM?
If i have to run DRM, is there any Documentation that explains the
relation to fbdev? Eyeballing around in the intel code tells me, the
framebuffer is actually a DRM gem thingy. Can i sort of blit other DRM
gems onto a framebuffer?
If i can avoid DRM, any idea how i could allocate small VMem areas from
userspace on demand? FB seems to have no api for that at all.
All we have is a single large VMem area to pixel manipulate.
Unless i totally missread that code. I am guessing, i could archive what
i want by adding some extra ioctls, but i dont see where, since the device
is abstracted away from the drivers.
--
Arvid
reply other threads:[~2010-06-18 2:59 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=87sk4l82q9.fsf@exys.org \
--to=aep@exys.org \
--cc=linux-fbdev@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.