jernej

  • Posts

    1033
  • Joined

  • Last visited

Reputation Activity

  1. Like
    jernej reacted to zador.blood.stained in Orange Pi Plus2E changing CPU speed?   
    Overclocking H3 based boards is an option for users who believe in rationalism and not for users who believe in marketing bullshit. So @tkaiser simply protects this forum from users that would set their boards to 1.6GHz instead of 1.2GHz just because 1.6 is higher than 1.2, and then whine that "my board doesn't work anymore", "armbian is unstable" and "armbian sucks".
  2. Like
    jernej got a reaction from wildcat_paris in Orange Pi Plus2E changing CPU speed?   
    Why don't you look at original Loboris settings then? Nobody here is comfortable to give you instructions how to shorten your board life. After all, a lot of time was spent to convince everyone that 1.6 GHz @ 1.5V hurts the chip.
  3. Like
    jernej got a reaction from zador.blood.stained in How to build kernel module?   
    Well, if you use legacy image you have this driver already included and you don't have to do absolutely anything, except fix script.bin Unless you want to have it as a module, but this will give you just additional work without any benefit. Do you by any chance want to transfer this module to mainline kernel?
  4. Like
    jernej got a reaction from manuti in Beelink X2 with armbian possible?   
    Yeah, bcmdhd driver has some strange things inside the code. It seems mandatory to have some file specified, but later on it gets replaced with correct FW name based on chip id. If you check driver source, you can see a lot of different FW file names.
  5. Like
    jernej got a reaction from Gravelrash in H3 kernel repo   
    Thanks for at least some encouragement While you (tkaiser) are absolutely focused on headless systems, others might be on desktop/graphics. So at least for them this will be interesting for a while. I will join you with maintaining desktop version shortly. If I want to make Kodi working with libvdpau-sunxi, Armbian is much nicer platform to develop on and I can help you with squashing some bugs in the meantime. Currently I'm a bit short on time, but I will contribute for sure.
  6. Like
    jernej got a reaction from lanefu in Orange Pi Lite - now available   
    Not sure if this would help. On H3 U-Boot is actually responsible for bringing up all cores through PSCI interface.
  7. Like
    jernej got a reaction from dimag0g in OpenGL on Mali GPU (BananaPi, OrangePi PC, etc)   
    You will still have problems with decoding then. GL doesn't do any video decoding, just rendering. VDPAU rendering much more efficient BTW.
  8. Like
    jernej got a reaction from Albert911 in Armbian, OrangePI (PC) and Kodi   
    Which audio output do you use? There is a bug in analog output - it says that it supports audio formats which in reality it can't, namely 24 bit audio. If you patch it (check this and this patch), sound output should work normally.
  9. Like
    jernej got a reaction from slinde in Beelink X2 with armbian possible?   
    Firmware is missing. Extract https://transfer.sh/h6nda/ap6210.tar.xzto /lib/firmware so you will have /lib/firmware/ap6210 folder. Then unload bcmdhd driver if it is already loaded and load it with following command:
    modprobe bcmdhd firmware_path=/lib/firmware/ap6210/bcmdhd.bin nvram_path=/lib/firmware/ap6210/nvram.txt NOTE: Download link will be valid only for 14 days, but until then it will be fixed, I guess.
  10. Like
    jernej got a reaction from Igor in H3 kernel repo   
    Thanks for at least some encouragement While you (tkaiser) are absolutely focused on headless systems, others might be on desktop/graphics. So at least for them this will be interesting for a while. I will join you with maintaining desktop version shortly. If I want to make Kodi working with libvdpau-sunxi, Armbian is much nicer platform to develop on and I can help you with squashing some bugs in the meantime. Currently I'm a bit short on time, but I will contribute for sure.
  11. Like
    jernej got a reaction from tkaiser in H3 kernel repo   
    Thanks for at least some encouragement While you (tkaiser) are absolutely focused on headless systems, others might be on desktop/graphics. So at least for them this will be interesting for a while. I will join you with maintaining desktop version shortly. If I want to make Kodi working with libvdpau-sunxi, Armbian is much nicer platform to develop on and I can help you with squashing some bugs in the meantime. Currently I'm a bit short on time, but I will contribute for sure.
  12. Like
    jernej reacted to Igor in Claim a task, set DUE date and start doing it!   
    [Ended]   Be active, creative, helpful and you can get a powerful board in return. First give away batch is starting 11.6.2016  
    It's not often that you can work on a software project that actually brings joy and helps people. Armbian is one of those project. It is a system that helps one build a kernel or boot images for several ARM development boards. 
     
    It's in common interest that we improve level of support and to relieve most active people. Our crew needs an upgrade:
    we need more coders, kernel hackers, UX designers to find and solve problems. If you are one of them, join our forum, join project at Github. we need properly built, packed and supported desktop with major functions: video acceleration/fbturbo, libump, mali, etc. we need to put together much better documentation. We need to fine tune MkDocs documentation tools For those who are willing to claim a task or help others to understand "how do I do this in Armbian" we prepared a dozen of boards as a small reward. It's a Xunlong Orange PI+ 2E, which design was improved based on requests from our community. It's H3 based quad core with 2G RAM, 16G eMMC, Gigabit LAN, WIFI and 3x USB.     There might be just enough boards for everyone who are willing to do some public service work. Claim your projects at this topic and each weekend we will discuss and select up to 15 people who will get the board, starting with 11.6., ... until we run out of boards. One will be notified by email and expect an answer within 48 hours, if not, board goes to somebody else.   Boards were donated and will be sent directly from Xunlong Co., Shenzhen, China.     1st batch is going to: Kriston, lanefu, vlad59, martinayotte, jeanrhum, Gravelrash, xcasex, naibmra, Xer0, madilabs, wha, @lex, WereCatf   naibmra - Bulgaria - kernel testing, try hooking to kernelci.org, docs - mid July wha - USA - 50unattended-upgrades, issue #337 - June Kriston - USA - documentation rework - July, August Xer0 - Germany - media build - July, August lanefu - USA - issue tracking improvements between forum and github - 22 June, July madilabs - Martinique - Packaging for desktop video acceleration - June xcasex - Sweden - desktop packaging - July, August jeanrhum - France - documentation and debian packaging - July martinayotte - Canada - maintain/fix DTS entries for some devices such I2C/SPI/W1 - ASAP vlad59 - France - Nanopi M1 testing and documentation Gravelrash - UK - Prepare HOWTO's & package "armbian-gc2035-fswebcam package" - June   2nd batch is going to: dimag0g, R2D2_C3PO, miked, 0x0, sysitos, jmcneill    dimag0g - France -  Packaging of OpenGL wrapper library - end of July R2D2_C3PO - Germany - Improved SD-Card partitioning - end of August miked - Canada - build system recension - end of August 0x0 - Russian Federation - Redesign site and documentation WIP + add some changes to graphics in distro. - end of July sysitos - Germany - replace/rework ramlog for systemd - end of August jmcneill - Canada - (Armbian is helping porting Freebsd)    Users were notified and were requested to provide: project name, due date and their shipping address
  13. Like
    jernej got a reaction from tkaiser in OPI LITE wireless device not working   
    You can't. Driver has some generic code but chip dependant code is only for 8189fs. AFAIK, 8189es driver, which you added today, is the latest one.
  14. Like
    jernej got a reaction from Igor in OPI LITE wireless device not working   
    You can't. Driver has some generic code but chip dependant code is only for 8189fs. AFAIK, 8189es driver, which you added today, is the latest one.
  15. Like
    jernej got a reaction from rodolfo in OPI LITE wireless device not working   
    Here is my solution for loading different wifi drivers on different boards. Basically it is just oneshot systemd service which runs a bash script. That script checks script.bin settings currently in use (there is read_fex.c source) and based on wifi settings loads appropriate wifi driver. In case of RTL8189FS it also checks for saved mac address and pass it as an argument or it creates a random one and saves it. Paths should be updated to be more appropriate for Debian.
     
    Latest RTL8189FS source is here.
  16. Like
    jernej got a reaction from gnasch in OPI LITE wireless device not working   
    Here is my solution for loading different wifi drivers on different boards. Basically it is just oneshot systemd service which runs a bash script. That script checks script.bin settings currently in use (there is read_fex.c source) and based on wifi settings loads appropriate wifi driver. In case of RTL8189FS it also checks for saved mac address and pass it as an argument or it creates a random one and saves it. Paths should be updated to be more appropriate for Debian.
     
    Latest RTL8189FS source is here.
  17. Like
    jernej got a reaction from tkaiser in OPI LITE wireless device not working   
    Here is my solution for loading different wifi drivers on different boards. Basically it is just oneshot systemd service which runs a bash script. That script checks script.bin settings currently in use (there is read_fex.c source) and based on wifi settings loads appropriate wifi driver. In case of RTL8189FS it also checks for saved mac address and pass it as an argument or it creates a random one and saves it. Paths should be updated to be more appropriate for Debian.
     
    Latest RTL8189FS source is here.
  18. Like
    jernej got a reaction from wildcat_paris in How to build my own image or kernel?   
    Yes, Igor, in order to build sun8i on non x64 host machines, this patch should be included: https://github.com/jernejsk/OpenELEC-OPi2/blob/openelec-7.0/projects/H3/patches/linux/linux-82-fix-build-on-non-amd64-hosts.patch
  19. Like
    jernej got a reaction from wildcat_paris in Prepare v5.11 bugfix update   
    What issue do you have with green led? You mean heartbeat trigger set by default? If that is so, you can take my patch...
  20. Like
    jernej reacted to Igor in Prepare v5.1 & v2016.04   
    - added already mentioned R1 patch for 4.5.x. Zador made a great job, again.
    - upgraded Guitar kernel
    - added / fixed C1. Thanks to Joe for C1 and Armbian mugs! My generic mugs has been replaced 

    - various small bugfixes
  21. Like
    jernej got a reaction from tkaiser in [WiP / Orange Pi One] Support for the upcoming Orange Pi One?   
    @tkaiser,
    I can confirm that booting from eMMC already works. Only one option is needed to be turned on in U-Boot (check my github).
     
    There is one interesting detail, though. /dev/mmcblk0 and /dev/mmcblk1 have reversed meaning for Plus, at least in OpenELEC. Usually, /dev/mmcblk0 is SD card, but for Plus this means eMMC.
  22. Like
    jernej got a reaction from tkaiser in [WiP / Orange Pi One] Support for the upcoming Orange Pi One?   
    I hope you don't mind if I join your party
     
    My fbdev patch allows changing only to already supported resolutions on the fly, but you must be aware of two things:
    1. video memory gets reserved at boot, so you can't change to resolution bigger than it was set at boot,
    2. fbset changes only framebuffer resolution info, but doesn't actually switch to it in HW - that can be done via debugfs or disp2's ioctl interface
     
    debugfs method:
    sudo su cd /sys/kernel/debug/dispdbg/ echo "switch" > command echo "disp" > name echo "4 5" > param echo "1" > start where 4 means HDMI output and 5 has the same meaning as in script.bin. For ioctl variant, which is more C friendly, you can check my Kodi patch.
     
    Also one note on your unifying attempt and gmac patch / script.bin dilemma. Please check my github for updated patch. Idea behind it is that driver doesn't fail if there is no [gmac_phy_power] section in script.bin. That way you don't need to change script.bin at all.
     
    And last but not least, if you want to use sy8106a patch on u-boot, you must update u-boot to version 2016.03-rc2.
  23. Like
    jernej got a reaction from Igor in [WiP / Orange Pi One] Support for the upcoming Orange Pi One?   
    I hope you don't mind if I join your party
     
    My fbdev patch allows changing only to already supported resolutions on the fly, but you must be aware of two things:
    1. video memory gets reserved at boot, so you can't change to resolution bigger than it was set at boot,
    2. fbset changes only framebuffer resolution info, but doesn't actually switch to it in HW - that can be done via debugfs or disp2's ioctl interface
     
    debugfs method:
    sudo su cd /sys/kernel/debug/dispdbg/ echo "switch" > command echo "disp" > name echo "4 5" > param echo "1" > start where 4 means HDMI output and 5 has the same meaning as in script.bin. For ioctl variant, which is more C friendly, you can check my Kodi patch.
     
    Also one note on your unifying attempt and gmac patch / script.bin dilemma. Please check my github for updated patch. Idea behind it is that driver doesn't fail if there is no [gmac_phy_power] section in script.bin. That way you don't need to change script.bin at all.
     
    And last but not least, if you want to use sy8106a patch on u-boot, you must update u-boot to version 2016.03-rc2.