From: Vladimir Dergachev <volodya@mindspring.com>
To: Jon Smirl <jonsmirl@gmail.com>
Cc: fbdev <linux-fbdev-devel@lists.sourceforge.net>,
DRI developer's list <dri-devel@lists.sourceforge.net>,
esellers@users.sourceforge.net
Subject: Re: waitforVBlank, how does this even work?
Date: Wed, 2 Mar 2005 12:45:54 -0500 (EST) [thread overview]
Message-ID: <Pine.LNX.4.62.0503021242370.15365@node2.an-vo.com> (raw)
In-Reply-To: <9e47339105030209302701e9b5@mail.gmail.com>
On Wed, 2 Mar 2005, Jon Smirl wrote:
> On Wed, 2 Mar 2005 12:15:18 -0500 (EST), Vladimir Dergachev
> <volodya@mindspring.com> wrote:
>>> I would find it useful if someone came up with a standard kernel space
>>> V4L radeon driver instead of the Gatos stuff.
>>
>> By "standard" you mean "self-contained", right ?
>
> One that doesn't depend on X being there.
>
> Can one be build now that just ignores the memory management hooks?
Sure, but you would have to give up using X on that card.
In fact, Eric Sellers has already written such a module that provides V4L
1 and 2 support (Eric, please correct me if I got anything wrong..)
best
Vladimir Dergachev
>
> --
> Jon Smirl
> jonsmirl@gmail.com
>
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
--
next prev parent reply other threads:[~2005-03-02 17:45 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-02 5:50 waitforVBlank, how does this even work? Jon Smirl
2005-03-02 5:55 ` Jon Smirl
2005-03-02 7:10 ` Benjamin Herrenschmidt
2005-03-02 7:30 ` [Linux-fbdev-devel] " Ville Syrjälä
2005-03-02 7:53 ` Benjamin Herrenschmidt
2005-03-02 14:42 ` Torgeir Veimo
2005-03-02 16:32 ` Vladimir Dergachev
2005-03-02 17:09 ` Jon Smirl
2005-03-02 17:15 ` Vladimir Dergachev
2005-03-02 17:30 ` Jon Smirl
2005-03-02 17:45 ` Vladimir Dergachev [this message]
2005-03-02 17:51 ` Jon Smirl
2005-03-02 19:45 ` Vladimir Dergachev
2005-03-02 18:08 ` Eric Sellers
2005-03-02 19:06 ` Jon Smirl
2005-03-02 17:29 ` James Simmons
2005-03-02 22:38 ` Benjamin Herrenschmidt
2005-03-03 0:04 ` James Simmons
2005-03-02 23:42 ` Benjamin Herrenschmidt
2005-03-03 1:03 ` Vladimir Dergachev
2005-03-03 2:23 ` Benjamin Herrenschmidt
2005-03-03 3:01 ` Vladimir Dergachev
2005-03-03 7:55 ` Ville Syrjälä
2005-03-03 15:12 ` Vladimir Dergachev
2005-03-03 22:47 ` Benjamin Herrenschmidt
2005-03-03 22:08 ` Benjamin Herrenschmidt
2005-03-04 13:18 ` Ville Syrjälä
2005-03-04 22:35 ` Benjamin Herrenschmidt
2005-03-05 6:30 ` Ville Syrjälä
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.62.0503021242370.15365@node2.an-vo.com \
--to=volodya@mindspring.com \
--cc=dri-devel@lists.sourceforge.net \
--cc=esellers@users.sourceforge.net \
--cc=jonsmirl@gmail.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).