On 17 December 2015 at 08:11, Rob Clark wrote:
> On Wed, Dec 16, 2015 at 10:52 AM, Tomi Valkeinen
> wrote:
>> Hi Dave,
>>
>> On 10/12/15 16:25, Tomi Valkeinen wrote:
>>> Hi,
>>>
>>> Here's an RFC series to fix the mess we have at the moment with
>>> omapdrm/omapfb/omapdss.
>>
>> There hasn't bee
Hi Dave,
On 10/12/15 16:25, Tomi Valkeinen wrote:
> Hi,
>
> Here's an RFC series to fix the mess we have at the moment with
> omapdrm/omapfb/omapdss.
There hasn't been any NACKs for this series, so I'd like to get this in
for 4.5.
As it's mostly on the fbdev side, I can merge this via fbdev tre
On Wed, Dec 16, 2015 at 10:52 AM, Tomi Valkeinen
wrote:
> Hi Dave,
>
> On 10/12/15 16:25, Tomi Valkeinen wrote:
>> Hi,
>>
>> Here's an RFC series to fix the mess we have at the moment with
>> omapdrm/omapfb/omapdss.
>
> There hasn't been any NACKs for this series, so I'd like to get this in
> for
On 12/11/2015 01:27 PM, Tomi Valkeinen wrote:
>
> On 11/12/15 08:14, Archit Taneja wrote:
>
>> Is it possible to make omapfb get some of the old files (apply.c,
>> overlay.c, manager.c, sysfs files etc)? It might be helpful to have git
>> associate these files with omapfb/omap_vout since they hav
On 12/10/2015 07:55 PM, Tomi Valkeinen wrote:
> Hi,
>
> Here's an RFC series to fix the mess we have at the moment with
> omapdrm/omapfb/omapdss.
>
> First, a short background on the current status. We have the following
> entities:
>
> * omapdss, located in drivers/video/fbdev/omap2/dss/. This i
On 11/12/15 08:14, Archit Taneja wrote:
> Is it possible to make omapfb get some of the old files (apply.c,
> overlay.c, manager.c, sysfs files etc)? It might be helpful to have git
> associate these files with omapfb/omap_vout since they have been the
> only users of it. After cleanups, these fi
On 10/12/15 19:00, Emil Velikov wrote:
> On 10 December 2015 at 14:53, Rob Clark wrote:
>
>> It would be nice to see omapdrm eventually using the panel framework,
>> etc. But I think copy/paste to decouple omapdrm from omapfb/vout as
>> the first step makes sense.
>>
> Moar panels/bridges :-P
On 10 December 2015 at 14:53, Rob Clark wrote:
> It would be nice to see omapdrm eventually using the panel framework,
> etc. But I think copy/paste to decouple omapdrm from omapfb/vout as
> the first step makes sense.
>
Moar panels/bridges :-P
But seriously, I think that this is the better ide
On 10/12/15 16:53, Rob Clark wrote:
> It would be nice to see omapdrm eventually using the panel framework,
> etc. But I think copy/paste to decouple omapdrm from omapfb/vout as
> the first step makes sense.
Yes, long term plans include getting rid of the omap specific
panel/encoder drivers. Bu
Hi,
Here's an RFC series to fix the mess we have at the moment with
omapdrm/omapfb/omapdss.
First, a short background on the current status. We have the following
entities:
* omapdss, located in drivers/video/fbdev/omap2/dss/. This is a driver for the
display subsystem IPs used on OMAP (and re
On Thu, Dec 10, 2015 at 9:25 AM, Tomi Valkeinen
wrote:
> Hi,
>
> Here's an RFC series to fix the mess we have at the moment with
> omapdrm/omapfb/omapdss.
>
> First, a short background on the current status. We have the following
> entities:
>
> * omapdss, located in drivers/video/fbdev/omap2/dss
11 matches
Mail list logo
