Well, as far as I can see, the community is actively working on fixing Sunxi kernel, although it seems that interest in 3.4 kernel is somehow descending. Anyway, I thought that someone would use overlay from original disp driver, which is why I posted fixes for it - same goes for CSI.
As I said before, even though everything is dirty and buggy, abstraction level is much easier to grasp in contrast with Freescale i.MX series kernels, at least for beginner/intermediate in Linux programming... And honestly, it seems that A20 is suffering from much less HW bugs than i.MX6, at least as far as I can see. On Monday, March 31, 2014 5:53:52 PM UTC+2, Siarhei Siamashka wrote: > > On Mon, 31 Mar 2014 08:33:29 -0700 (PDT) > Ivan Kozic <[email protected] <javascript:>> wrote: > > > Hi Luc, > > > > Found out why disp driver has choppy overlay - for me overlay comes > through > > DMA from memory. Funny thing - disp_malloc is fetching cached memory, so > > choppiness or "trailing" is due to caching framebuffer protected memory. > > Very silly - I found this out by changing caching method of ARM from > > WRITEALLOC to WRITETHROUGH, also waited 10 minutes for system to boot up > :) > > > > The matter is solved by adding the following line to disp_mmap() > function: > > > > vma->vm_page_prot = pgprot_noncached(vma->vm_page_prot); > > > > Solved. Just wondering how people were using this before... > > As far as I know, nobody is using these bug ridden memory allocators > that Allwinner has implemented in disp and g2d drivers. Except for > maybe Allwinner itself in their Android code. > > -- > Best regards, > Siarhei Siamashka > -- You received this message because you are subscribed to the Google Groups "linux-sunxi" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
