From: Gary Mort <garyamort@gmail.com>
To: David Herrmann <dh.herrmann@gmail.com>
Cc: "dri-devel@lists.freedesktop.org" <dri-devel@lists.freedesktop.org>
Subject: Re: SimpleFB drivers repository?
Date: Tue, 15 Oct 2013 09:18:19 -0400 [thread overview]
Message-ID: <525D409B.5030909@gmail.com> (raw)
In-Reply-To: <CANq1E4TMsEO0a3=Q_DzR4Cu-ZK-y=VUODu0hu3a5HDSQ3osF0Q@mail.gmail.com>
On 10/14/2013 1:02 PM, David Herrmann wrote:
> Hi
>
> On Mon, Oct 14, 2013 at 6:19 PM, Gary Mort <garyamort@gmail.com> wrote:
>> Is there a repository for the SimpleFB drivers[the DRI driver and the plain
>> framebuffer driver]?
> Which drivers are you exactly talking about? Do you have links to the
> patches? There're several independent projects called "simplefb". If
> you're talking about the simplefb fbdev driver, it's developed
> upstream and available since linux-3.10 (linux-fbdev@vger.kernel.org
> ML). SimpleDRM is developed on this list and still experimental.
> There're no "upstream" repositories just for the drivers. Patches on
> the ML is all there is.
Thanks, it was both of those I was looking for[the one that has been
upstreamed and the DRI one]
I want to use simplefb and the USB webcam gadget to create a USB display
solution - similar to DisplayLink but entirely opensource.
The UVC standard supports streaming in framebuffer mode - and some of
the standard transmission methods have compression options - as well as
allowing for 'vendor defined' formats - so rather than having to reverse
engineer proprietary displaylink compression methods - I prefer to use a
complete open source solution.
simplefb looks like a good fit since it allows me to define the memory
region for the framebuffer to use - so if I can initialize that in the
videobuffer it cuts down on memory copies.
prev parent reply other threads:[~2013-10-15 13:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-14 16:19 SimpleFB drivers repository? Gary Mort
2013-10-14 17:02 ` David Herrmann
2013-10-15 13:18 ` Gary Mort [this message]
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=525D409B.5030909@gmail.com \
--to=garyamort@gmail.com \
--cc=dh.herrmann@gmail.com \
--cc=dri-devel@lists.freedesktop.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.