Xer0

  • Content Count

    15
  • Joined

  • Last visited

Reputation Activity

  1. Like
    Xer0 reacted to tkaiser in Orange Pi R1   
    Update: still no schematics but some OS images and another Android source code drop dating from 2017-04-01 provided by Xunlong: http://www.orangepi.org/downloadresources/orangepiR1/2017-08-18/orangepiR1a8ec1de21ce78b0942f9be38ab.html
     
    I booted this 'Debian Server' image on a NanoPi M1 with attached RTL8152 dongle and only connected this to my network. Booted successfully with a smelly 3.4.39 kernel built on 'Apr 14 14:05:55 CST 2017' (WTF?) an OS image obviously based on loboris' work. Hopefully all relevant information collected here: https://pastebin.com/XZ5vM0df
     
    'Fortunately' bash history was not cleared so we're able to see that this here has been added to /etc/rc.local:
    dmesg -n 1 install --group=root --owner=root --mode=0644 /root/50-usb-realtek-net.rules /etc/udev/rules.d/ And this udev rule that gets installed on every boot looks like this:
    root@OrangePizero:~# cat /etc/udev/rules.d/50-usb-realtek-net.rules # This is used to change the default configuration of Realtek USB ethernet adapters ACTION!="add", GOTO="usb_realtek_net_end" SUBSYSTEM!="usb", GOTO="usb_realtek_net_end" ENV{DEVTYPE}!="usb_device", GOTO="usb_realtek_net_end" # Modify this to change the default value ENV{REALTEK_NIC_MODE}="1" # Realtek ATTR{idVendor}=="0bda", ATTR{idProduct}=="8153", ATTR{bConfigurationValue}!="$env{REALTEK_NIC_MODE}", ATTR{bConfigurationValue}="$env{REALTEK_NIC_MODE}" ATTR{idVendor}=="0bda", ATTR{idProduct}=="8152", ATTR{bConfigurationValue}!="$env{REALTEK_NIC_MODE}", ATTR{bConfigurationValue}="$env{REALTEK_NIC_MODE}" # Samsung ATTR{idVendor}=="04e8", ATTR{idProduct}=="a101", ATTR{bConfigurationValue}!="$env{REALTEK_NIC_MODE}", ATTR{bConfigurationValue}="$env{REALTEK_NIC_MODE}" # Lenovo ATTR{idVendor}=="17ef", ATTR{idProduct}=="304f", ATTR{bConfigurationValue}!="$env{REALTEK_NIC_MODE}", ATTR{bConfigurationValue}="$env{REALTEK_NIC_MODE}" ATTR{idVendor}=="17ef", ATTR{idProduct}=="3052", ATTR{bConfigurationValue}!="$env{REALTEK_NIC_MODE}", ATTR{bConfigurationValue}="$env{REALTEK_NIC_MODE}" ATTR{idVendor}=="17ef", ATTR{idProduct}=="3054", ATTR{bConfigurationValue}!="$env{REALTEK_NIC_MODE}", ATTR{bConfigurationValue}="$env{REALTEK_NIC_MODE}" ATTR{idVendor}=="17ef", ATTR{idProduct}=="3057", ATTR{bConfigurationValue}!="$env{REALTEK_NIC_MODE}", ATTR{bConfigurationValue}="$env{REALTEK_NIC_MODE}" ATTR{idVendor}=="17ef", ATTR{idProduct}=="7205", ATTR{bConfigurationValue}!="$env{REALTEK_NIC_MODE}", ATTR{bConfigurationValue}="$env{REALTEK_NIC_MODE}" ATTR{idVendor}=="17ef", ATTR{idProduct}=="720a", ATTR{bConfigurationValue}!="$env{REALTEK_NIC_MODE}", ATTR{bConfigurationValue}="$env{REALTEK_NIC_MODE}" ATTR{idVendor}=="17ef", ATTR{idProduct}=="720b", ATTR{bConfigurationValue}!="$env{REALTEK_NIC_MODE}", ATTR{bConfigurationValue}="$env{REALTEK_NIC_MODE}" ATTR{idVendor}=="17ef", ATTR{idProduct}=="720c", ATTR{bConfigurationValue}!="$env{REALTEK_NIC_MODE}", ATTR{bConfigurationValue}="$env{REALTEK_NIC_MODE}" # TP-LINK ATTR{idVendor}=="2357", ATTR{idProduct}=="0601", ATTR{bConfigurationValue}!="$env{REALTEK_NIC_MODE}", ATTR{bConfigurationValue}="$env{REALTEK_NIC_MODE}" # Nvidia ATTR{idVendor}=="0955", ATTR{idProduct}=="09ff", ATTR{bConfigurationValue}!="$env{REALTEK_NIC_MODE}", ATTR{bConfigurationValue}="$env{REALTEK_NIC_MODE}" LABEL="usb_realtek_net_end" Contents of script.bin look reasonable: led pins still PA17/PL10, mmc1_para/module_para/wifi_para (Wi-Fi), usbc0 (OTG) and dvfs_table (voltagae regulation) all match (only dram_clk seems a bit too high).
     
    In other words: If we can rely on the above script.bin contents Armbian images for Orange Pi Zero should work out of the box.
  2. Like
    Xer0 got a reaction from lanefu in [394] - media build   
    So far,
     
    i've a minimized tarball with the compiled drivers that can be installed via make. for the .deb, im still to find out how the install script determines to which subdirs one module belongs. it could be the x of x_y*.ko but nor sure
  3. Like
    Xer0 got a reaction from slinde in V4L/DVB drivers for Armbian - testers wanted   
    i've cross-compiled all possible backported drivers for legacy 3.4.112 kernel
     
    could someone who has some usb tuners or video grabbers test it?
     
    download and untar http://d-h.st/k4kZ
    cd there and run sudo make install
  4. Like
    Xer0 got a reaction from xcasex in Claim a task, set DUE date and start doing it!   
    i've succesfully compiled media_build drivers on/for Orange Pi
    could share how to circumvent the caveats if someone needs