Jump to content

Lion Wang

Members
  • Posts

    88
  • Joined

  • Last visited

Posts posted by Lion Wang

  1. 14 minutes ago, tkaiser said:

     

    See also https://forum.armbian.com/topic/5579-power-off-with-hdd-over-active-hub/?do=findComment&comment=42914

     

    This is what happens if Armbian starts to officially support a device. We as volunteers explain in our spare time to Banana Pi customers why/how their hardware is flawed and how to workaround these hardware issues. And at the same time the responsible company repeats the same 'design decisions' just to trick their customers into believing RPi compatibility so that will continue over and over again. Only solution: raise awareness about hardware and company issues (the guy plagued by ignorance only recognizes as 'tkaiser attacking us').

     

    And now let's stop. Working on these SBCs should be fun if one is not paid (as it applies to all of us devs here). And with SinoVoip it's NO FUN AT ALL.

     

     

    orange pi is a perfect product ??, not any defect ??? they have complete product information service??? and write all right doucments??? 

     

    Why didn't you attack them???, why ,why .............What makes you lose basic justice??? And then you understand why I ignore you.  You even send email to our customers to let our customers choose orange PI.

     

     

  2. 12 minutes ago, lvmc said:

    @tkaiser and @Lion Wang it is time to put an end point on this "fight".

     

    In my option, things are getting too aggressive and boring from both sides and it is not good for both the Armbian community and SinoVoip business.

     

    @Lion Wang the community & customers are not satisfied with the information you are providing about your products. As CEO you have to listen and act as soon as possible to correct what is wrong.

     

    @tkaiser you are essential for Armbian community, but it has been useless to read your posts about SinoVoip.

     

    My suggestion is to give the last official chance for SinoVoip with Armbian community. I suggest to port Armbian to BPI ZERO and during the porting process both sides tell everything about what is not going right or hasn't been done right. Documentation is not good? SinoVoip will fix it. We need some detailed information about the hardware? SinoVoip will provide it... and so on.

     

    Let's do it, guys?

     

    We all want to build an ecosystem between hardware and software and a friendly community.

    I'm sorry, I just can't stand the continuous attacks from tkaiser in recent years. I will continue my work and try to make everything better.

    I've always had a lot of respect and admiration for the work that the armbian community has done, and they're a group of great people.I also want to have a better cooperation.

  3. 1 hour ago, tkaiser said:

    Me neither, so what are we talking here about? If providing wrong information is part of SinoVoip's business strategy while providing correct information is most basic requirement for 3rd parties supporting their hardware... well, do you get the mismatch?

     

    you don't work for SinoVoip,but your actions justify your working for someone else.

  4. Image
    ---------------------------
    New test images(kernel and root.squashfs) are available:
    http://pan.baidu.com/s/1nuXrUTb

    How to program both uImage and root file system
    ----------------------------
    1. Copy both uImagelede and root.squashfs to tftp server

    2. Run below command to program uImagelede
    >     tftp 84000000 uImagelede
    >     mmc dev 0
    >     mmc write  84000000 1000 6000

    3. Run below command to program root.squashfs to EMMC:
    >     tftp 84000000 root.squashfs
    >     mmc dev 0
    >     mmc write 84000000 20A00 6000

    4. Run command: boot

    5. Configure an available IP address and then run below commands when entering OS
    >     opkg update
    >     opkg  install luci-theme-bootstrap
    >     opkg  install luci-mod-admin-full

    6. Connect R2 board via web

     

    Ledeweb.png

  5. I've test the AP mode, find it works fine, please follow my steps to enable it.

    Firstly please install Ubuntu 16.04 image, and then:

    1,Remove pkg wpasupplicant(apt-get remove wpa_supplicant) if you're using Ubuntu 16.04 image

    2,Comment out echo 1 > ${{WIFI_DEV} in /etc/init.d/wifi_enable if you're using Ubuntu 16.04 image

    3,Reboot

    4,Run command "echo A >/dev/wmtWifi"

    5,Run comand : hostapd -dd -C /etc/hostapd/hostapd.conf

     

    Below is an example of hostapd.conf:

     

     hw_mode=g
     interface=ap0
     driver=nl80211
     channel=1
     auth_algs=1
     ssid=test

    Also the patch @BitMaster provided is delivered to github. Thanks a lot, BitMaster. https://github.com/BPI-SINOVOIP/BPI-R2-bsp/commit/219be3221aadb2d316557df8064bb231ca46ed51

  6. 51 minutes ago, Jens Bauer said:

    I've seen that Armbian support for ExpressoBIN is on its way.

    The CPU on this board is made by Marvell, who are experts in high-performance CPUs and buses (SATA, PCIe, ...)

    Personally I expect this board to be a great choice for a NAS, but as this board has the exact same problem as Lamobo-R1 (the 'LAN' and 'WAN' Gbit ports are bridged), it's not a good choice for a router+firewall unless you add a WAN port on the MiniPCIe and keep the 3 bridged switch-ports on the LAN side.

     

    so are you like BPI-R2 ???

     

    BPI-R2 Interface.JPG

  7. 1,BPI-M2+ ,just HDMI , you need use HDMI to VGA accessories line to let it support VGA.  Just BPI-M1 with VGA and HDMI port.

     

    2,about H2+,H3,H5 chip , all is PIN to PIN compatibility, to support your project ,more support is about software support.

     

    3,this is open source project ,you can get all design documents. we can support you.

     

    4, armbian have do a good work for support allwinner H3 chip.:)

     

     

     

     

     

  8. Read that 4.14 will have additional ARM Board Support including some Banana Pi products ..

    Among the new ARM boards supported are for the Beaglebone X15 Rev C (TI AM57xx), Raspberry Pi Zero W, D-Link DIR-685 router (Gemini-based), Banana Pi R2 (MT7623), Cubietruck Plus, Banana Pi M3/M2M/M64, NanoPi A64, A64-OLinuXino, Pine64, Rockchip RK3328 Pine64/Rock64 support, ZTE ZX296718 PCBOX Board, and others.

     

    link: 

    https://www.phoronix.com/scan.php?page=news_item&px=ARM-Hardware-Linux-4.14

  9. 5 minutes ago, tkaiser said:

    There you find the iperf numbers, the poor SATA performance, R2 suffering from the same problem as R1 and also people desperately asking for SinoVoip's most hidden secret: their proprietary battery connector they don't want you to use.

     

    We're just documenting some of the real data that we've gotten in the development process.Let everyone have a reference, also hope more help us to test.:)

    The test of hardware performance is sometimes very much related to the test environment, and we try our best to test our overall hardware performance to meet the requirements of chip design

  10. we test  a SAMSUNG SSD DISK, the Read/Write performance are below:

    (1) Read from disk: 230MB/s (command: dd if=/dev/sda of=/dev/zero bs=1M count=10240)

    (2) Write to disk: 192MB/s (command: dd if=/dev/zero of=/dev/sda bs=1M count=1024 oflag=direct)

  11. Below is the performance of IP forwarding over GMACs(eth0 and eth1):

    Single direction flow

    59b7a41f69edf_eth0test.png.ef90a505bd69ce7d24242b01666a99bb.png

    Bidirection flow

    59b7a43a394c5_eth1test.png.add821b3993236d3c16806d8cb565389.png

    Statistics on R2 board:
      root@LEDE:/proc/irq/70# ifconfig 
     

       eth0      Link encap:Ethernet  HWaddr EE:86:59:C8:EB:3A  
                  inet addr:192.168.1.1  Bcast:192.168.1.255  Mask:255.255.255.0
                  inet6 addr: fe80::ec86:59ff:fec8:eb3a/64 Scope:Link
                  UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
                  RX packets:26822854 errors:0 dropped:0 overruns:0 frame:0
                  TX packets:37617944 errors:0 dropped:0 overruns:0 carrier:0
                  collisions:0 txqueuelen:1000 
                  RX bytes:35021520367 (32.6 GiB)  TX bytes:49849909918 (46.4 GiB)
                  Interrupt:68 
        eth1      Link encap:Ethernet  HWaddr 8E:3B:FE:FC:EA:BE  
                  inet addr:192.168.10.1  Bcast:192.168.10.255  Mask:255.255.255.0
                  inet6 addr: fe80::8c3b:feff:fefc:eabe/64 Scope:Link
                  UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
                  RX packets:37621811 errors:0 dropped:0 overruns:0 frame:0
                  TX packets:26821988 errors:0 dropped:0 overruns:0 carrier:0
                  collisions:0 txqueuelen:1000 
                  RX bytes:49699772484 (46.2 GiB)  TX bytes:35127932237 (32.7 GiB)
                  Interrupt:68

     

×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines