Jump to content

SKayser

Members
  • Posts

    8
  • Joined

  • Last visited

Reputation Activity

  1. Like
    SKayser reacted to tkaiser in H6 boards: Orange Pi One Plus, Orange Pi 3 Plus and Pine H64   
    Nah, but let's try another 'joke'. Can you imagine how the lower PCB side of the new small Xunlong H6 boards might look like if checking the size of a mPCIe Marvell SATA controller and OPi One/Lite:

     
    (disclaimer: I've really no idea what Xunlong is planning, just a thought since H6 has PCIe so why not trying to expose the interface? Maybe just routing/preparing the 52 pins and not soldering the connector by default?)
  2. Like
    SKayser reacted to tkaiser in armv8 boards comparison and benchmarks   
    Unfortunately these are numbers without meaning. Sysbench can be used to heat chips but not to measure performance of different hardware, especially not in your mode. Details: https://forum.armbian.com/index.php/topic/1748-sbc-consumptionperformance-comparisons/
     
    It should also be noted that potential throttling has to be monitored, that OPi PC 2 with the crappy BSP based OS image you used is limited to 1008 MHz and that RPi is cheating on you since cpufreq sysfs nodes lie (they report 1200 MHz even when the CPU cores run only with 800 MHz)
     
    CPU wise A64 and H5 should perform identical and RPi when using ARMv8 code should be slightly faster. Apart from that it's all about settings and use cases so these passive benchmarking approaches producing some numbers are always useless anyway
  3. Like
    SKayser got a reaction from tkaiser in Driver for ili9163 TFT for the 3.4 sunxi kernel   
    Hello,

    since my good friend and favorite tinkerer Olgierd wanted to run this 

    http://www.ebay.com/itm/1-44-Red-Serial-128X128-SPI-Color-TFT-LCD-Module-Display-Replace-Nokia-5110-LCD-/262136737086?hash=item3d08912d3e%3Ag%3AwyQAAOSwoydWoYhX

    on his OPi, but the drivers aren't in the 3.4 kernel I did that

    https://github.com/SvenKayser/Sambooca-Kernel-H3/commit/3511b0d142f4632f77cd1d82bae08bc584f54805.patch

    It isn't art, but it's working (or so he said). Alright, there seems to be a timing issue when loading the module for the first time.... 

    Feel free to use it to your repo if you feel like using it.

    Regards
    Sven
  4. Like
    SKayser got a reaction from Christos in dirtyCOW fix for 3.4.112   
    Hello,

    I attempted to port the dirty COW fix (https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=19be0eaffa3ac7d8eb6784ad9bdbc7d67ed8e619) for 3.4.112, and came up with this: https://github.com/SvenKayser/Sambooca-Kernel-H3/commit/543472582a6adcef12fae4ad11da72a62f29fb74.patch

    Apparently it solves the issue, but to be sure maybe some of you guys can give it a test. If it checks out please do commit it in the right places for Armbian - which I wouldn't know (Armbian has so many kernel patch folders, I don't wanna mess things up)

    Regards

    Sven
  5. Like
    SKayser got a reaction from Igor in dirtyCOW fix for 3.4.112   
    Hello,

    I attempted to port the dirty COW fix (https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=19be0eaffa3ac7d8eb6784ad9bdbc7d67ed8e619) for 3.4.112, and came up with this: https://github.com/SvenKayser/Sambooca-Kernel-H3/commit/543472582a6adcef12fae4ad11da72a62f29fb74.patch

    Apparently it solves the issue, but to be sure maybe some of you guys can give it a test. If it checks out please do commit it in the right places for Armbian - which I wouldn't know (Armbian has so many kernel patch folders, I don't wanna mess things up)

    Regards

    Sven
  6. Like
    SKayser reacted to ChrisK in U-Boot patch to use uEnv.txt instead of boot.scr   
    Hi,
     
    attached is a patch for U-Boot (should work on 2016.09-rc1 and 2016-09-rc2-dirty, will probably work on older ones as well) that makes it use the plain text file uEnv.txt instead of boot.scr, which has to be translated to a binary file first. This way changing the environment means only editing a text file, instead of editing a file, converting it to binary, and copying it over to the /boot partition on the SD. This becomes active if the U-Boot config has the option OLD_SUNXI_COMPAT disabled (in the menuconfig this is under ARM architecture -> Enable workarounds for booting old kernels).
     
    It also adds a small patch to board/sunxi/board.c to skip the setting of the MAC address if the option CONFIG_CMD_NET is disabled. That way it is possible to leave out networking stuff and save some time at boot because it doesn't init the networking stuff. Personally i prefer a boot that is as quick as possible, because i just hate it to wait for no useful reason On my board it basically just falls through to immediately boot the kernel after power-up, because i have the wait time for user-input disabled as well in the config.
     
    As an example, this is what my uEnv.txt looks like, i have reserved a core and incresed the loglevel:
    machid=1029 bootm_boot_mode=sec bootargs=console=ttyS0,115200 noinitrd root=/dev/mmcblk0p2 rootfstype=ext4 rootwait loglevel=7 isolcpus=3 bootcmd=load mmc 0 0x43000000 script.bin; load mmc 0 0x40008000 uImage; bootm 0x40008000 Greetings,
     
    Chris
     
    0000-use-uEnv.txt-by-default-on-sunxi.patch.gz
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines