Re: [PATCH] dma-buf: Update docs for SYNC ioctl

Hi On Mon, Mar 28, 2016 at 9:42 PM, Tiago Vignatti wrote: > Do we have an agreement here after all? David? I need to know whether this > fixup is okay to go cause I'll need to submit to Chrome OS then. Sure it is fine. The code is already there, we cannot change it.

Re: [PATCH] dma-buf: Update docs for SYNC ioctl

Hi On Wed, Mar 23, 2016 at 12:56 PM, Chris Wilson <ch...@chris-wilson.co.uk> wrote: > On Wed, Mar 23, 2016 at 12:30:42PM +0100, David Herrmann wrote: >> My question was rather about why we do this? Semantics for EINTR are >> well defined, and with SA_RESTART (default on

Re: [PATCH] dma-buf: Update docs for SYNC ioctl

Hey On Mon, Mar 21, 2016 at 6:14 PM, Daniel Vetter <dan...@ffwll.ch> wrote: > On Mon, Mar 21, 2016 at 01:26:58PM +0100, David Herrmann wrote: >> Hi >> >> On Mon, Mar 21, 2016 at 8:51 AM, Daniel Vetter <daniel.vet...@ffwll.ch> >> wrote: >> &

Re: [PATCH] dma-buf: Update docs for SYNC ioctl

ilson.co.uk> > Cc: Tiago Vignatti <tiago.vigna...@intel.com> > Cc: Stéphane Marchesin <marc...@chromium.org> > Cc: David Herrmann <dh.herrm...@gmail.com> > Cc: Sumit Semwal <sumit.sem...@linaro.org> > Cc: Daniel Vetter <daniel.vet...@intel.com> > C

Re: dma-buf/fbdev: one-to-many support

Hi Laurent and Alan On Tue, Jul 17, 2012 at 1:24 PM, Alan Cox a...@lxorguk.ukuu.org.uk wrote: The main issue is that fbdev has been designed with the implicit assumption that an fbdev driver will always own the graphics memory it uses. All components in the stack, from drivers to applications,

dma-buf/fbdev: one-to-many support

Hi I am currently working on fblog [1] (a replacement for fbcon without VT dependencies) but this questions does also apply to other fbdev users. Is there a way to share framebuffers between fbdev devices? I was thinking especially of USB devices like DisplayLink. If they share the same screen