• Content count

  • Joined

  • Last visited

1 Follower

Recent Profile Visitors

248 profile views
  1. Which ones exactly? H2+ is actually H3, so you can take a look there. If you need ARM CPU registers, you can take a look at Cortex A7 user manual on ARM site.
  2. Not sure. As I said already, I wanted just understand the procedure, not change it. I remember that there was already a discussion about this on linux-sunxi google group, but I don't remember the conclusion. On the other hand, clock drivers on mainline kernel still evolve. It might even work automatically with upcoming 4.13, but please don't rely on that.
  3. TV unit is described only in A10 and R40 datasheet. Even in those two datasheets some register descriptions are missing, but they should be enough. You can find them through
  4. Sorry, no. I was never curious enough to try to change the parent clock and now I lost interest in 3.4 kernel. Maybe you can achieve something by changing drivers/clk/sunxi/clk-sun8iw7.c
  5. preview

    4.4 kernel should support it since last month or something like that (I was analyzing exactly that piece of the code), but I didn't test it.
  6. Uh, sorry for confusion, I was talking about video driver ("Nope, didn't make it. ").
  7. Nope, didn't make it. U-Boot 2017.05 was tagged few hours ago and sunxi merge is still pending. Well, at least fixes will be merged till next release for sure.
  8. Seems so. Compare this and this. Pick a place to fix it. Please note that TV out is not included in this patch. I will add it when I will have time. P.S.: It looks like this driver will be in next U-Boot release. Unfortunately, I can't say the same for fixes I sent later (they go in through different repo).
  9. Short: That is not possible. Long: Pins for LAN LEDs are dedicated to only this functionality, e.g. you can't configure them as GPIO and quick look trough datasheet didn't show any register for controlling them independently.
  10. Yes, I know. This was because DE2 itself needs DM_I2C to be enabled (not really, just to prevent warnings), so I had to do some intermediate patches which was ready few days after clocks were merged. However, pull to master for rc3 was done in between those few days when I was preparing DM_I2C patches... Now I'm really not sure if DE2 will be merged or not. One week chance
  11. That article compares F2FS and BTRFS on multiple SSDs. Here is comparison between F2FS and EXT4 on single SD card. Apple and oranges.
  12. At least here is the (temporary) solution for simplefb:
  13. I'm really not sure, since U-Boot merge process is not as strict as Linux one. They were acked a day or two before merge window closed. I know there were some complaints in the past that new, not well tested, drivers were merged in rc2 or rc3, but then someone also comment that U-Boot is getting better in adhering to guidelines.
  14. Driver is merged in U-Boot sunxi master. However, it uses different framework (DM video) than my original attempt, so there are some differences, which must be taken into account: 1. It doesn't support simplefb. It does support efifb, but that doesn't work properly on 32 bit SoCs, since nobody invested time to go trough all places where 32/64 bit differences must be taken into account. 2. It also doesn't support TV out output, but patch for that could be taken from my working branch (only plug in detection is missing - always on). 3. DVI monitors doesn't work yet, since there is no differentiation between DVI and HDMI yet. Fix for that is already sent, but I'm not sure if it will be taken in before stable is released. 4. Some compilers might produce U-Boot with non working video driver, since one variable in edid parsing code is not initialized and might contain garbage. Fix for that is also sent and I'm also not sure if it will be taken in before stable is released. 5. Resolution can't be overriden and there is no overscan handling. So 1 and 5 might be an issue for Armbian mainline images. Unfortunatelly, also patch with old driver can't be applied as-is and has to be adopted. On the bright side, I and Icenowy managed to make working DE2, TV out and HDMI DRM driver based on linux-next (Linux 4.12-rc1 material). HDMI driver supports arbitrary resolutions, but not yet audio. However, that shouldn't be too hard to do now. @zador.blood.stained, what do you think is the way to go?
  15. You mean analog audio? From what I see, everything is set correctly. Maybe you have volume set too low or even muted? TV out driver supports only NTSC or PAL resolutions, maybe you can set TV to scale picture?