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

Hi David, On Tuesday 17 July 2012 14:23:18 David Herrmann wrote: > On Tue, Jul 17, 2012 at 1:24 PM, Alan Cox 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 st

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

Hi David, On Tuesday 17 July 2012 14:23:18 David Herrmann wrote: > On Tue, Jul 17, 2012 at 1:24 PM, Alan Cox 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 st

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

Hi Laurent and Alan On Tue, Jul 17, 2012 at 1:24 PM, Alan Cox 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, have been designed

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

Hi David, On Saturday 14 July 2012 16:10:56 David Herrmann wrote: > 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 thinkin

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

> 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, have been designed > around that assumption. > > We could of course fix this, revamp the

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

Hi Laurent and Alan On Tue, Jul 17, 2012 at 1:24 PM, Alan Cox 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, have been designed

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

> 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, have been designed > around that assumption. > > We could of course fix this, revamp the

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

Hi David, On Saturday 14 July 2012 16:10:56 David Herrmann wrote: > 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 thinkin

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 dim

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 dim