• Content count

  • Joined

  • Last visited

About Myy

  • Rank
    Elite member

Contact Methods

  • Website URL

Profile Information

  • Gender
    Not Telling
  • Interests

Recent Profile Visitors

644 profile views
  1. Hmm, the usb driver seems to be whining about missing regulators so there might be a few things to check here. Or maybe it's a red herring. Wasn't the q8 kind of similar to "MiQi" devices ? If you temporarily swap the MiQi DTS with the q8 DTS, do you have USB devices enabled ? If yes, does the same bug happen ? Also, if you shorten the following sections from : &usb_host0_ehci { reg = <0x0 0xff500000 0x0 0x20000>; resets = <&cru SRST_USBHOST0_PHY>; reset-names = "phy-reset"; status = "okay"; }; &usb_host1 { pinctrl-names = "default"; pinctrl-0 = <&usbhub_rst>; resets = <&cru SRST_USBHOST1_PHY>; reset-names = "phy-reset"; status = "okay"; }; to &usb_host0_ehci { status = "okay"; }; &usb_host1 { status = "okay"; }; Does it work better ?
  2. Could you provide your dmesg logs ? Also, what's the issue with the USB ports exactly ? They just don't work or is it more subtle ?
  3. I2S and MiQi devices

    So Rockchip's 4.4 I2S driver works fine though ? I'll take a look at it then.
  4. I2S and MiQi devices

    Greetings, I recently had a request about testing the I2S and SPDIF output of MiQi devices and after some fiddling on this board, it seems that the Rockchip I2S + Simple-Audio ALSA driver just output nothing on the I2S TX/RX pins, at least. So was anyone able to output sound directly through the I2S GPIO pins on any RK3288 device ? Tinkerboard devices seems to use that setup and it seems to be working, but I'd like to know if that's working through the soldered Jack or the GPIO.
  5. There is no /dev/watchdog :-(

    Did you enable the Synopsys DesignWare Watchdog Driver ? Check in your .config file if DW_WATCHDOG=m or DW_WATCHDOG=y is present. It's the only watchdog driver compatible with snps,dw-wdt DTB entries. /* drivers/watchdog/dw_wdt.c */ static const struct of_device_id dw_wdt_of_match[] = { { .compatible = "snps,dw-wdt", }, { /* sentinel */ } };
  6. GPU driver?

    Are you sure the driver is installed ? I'll see if I can put a tutorial on how to install Rockchip libmali Debian packages ( ) and their Xserver ( ). Anyway, if you don't care about X11, install the libmali package and launch glmark2-es2-drm. Else, try to install the Xserver first, then the libmali package. The reason being that the official XServer glamor extension does not play well with the Mali drivers, it seems. Could you give the output of glmark2-es2-drm --debug ?
  7. GPU driver?

    Be sure to use the git version of glmark2, as Debian or Ubuntu's version of glmark2 might not have the Udev DRM node selection code. Also, be sure to execute this from a real terminal (CTRL+ALT+F1 if your keyboard is connected to the RK3288 device, or chvt 1 if you're connected through SSH). At last, try this as root in order to be sure that you don't have any issue due /dev/mali0 access rights.
  8. GPU driver?

    Ah ! Good to know ! I'll still keep it in the "To be done or documented" list, though.
  9. GPU driver?

    So, since I received my microSD correctly, I've been able to test the Tinkerboard with my kernels, using an Armbian image as a basis (along with some microSD cards), and I hit one of the bugs that were reported on my Github page. This bug triggers an endless stream or error messages which talk about the DRM driver trying to bind something through the MIPI output and failing. Which is perfectly normal since I didn't plug anything in MIPI (nor HDMI when the bug was triggered). Still, blocked the boot phase. With the original boot.scr, it seemed to trigger a quick reboot continuously, but I don't know if it's because of that bug since I got no output on the serial console when that happened with that configuration (just U-boot output, booting, and U-boot output again, ...). Switching to extlinux/extlinux.conf configuration displayed the error messages, with no reboot. Anyway, the only solution I found to sidestep the issue at the moment is to avoid adding a mipi_dsi node to the Tinkerboard DTS which... removes the MIPI DSI capabilities of the board, yeah... So, basically, I don't apply the patch that adds the mipi_dsi node to the rk3288-tinker.dts for the moment. However, if I get a touchscreen, I'll still try to see if I can enable such functionnality without triggering the same issue.
  10. rk3288 tinker: Ubuntu image not booting

    Is the CPU becoming burning hot during when it hangs ? Your issue sounds like @Tido's issue in the GPU Driver? thread. What kind of display do you use ? And also what is its resolution ?
  11. The VPU driver

    Well, after upgrading to artful, I discovered that the official FFMPEG project pulled a patch provided by LongChair which enable MPP support in FFMPEG directly... So I now need to recompile FFMPEG... On Ubuntu... I'll try to recompile ffmpeg with just h264 support for now.
  12. The VPU driver

    I've ported the new code provided by Ayaka but I still need to test it. Since I'm using a different MiQi, I have to recompile mpp (done) and mpv. The last one is posing several issues since it wants a pretty recent version of FFMPEG. I'll see whether I compile a new local version of ffmpeg of if I upgrade from Ubuntu Xenial to Ubuntu Artful to resolve this issue.
  13. GPU driver?

    Yeah, I only care about the the Direct Rendering Manager system (・ω・`;) Now, I understand everyone requests for a better documentation on how to install and use the Mali user-space binary drivers. This has been asked on my repository too, and I just started and untested draft in the Wiki of my repository, until I find a better way to format and distribute such documentation. Still, I repeat, this is untested for now.
  14. GPU driver?

    Indeed, the DRM tests are VSync'ed by default. So you'll get ~1 FPS/Hz . I got 59 on a cold boot but when using a proper power supply, it stays at 60 for most of the tests, beside crystal bunny and that ugly terrain. Note that the special X server can be installed more easily if you have you use Zesty or Arftul repositories. However, I really doubt that any Armbian people could help you if that patched X Server becomes broken. If I have the time, I'll try, once again, to use plasma-desktop + KWin Wayland/DRM with the Mali drivers and see how it goes... It will probably fail miserably though, with no useful error messages.
  15. GPU driver?

    @Tido Glad you make it through. As always, ugly terrain and crystal bunny are the most GPU intensive operations. I guess that you're screen works at 55Hz ? Anyway, scripting the Mali user-space binary drivers sound nice and all until you realize that, besides wayland (weston only I'd say), DRM (used by almost nobody currently) and fbdev (used only by mediacenter-like distros), they won't be very useful. The X11 ones require a specific X Server, or you'll get a terrific crash when X starts... Anyway, something like : mkdir -p ~/.local/lib cd ~/.local/lib wget -O for file_to_link in{,.1}{,.2}{,.1}{,.1,.1.0.0}{,.1,.1.0.0}; do ln -s $file_to_link; done echo "alias mali_exec LD_LIBRARY_PATH=\$LD_LIBRARY_PATH:`echo ~/.local/lib`" >> ~/.bashrc Might do the trick for now. This is actually untested though. This should add a "mali_exec" command that can be used like this : mali_exec glmark2-es2-drm Providing a Nvidia Optimus bumblebee-like execution mechanism.