[Letux-kernel] OMAP3 framebuffer woes again in letux-4.15-rc8 due to mvduin/patch/tiler-fbdev for OMAP5

[H. Nikolaus Schaller]

Hi Tomi,

> Am 18.01.2018 um 08:41 schrieb H. Nikolaus Schaller <hns at goldelico.com>:
> 
> Hi,
> 
>> Am 18.01.2018 um 07:59 schrieb Andreas Kemnade <andreas at kemnade.info>:
>> 
>> Hi,
>> 
>> there is again a mvduin/patch/tiler-fbdev-v3 in the letux kernel.
> 
> Yes. Matthijs was so friendly to rebase and adapt it to 4.15 so that I
> thought it would be ok to merge it back (e.g. to demonstrate latest
> Letux OS on Pyra).
> 
>> And again framebuffer applications do not work sane. Mmapping /dev/fb0 and
>> zeroing that causes trouble (Bus error or hangs) on the gta04.
> 
> Oops. Thanks for the report. I didn't notice because I am usually testing
> with X11/DRM.
> 
>> Just text on framebuffer is ok (fixed by my patch)
>> 
>> If I understand it correctly:
>> That patch series is the best we have to have proper rotation on the Pyra
> 
> Yes.
> 
>> so that is why it is in altough the author knows that it breaks things
>> (and probably also what) and therefore did not recommend to apply it
>> anywhere.
> 
> Yes. We currently have to choose between Skylla and Charybdis.
> 
> Either have
> * no solution for OMAP5 or
> * a working (but not perfect) which makes problems with the OMAP3.
> 
>> 
>> But for qtmoko we need a working framebuffer. So we need a solution.
>> 
>> But as the patch series contains as far as I can remember wrong approaches
>> it does not make sense to further hack-fix it for me. And finding out
>> bugs which somebody else knows and understands seems to be duplicated effort.
>> 
>> Please correct me if I am wrong.
> 
> You are right. But what is the solution?
> 
> a) Andreas fixes it for OMAP3 case
> b) Matthijs fixes it so that it does not influence OMAP3 and can be recommended and endorsed by him to be applied
> c) both work together
> d) we do nothing and wait that it resolves itself by upstream changes
> e) we wait until someone else (Tomi Valkainen?) independently implements proper TILER code upstream

I should have included you for direct discussion.

What is missing / has to be fixed in your opinion to integrate the OMAP5 TILER demo code written by Matthijs into mainline?

Or are you working yourself on a proper implementation?

> f) we ship different kernel binaries for every device (which is against the Letux OS idea and other Distro kernels)
> g) ???

BR and thanks,
Nikolaus Schaller

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 801 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <http://lists.goldelico.com/pipermail/letux-kernel/attachments/20180118/9c65e97f/attachment.asc>