Re: [PATCH RFC 0/9] omapdrm/omapfb/omapdss split

[Tomi Valkeinen <tomi.valkeinen@ti.com>]

[-- Attachment #1: Type: text/plain, Size: 1145 bytes --]


On 10/12/15 19:00, Emil Velikov wrote:
> On 10 December 2015 at 14:53, Rob Clark <robdclark@gmail.com> 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

I have a bunch more in my TI branch, which I have never upstreamed
because I haven't wanted to push too much into the omap specific
panel/encoder directory...

> But seriously, I think that this is the better idea, despite the
> duplication that'll exist in the first place. Otherwise you'll end up
> pulling your hairs out trying to balance everything drm and fbdev/vout
> working.
> 
> A suggestion... do throw a big scary warning in the fbdev copy - "Here
> be dragons... old, mostly maintained code, bugfixes only please".
> Otherwise some poor soul might decide to port the drm patches back
> into the fbdev copy, or try to de-duplicate things :-)

The fbdev maintainer (me) will block any attempts to do so, but good
point, it doesn't harm to add a small README to the omapfb side.

 Tomi


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]