From: Vladimir Dergachev <volodya@mindspring.com>
To: Jon Smirl <jonsmirl@gmail.com>
Cc: Dave Airlie <airlied@linux.ie>,
dri-devel@lists.sourceforge.net,
lkml <linux-kernel@vger.kernel.org>
Subject: Re: Merging DRM and fbdev
Date: Sun, 3 Oct 2004 11:50:50 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.4.61.0410031145560.17248@node2.an-vo.com> (raw)
In-Reply-To: <9e4733910410030833e8a6683@mail.gmail.com>
On Sun, 3 Oct 2004, Jon Smirl wrote:
> If we could all just concentrate on fixing the radeondrm driver we
> could build a complete driver for the radeon cards instead of the ten
> half finished ones we have today. Once we get a complete driver the
> incentive for people to write new ones will be gone.
> My model....
>
> radeon - attached to hardware
> drm - library
> fb - library
> fbcon - library
Can we add to this "km" library ? (That's the GATOS v4l module)
In particular, I can contribute the code that does Framebuffer->System Ram
transfers over PCI/AGP. It is currently GPL licensed, but there is no
problem if BSD folks want it too.
This is also potentially useful for any Mesa functions that want to
transfer data back from video RAM - using plain reads for this is really slow.
best
Vladimir Dergachev
next prev parent reply other threads:[~2004-10-03 15:51 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-03 3:55 Jon Smirl
2004-10-03 7:26 ` Dave Airlie
2004-10-03 15:33 ` Jon Smirl
2004-10-03 15:50 ` Vladimir Dergachev [this message]
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=Pine.LNX.4.61.0410031145560.17248@node2.an-vo.com \
--to=volodya@mindspring.com \
--cc=airlied@linux.ie \
--cc=dri-devel@lists.sourceforge.net \
--cc=jonsmirl@gmail.com \
--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
all inboxes | Powered by JetHome®