• Content Count

  • Joined

  • Last visited


About jernej

  • Rank
    Embedded member

Recent Profile Visitors

3911 profile views
  1. No, they are disabled because nobody took time to properly enable them in board DTS until now (it will be in 5.7). No, sun4i-drm is for all Allwinner SoCs, it supports Display Engine 1.0, 2.0 and 3.0. It's just named by Linux tradition where it takes name of first (oldest) supported platform.
  2. It's completely different SoC which means that your boot attempt probably doesn't pass RAM initialization, if it even gets there. So no, you'll not see anything on the screen. I wouldn't count on UART either, since there is no guarantee it's on the same base address as on H6. Also UART related clocks may be different.
  3. @zanfi just to clear any confusion - there are multiple Tanix TX6 variants: - Tanix TX6 - Allwinner H6 - Tanix TX6 mini - Allwinner H6 - Tanix TX6s - Allwinner H616 As you can see, Tanix TX6s won't work with any image you can find, because it's using new SoC which is not supported anywhere. There are no public SDK and datasheet releases (that I know) for it, so you can't find any images besides Android from box manufacturer.
  4. If you have Pinebook in mind and the one from Olimex, they both use anx6345 IIRC. Driver for that chip was merged in kernel some time ago, but it doesn't consider "panel-supply" property. I guess that's what's wrong. @Icenowy?
  5. True, but port A and B are routed internally to AC200 co-packaged IC and not useful for outside world. Information about port A and B is not even in manual.
  6. Take a look into GPIO controller register description. You will find interrupt settings only for port F, G, H, L and M.
  7. You should send patch for that to U-Boot so next person which tries to use USB on OrangePi Win don't need to do that work again.
  8. I know, but now and then there are U-Boot changes which influence Linux. For example, I figured out that enabled display driver in U-Boot occasionally prevents Linux driver to read EDID. I could as well add unconditional HDMI reset in kernel, but then display would blink. Eventually, we will also add support for DT overlays in extlinux.conf which needs patched U-Boot, at least at first, until changes get merged upstream. Because of such things I like to keep U-Boot under control in official LE images. I have nothing against community builds which change this behaviour and enable multi-boot systems, but this is can of worms if not done correctly. I don't want to support that as official LE feature at this point.
  9. Allwinner SoCs can't boot from USB natively. So you must have SD card or eMMC to boot from anyway. But then it doesn't really matter if you load kernel and base filesystem from SD, eMMC or USB, does it? Once you booted Linux, you can use USB sticks as additional storage device.
  10. Well, there is another issue. U-Boot detected spurious key press on some keyboards, which were plugged in during boot. This caused abort of boot and clueless user thought that something is broken (there was nothing on screen). Such reports happened several times already. Besides you, nobody complained that USB support in U-Boot is missing. I think most users don't care about U-Boot, they just want that LE is booted either from SD or eMMC.
  11. I disabled USB in U-Boot because it considerably extends boot time (up to 5 seconds on some boards):
  12. OrangePi Win default configuration in U-Boot has only half drivers enabled for ethernet. I fixed that recently with It will be part of U-Boot v2020.04.
  13. AFAIK H6 USB3 is not supported yet in U-Boot, I have no idea about USB2 though. Also ethernet driver is not yet supported, although patch for boards with external PHY exist.
  14. @balbes150 I don't know much about RK and AML, but on AW most, if not all, SoCs have 3 mmc ports. SD card is always connected on first one, wifi SDIO module on second and eMMC on third. I guess that U-Boot enumerates devices in port order, so that would mean that SD card is always first device. However, another explanation would be that first device is one which you booted from - did you check that?
  15. Yes, you are missing something. Lima doesn't support video decoding. What you need is Cedrus. But using it is another story (currently a mess).