Jump to content

jernej

Members
  • Posts

    1128
  • Joined

  • Last visited

Reputation Activity

  1. 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.
  2. 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
  3. 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...
  4. 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
  5. 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.
  6. 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.
  7. 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.
×
×
  • Create New...