Jump to content

Nofan Tasi

Members
  • Posts

    74
  • Joined

  • Last visited

Posts posted by Nofan Tasi

  1. 15 hours ago, pszab said:

    Dont know anything. That's why i asked. And as I know s912 supports x265 encoding by hw.

    Reason why I asked is: one can find which libraries, for example, ffmpeg uses and then see if any of these are known to be responsible for the hw encoding.

    For example on my amd64 desktop with nvidia hw acceleration, the library is 'vdpau' and ffmpeg uses it.

    gentoo@desktop ~ $ lddtree $(which ffmpeg) | grep vdpau
            libvdpau.so.1 => /usr/lib64/libvdpau.so.1

    But for arm64 I actually do not even know if the graphics is nvidia, I guess it is arm. Perhaps 'mali' But then my ubuntu and gentoo ffmpeg do not use it

    (ubuntu) root@minimx-g:~# lddtree $(which ffmpeg) | grep -i mali
    (gentoo) minimx-g ~ # lddtree $(which ffmpeg) | grep -i mali

    The ubuntu arm64 ffmpeg does use vdpau but I kind of doubt if that is proving anything.

  2. 38 minutes ago, balbes150 said:

    Hi Marc.

    S905 works well for the main kernel 4.11\4.12 (and thus the images collected on these branches, in such images as the title indicated 4.11). It has support for USB to S905 and running HDMI and wired network.

    They have the opportunity to use MALI.

     

    Thanks Oleg,

    Which .config do you recommend for main kernel 4.12 ?

    Would the config-4.12.0-next-20170516+ I found in the Armbian (Test\20170516+) first partition be fine or do you propose another one?

    Have a nice day.

  3. 1 hour ago, balbes150 said:

    The new version of images Armbian (Test\20170519) kernel 4.9.26 models S905X and S912. In these images works HDMI USB network.

    Great to have HDMI USB networking 4.x kernel working!

    Is there a technical reason why model S905 is not included?

    I suppose the code is from amlogic branch in your kernel repository, right?

    I also see kernel 4.12.0-next in Armbian (Test\20170516+) ... can you tell something about it?

     

  4. I notice in first boot partition following files are present (after I added s905_autoscript and dtb.img)

    # ls -alrt
    total 15876
    drwxr-xr-x 50 root root     4096 Mar 18 19:43 ..
    -rwxr-xr-x  1 root root 16073280 May  2 13:59 uImage
    -rwxr-xr-x  1 root root    18053 May  2 13:59 meson-gxbb-vega-s95-telos.dtb
    -rwxr-xr-x  1 root root    18049 May  2 13:59 meson-gxbb-vega-s95-pro.dtb
    -rwxr-xr-x  1 root root    18049 May  2 13:59 meson-gxbb-vega-s95-meta.dtb
    -rwxr-xr-x  1 root root    18928 May  2 13:59 meson-gxbb-p201.dtb
    -rwxr-xr-x  1 root root    18992 May  2 13:59 meson-gxbb-p200.dtb
    -rwxr-xr-x  1 root root    18650 May  2 13:59 meson-gxbb-odroidc2.dtb
    -rwxr-xr-x  1 root root    19028 May  2 13:59 meson-gxbb-nexbox-a95x.dtb
    -rwxr-xr-x  1 root root      935 May  2 17:15 s905_autoscript
    -rwxr-xr-x  1 root root    20728 May  2 17:15 dtb.img
    drwxr-xr-x  2 root root    16384 May  2 20:53 .

    Is that correct amount of files?

    I ask because usually I also see files like (with kernel version appended)

    zImage
    aml_autoscript
    initrd.img
    config
    System.map

    Just to be sure ...

  5. 3 hours ago, balbes150 said:

    Test versions images (20170401) server and mate  kernel 4.10.8. When run from SD card the system starts up and allows you to log in through the console UART. Network and USB does not work yet. Error with the eMMC. Note that these images are for experienced users only, if you would be willing to help with debugging and testing.

     

    congratulations, looking forward to run latest linux kernel on amlogic

  6. 5 hours ago, diaamant said:

    Unfortunately, everything is very simple.
    The library libmali.so is in the folders at: buildroot/package/opengl/src/lib/arm64/r6p1
    There are folders:
    m450
    m450-x
    And there are no folder for T8xx

    And assembly buildroot with opengl for S912 is interrupted with the inscription:
    cp: cannot stat '/home/buildroot-openlinux-20170310/output/mesongxm_q200/build/opengl/lib/arm64/r6p1//*.so*': No such file or directory

     

    For the active use of Linux, the acquisition of S912 seems so far too early ... IMHO

    S905x at the moment is the most ..

    You could perhaps attempt to continue assembly by linking, say

    ln -s m450/libMali.so /home/buildroot-openlinux-20170310/output/mesongxm_q200/build/opengl/lib/arm64/r6p1

    I recall I did something similar for S905x.

     

  7. 5 minutes ago, diaamant said:

    During the compilation, was built a file: mali.ko, Which is placed in the file system /output/target  In folder /lib/modules/3.14.29/kernel/amlogic/gpu

     

    gpu r6p1 Installing to target

     

    In folder buildroot-openlinux-20170310/output/mesongxm_q200/build created folder /gpu-r6p1

     

    That's nice. It seems 4.9.4 does not provide this module (yet).

  8. 10 minutes ago, gnthibault said:

    I was finally not able to build:

     

    RuntimeError: Bad magic number in .pyc file
    /home/tnotargi/projects/S912/buildroot/buildroot-openlinux-20170310/output/mesongxm_q200/build/uboot-next-2015-dev/Makefile:927: recipe for target 'boot.bin' failed

     

    How can I debug this, and eventually remove the package that generated the error  ?

     

     I get similar error when I build in gentoo.

    But when I build same way inside a minimal ubuntu chroot all goes fine.

    Not sure how to troubleshoot this. Perhaps python 2.7 is required.

    If I google "RuntimeError: Bad magic number in .pyc file", I do get a lot of hits.

     Which linux distribution do you use? And which python version?

    My gentoo has python 3.6 selected active. The ubuntu chroot has python 2.7 selected active

     PS: I built mesongxl_p212_kernel49.

     

     

  9.  

    1 hour ago, balbes150 said:

    Compiled a test version of Ubuntu server-4.9. Want to try - website catalog test\4.9 . Note that you need to download another dtb file and add the media with the name of the dtb.img. Monitor not working yet, but you can connect over the network via SSH or through the console UART. I checked the work on s905x, the network is working SSH, you can manage the system.

    p.s. Who is interested in the kernel sources - I GIT s905 in the thread "test".

     

    Thanks a lot for the update.

    openlinux.amlogic mentions:

    Note: xxxx_kernel49_release is under development , and not completed yet.

    so it is very cool you get it to work.

    I just finished to build buildroot and kernel (for using in gentoo) myself,

    but I guess without monitor I may need some more patience to enjoy fully :-)

    questions:

    - in your /boot I see android linux.img ... Is that file needed for armbian?

    - are other files like aml_autoscript and s905_autoscript etc... fundamentally different from, say the 3.14.29 ones?

    note:

    I see no mali.ko in /lib/modules (not in my build either).

     

  10. 57 minutes ago, gnthibault said:

    Is someone able to follow the instructions given at http://openlinux.amlogic.com/wiki/index.php/Arm/Buildroot/buildroot-3.14/buildroot-2017-03-10 ?

    The ssh command ask me for a password, so I am stuck right now.

    I would like to see if I can build my own mini distribution from scratch with a recent kernel, and all driver support from AmLogic through the builroot project they provide.

     

    It seems transition to repo correctly is imminent,  but for now one can still download from

    http://openlinux.amlogic.com:8000/download/ARM/filesystem/buildroot-openlinux-20170310.tar.gz

    Then one can go from step:

    % source buildroot/build/setenv.sh

    no password needed.

    I am doing this right now...

     

  11. about building the amlogic buildroot : is it as simple as say

    make  <my>_defconfig
    e.g.
    make mesongxb_p200_defconfig
    make

    Or does one have to tweak every single option in config ?

    So what would be a good config for s905(x) or s912 ?

  12. I am compiling natively directly from the GT1, ubuntu xenial mate desktop 5.26 image from Balbes150.yandex, as it was booting fine, with X, I tried just to re compile the kernel on Balbes git in order to add bluetooth to brcmfmac but there's something wrong with mpi-internal.h and mpi-inline.h from the compiler point of view ...

     

    gcc is 5.4 on this image, perhaps this is the problem ? (shoud I try with 4.9.4 ? )

     

    @pel.hu : with Android AP6255 firmwares, I can see 5Ghz networks (didn't try to connect to as that's my neighbours ones, but I can see them)

    try 4.9.4

×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines