mix359

Validating
  • Content Count

    7
  • Joined

  • Last visited

  1. Sadly that is what it show even during the uboot phase. About xorg, I don't have any X server installed at the moment (to keep the dmesg a bit cleaner... with Xorg installed it was really a mess...) Do you suggest to make some other try with it installed? Thanks Cheers Mix
  2. No, I haven't tried compiling it myself, the driver is the one shipped with the 5.6.12 kernel and I'm surprise too it doesn't work... For that reason I was trying to find what I was doing wrong, but all the changes I'm doing at the moment doesn't seam to change anything on the result: the display always show a random/out of sync image and in the dmesg there always that vblank sync errors. I've also take a look at what as changed in the driver code from the version that is ship with the 5.4.x kernel and the 5.6.x and there's seam to be only refactor done massively to all t
  3. I've checked the dt patches and I've found out something interesting about the touchscreen that I was missing, but sadly even making in my dt overlay the same change, the screen still show random gray lines... and there's still the same errors in the dmesg caused by the panel_feiyang_fy07024di26a30d driver. I would like to make a little bit of debugging of that driver, but I don't know where to start debugging C code like that.... @Gavinb does the screen work to you with the patch you have done? do you have the "vblank wait timed out" error in dmesg? can I ask you
  4. I've tried something like this in my boot.cmd/boot.scr: setenv video-mode sunxi:1024x600,monitor=lcd,hpd=0,edid=1 But nothing changed... There's still the error in the dmesg and random image on the screen... Searching on the web about that message I've found this: https://patchwork.freedesktop.org/patch/334084/ This is similar to what's happening to me... but even if it have done this patch, I still get the error... Hoping that Jagan would answer to my email
  5. My daily update (hope this post limit will disappear soon) @Learnincurve Yep, you where right, there was a parameter missing in the overlay, and there wasn't any trace of the panel in the dmesg... Looking around I've found that there is a driver for the Feiyang lcd (thanks for the model information) and also an old example of dt config: https://github.com/torvalds/linux/blob/master/Documentation/devicetree/bindings/display/panel/feiyang%2Cfy07024di26a30d.txt So using that, I've created a user dt overlay to use the lcd, here's the code: https://pasteb
  6. Hi to all, Sorry but for some reason I can post only once a day... so i had to wait... I've done some other test and research. First thing, thanks to have point me to the device tree/overlay world... I've studied a bit how that work and I've decompiled the pine64+ file dtb file, to find out those paragraph: Haven't found a way to upload here, so if someone is interested, this is the decompiled sun50i-a64-pine64-plus.dts on pastebin: https://pastebin.com/nRkD0hep Searching around I've found that those two were disabled by the status = "disabled"
  7. I've flashed a 5.4 Bionic on my Pine64 (kickstarter edition) and I've switched to Nightly release & the 5.6.12 kernel, but I have no idea how to "enable" the support... (and it hasn't started working... the LCD is still off) I've tried adding both the pine64_lcd=on and the monitor=lcd row to the /boot/armbianEnv.txt (don't know if it's required) but nothing changed. Taking a first look I can't see any a64 DT overlay regarding the dsi or mipi dsi. If I search inside the "/boot/dtb/allwinner/sun50i-a64-pine64.dtb" file, I can find a reference to "sun50i-a64-mipi-ds