From mboxrd@z Thu Jan 1 00:00:00 1970 From: Gary Mort Subject: Re: SimpleFB drivers repository? Date: Tue, 15 Oct 2013 09:18:19 -0400 Message-ID: <525D409B.5030909@gmail.com> References: <525C198E.4090906@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; Format="flowed" Content-Transfer-Encoding: 7bit Return-path: Received: from mail-qe0-f45.google.com (mail-qe0-f45.google.com [209.85.128.45]) by gabe.freedesktop.org (Postfix) with ESMTP id 2B37F44BCF for ; Tue, 15 Oct 2013 06:18:29 -0700 (PDT) Received: by mail-qe0-f45.google.com with SMTP id 8so6154956qea.18 for ; Tue, 15 Oct 2013 06:18:26 -0700 (PDT) In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: dri-devel-bounces+sf-dri-devel=m.gmane.org@lists.freedesktop.org Errors-To: dri-devel-bounces+sf-dri-devel=m.gmane.org@lists.freedesktop.org To: David Herrmann Cc: "dri-devel@lists.freedesktop.org" List-Id: dri-devel@lists.freedesktop.org On 10/14/2013 1:02 PM, David Herrmann wrote: > Hi > > On Mon, Oct 14, 2013 at 6:19 PM, Gary Mort 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.