jernej

MAC address is generated based on SID in U-Boot. This is something like eFuse and calibration register. It should be unique number, but because of HW bug it was not (mostly zeros) if you directly read it first time. Latest U-Boot has fix for that, you can refer to #linux-sunxi log and mailing list if you want technical details. Of course, this fix influenced MAC address.

Please check this two topics before: https://forum.armbian.com/index.php/topic/2991-opi-pc-2e-h3disp-1680x1050-dvi-display-issues/?p=23425 https://forum.armbian.com/index.php/topic/3407-orange-pi-2-custom-resolution-problem/ And then ask specific questions.

Be aware that simplefb driver in dev version has a lot of limitations - no double buffering, no resolution switching, no power management, no HDMI sound, etc.

Regarding the patch: - don't change hdcp_enable variable Why do you want HDMI encryption enabled? It can only bring troubles - you missed few places - it would be better to add new mode instead of changing existing one For proper addition please check this patch: https://github.com/igorpecovnik/lib/blob/master/patch/kernel/sun8i-default/z-0003-add-additional-video-modes.patch Regarding script.fex: - hdcp_enable should be 0 - tv_used should be 0 (if HDMI and TV out are enabled at the same time, artifacts on HDMI might appear) - screen1_output_type and screen1_output_mode should be 0, they are used only for TV out

CEC driver is missing. jodamm was kind enough to implement it (https://github.com/jodamm/linux/tree/sun8i) based on his own research without any documentation, which means that it might not be 100% reliable. You will have to rebuild kernel, but that it is easy to do once you have the patches. Unfortunatelly, I'm not sure if you can easily take jodamm's patches and apply it to Armbian kernel sources. But don't be afraid, I'm pretty sure not much fixing is needed.

Please provide full script.bin & kernel changes. dmesg output shows that script.bin might be misconfigured.

No, I don't, because I happily use already present IR receiver on Oranges (same chip). Maybe someone else can help you.

Why do you expect that it will be completely the same as with Raspberry? They have completely different chips with nothing in common, not even the CPU cores. I said that 10k pull-up should be there for receiver, I don't know why did you remove it. If you are really desperate to use same driver as on Raspberry Pi, then you will have to do dirty work of making driver H3 compatible. Please read whole thread: https://forum.armbian.com/index.php/topic/1288-opi-pc-with-lirc-ir-transmit/?p=24200 Still, you didn't answer why do you need this if not for receiver (IR RX).

Actually, ir_rx is not used anywhere, because PL11 is the only pin which supports HW IR receive. Which mode you need then? TX? It is not supported by HW. P.S. This driver doesn't use HW unit, you should use sunxi_cir (or something like that, I can't check in this moment) for pin PL11 AFAIK, RPi doesn't have HW IR support. Driver emulates this functionality through GPIO and external interrupts. Some people already fiddle with it, but I did not hear any success story. I'm not sure if those people actually understand what they were doing. One of the prerequirements is that pin must support external interrupt. I never bothered to try to make it work on a GPIO if HW IR on PL11 work flawlessly on basically any Orange and should on any other board too. There are some who managed to hand solder it to One and it worked. According to Orange Pi PC Plus schematic that 10k pull up is ok for IR. Just add 33R resistor between 3.3V and IR receiver power pin and decoupling capacitor and you should be fine. I still don't understand why you are so determined to use it on another pin.

You want stability under stress, so...

Ah, ok, then I can't really help you because I'm not familiar with Linux Extension Plugin.

It has a possibility, but it doesn't include IR by default, whereas other boards do. I was talking about schema from which you can clearly see how to properly connect IR.

Can't tell if you don't provide exact part name and how is it connected to the board. No, PL11 pin is the only one which supports IR RX mode. Pull-up/-down resistors are usually external, which means that you need to add it if applicable. Check schematic for any OrangePi board with IR (all of them except zero)

Please provide full command. Did you forget -lpthread ?

There is no need to do that, unless you load sunxi-gpio driver but AFAIK nobody use it, even Allwinner removed it from newer BSP kernels.

If I understand you correctly, you didn't try it yet? Because the driver should select native screen resolution, in this case 1080p. If it is not, then it is bug. H5 doesn't have any HW 2D acceleration, only 3D through mali. For this you need DRM driver. Maybe something can be done with H3 experimental one, but let's focus on basics first.

Everything you calculated is correct, but IIRC only first few entries are taken into account. Change ir_power_key_code0 & ir_addr_code0, for example.

Addition: Pin should be pulled up to 3V3 and when you want to wake it up, you have to connect pin to GND. Check schematic for any other board, which has power button.

What do you mean by kernel config? I tested this actually on OpenELEC on multiple boards, kernel 3.4.113, but there is no reason that it shouldn't work on legacy Armbian. Be aware that USB hubs for some reason break suspend procedure. Command for go to sleep: systemctl suspend

Can you please join the discussion: https://irclog.whitequark.org/linux-sunxi/2017-01-25#18706221;

Ah, I again misread your OP, sorry. So, if you want to wake-up by GPIO, then you have to specify wanted pin in FEX. Find something like: [wakeup_src_para] wakeup_src_bt = port:PL03<6><default><default><0> You can add some wakeup_src_* entries here. Full name of the entry doesn't matter, but it must start with "wakeup_src_" You have to reboot before it will take an effect. I saw USB mentioned as wake up event, but I'm not sure how to set it up.

ah, sorry, you mean OPi Zero... Then be sure to connect IR receiver to PL11, otherwise it won't work. ARISC know to use only dedicated IR pin. I believe OPiZero hat use it, but I'm not sure.

OrangePi forum has full instructions: http://www.orangepi.org/orangepibbsen/forum.php?mod=viewthread&tid=2048&extra=page%3D1 You could use exactly the same principle, except, obviously, path will be different.

Once SoC is supported, adding new boards should be easy. But first, please wait until RK3288 is supported in Armbian.

You can choose only PAL or NTSC for TV out. Neither of those offer 800x480 resolution.