150balbes / jetson-nano Goto Github PK

Kernel Jetson Nano

License: Other

Makefile 0.29% C 97.71% Assembly 1.54% C++ 0.03% Shell 0.06% Perl 0.23% Awk 0.01% Python 0.07% Yacc 0.02% Lex 0.01% UnrealScript 0.01% Gherkin 0.01% XS 0.01% Roff 0.01% Clojure 0.01% M4 0.01% sed 0.01% SmPL 0.01% Raku 0.01% GDB 0.01%

jetson-nano's Introduction

        Linux kernel release 4.x <http://kernel.org/>

These are the release notes for Linux version 4.  Read them carefully,
as they tell you what this is all about, explain how to install the
kernel, and what to do if something goes wrong.

WHAT IS LINUX?

  Linux is a clone of the operating system Unix, written from scratch by
  Linus Torvalds with assistance from a loosely-knit team of hackers across
  the Net. It aims towards POSIX and Single UNIX Specification compliance.

  It has all the features you would expect in a modern fully-fledged Unix,
  including true multitasking, virtual memory, shared libraries, demand
  loading, shared copy-on-write executables, proper memory management,
  and multistack networking including IPv4 and IPv6.

  It is distributed under the GNU General Public License - see the
  accompanying COPYING file for more details.

ON WHAT HARDWARE DOES IT RUN?

  Although originally developed first for 32-bit x86-based PCs (386 or higher),
  today Linux also runs on (at least) the Compaq Alpha AXP, Sun SPARC and
  UltraSPARC, Motorola 68000, PowerPC, PowerPC64, ARM, Hitachi SuperH, Cell,
  IBM S/390, MIPS, HP PA-RISC, Intel IA-64, DEC VAX, AMD x86-64, AXIS CRIS,
  Xtensa, Tilera TILE, AVR32, ARC and Renesas M32R architectures.

  Linux is easily portable to most general-purpose 32- or 64-bit architectures
  as long as they have a paged memory management unit (PMMU) and a port of the
  GNU C compiler (gcc) (part of The GNU Compiler Collection, GCC). Linux has
  also been ported to a number of architectures without a PMMU, although
  functionality is then obviously somewhat limited.
  Linux has also been ported to itself. You can now run the kernel as a
  userspace application - this is called UserMode Linux (UML).

DOCUMENTATION:

 - There is a lot of documentation available both in electronic form on
   the Internet and in books, both Linux-specific and pertaining to
   general UNIX questions.  I'd recommend looking into the documentation
   subdirectories on any Linux FTP site for the LDP (Linux Documentation
   Project) books.  This README is not meant to be documentation on the
   system: there are much better sources available.

 - There are various README files in the Documentation/ subdirectory:
   these typically contain kernel-specific installation notes for some
   drivers for example. See Documentation/00-INDEX for a list of what
   is contained in each file.  Please read the Changes file, as it
   contains information about the problems, which may result by upgrading
   your kernel.

 - The Documentation/DocBook/ subdirectory contains several guides for
   kernel developers and users.  These guides can be rendered in a
   number of formats:  PostScript (.ps), PDF, HTML, & man-pages, among others.
   After installation, "make psdocs", "make pdfdocs", "make htmldocs",
   or "make mandocs" will render the documentation in the requested format.

INSTALLING the kernel source:

 - If you install the full sources, put the kernel tarball in a
   directory where you have permissions (e.g. your home directory) and
   unpack it:

     xz -cd linux-4.X.tar.xz | tar xvf -

   Replace "X" with the version number of the latest kernel.

   Do NOT use the /usr/src/linux area! This area has a (usually
   incomplete) set of kernel headers that are used by the library header
   files.  They should match the library, and not get messed up by
   whatever the kernel-du-jour happens to be.

 - You can also upgrade between 4.x releases by patching.  Patches are
   distributed in the xz format.  To install by patching, get all the
   newer patch files, enter the top level directory of the kernel source
   (linux-4.X) and execute:

     xz -cd ../patch-4.x.xz | patch -p1

   Replace "x" for all versions bigger than the version "X" of your current
   source tree, _in_order_, and you should be ok.  You may want to remove
   the backup files (some-file-name~ or some-file-name.orig), and make sure
   that there are no failed patches (some-file-name# or some-file-name.rej).
   If there are, either you or I have made a mistake.

   Unlike patches for the 4.x kernels, patches for the 4.x.y kernels
   (also known as the -stable kernels) are not incremental but instead apply
   directly to the base 4.x kernel.  For example, if your base kernel is 4.0
   and you want to apply the 4.0.3 patch, you must not first apply the 4.0.1
   and 4.0.2 patches. Similarly, if you are running kernel version 4.0.2 and
   want to jump to 4.0.3, you must first reverse the 4.0.2 patch (that is,
   patch -R) _before_ applying the 4.0.3 patch. You can read more on this in
   Documentation/applying-patches.txt

   Alternatively, the script patch-kernel can be used to automate this
   process.  It determines the current kernel version and applies any
   patches found.

     linux/scripts/patch-kernel linux

   The first argument in the command above is the location of the
   kernel source.  Patches are applied from the current directory, but
   an alternative directory can be specified as the second argument.

 - Make sure you have no stale .o files and dependencies lying around:

     cd linux
     make mrproper

   You should now have the sources correctly installed.

SOFTWARE REQUIREMENTS

   Compiling and running the 4.x kernels requires up-to-date
   versions of various software packages.  Consult
   Documentation/Changes for the minimum version numbers required
   and how to get updates for these packages.  Beware that using
   excessively old versions of these packages can cause indirect
   errors that are very difficult to track down, so don't assume that
   you can just update packages when obvious problems arise during
   build or operation.

BUILD directory for the kernel:

   When compiling the kernel, all output files will per default be
   stored together with the kernel source code.
   Using the option "make O=output/dir" allows you to specify an alternate
   place for the output files (including .config).
   Example:

     kernel source code: /usr/src/linux-4.X
     build directory:    /home/name/build/kernel

   To configure and build the kernel, use:

     cd /usr/src/linux-4.X
     make O=/home/name/build/kernel menuconfig
     make O=/home/name/build/kernel
     sudo make O=/home/name/build/kernel modules_install install

   Please note: If the 'O=output/dir' option is used, then it must be
   used for all invocations of make.

CONFIGURING the kernel:

   Do not skip this step even if you are only upgrading one minor
   version.  New configuration options are added in each release, and
   odd problems will turn up if the configuration files are not set up
   as expected.  If you want to carry your existing configuration to a
   new version with minimal work, use "make oldconfig", which will
   only ask you for the answers to new questions.

 - Alternative configuration commands are:

     "make config"      Plain text interface.

     "make menuconfig"  Text based color menus, radiolists & dialogs.

     "make nconfig"     Enhanced text based color menus.

     "make xconfig"     Qt based configuration tool.

     "make gconfig"     GTK+ based configuration tool.

     "make oldconfig"   Default all questions based on the contents of
                        your existing ./.config file and asking about
                        new config symbols.

     "make silentoldconfig"
                        Like above, but avoids cluttering the screen
                        with questions already answered.
                        Additionally updates the dependencies.

     "make olddefconfig"
                        Like above, but sets new symbols to their default
                        values without prompting.

     "make defconfig"   Create a ./.config file by using the default
                        symbol values from either arch/$ARCH/defconfig
                        or arch/$ARCH/configs/${PLATFORM}_defconfig,
                        depending on the architecture.

     "make ${PLATFORM}_defconfig"
                        Create a ./.config file by using the default
                        symbol values from
                        arch/$ARCH/configs/${PLATFORM}_defconfig.
                        Use "make help" to get a list of all available
                        platforms of your architecture.

     "make allyesconfig"
                        Create a ./.config file by setting symbol
                        values to 'y' as much as possible.

     "make allmodconfig"
                        Create a ./.config file by setting symbol
                        values to 'm' as much as possible.

     "make allnoconfig" Create a ./.config file by setting symbol
                        values to 'n' as much as possible.

     "make randconfig"  Create a ./.config file by setting symbol
                        values to random values.

     "make localmodconfig" Create a config based on current config and
                           loaded modules (lsmod). Disables any module
                           option that is not needed for the loaded modules.

                           To create a localmodconfig for another machine,
                           store the lsmod of that machine into a file
                           and pass it in as a LSMOD parameter.

                   target$ lsmod > /tmp/mylsmod
                   target$ scp /tmp/mylsmod host:/tmp

                   host$ make LSMOD=/tmp/mylsmod localmodconfig

                           The above also works when cross compiling.

     "make localyesconfig" Similar to localmodconfig, except it will convert
                           all module options to built in (=y) options.

   You can find more information on using the Linux kernel config tools
   in Documentation/kbuild/kconfig.txt.

 - NOTES on "make config":

    - Having unnecessary drivers will make the kernel bigger, and can
      under some circumstances lead to problems: probing for a
      nonexistent controller card may confuse your other controllers

    - A kernel with math-emulation compiled in will still use the
      coprocessor if one is present: the math emulation will just
      never get used in that case.  The kernel will be slightly larger,
      but will work on different machines regardless of whether they
      have a math coprocessor or not.

    - The "kernel hacking" configuration details usually result in a
      bigger or slower kernel (or both), and can even make the kernel
      less stable by configuring some routines to actively try to
      break bad code to find kernel problems (kmalloc()).  Thus you
      should probably answer 'n' to the questions for "development",
      "experimental", or "debugging" features.

COMPILING the kernel:

 - Make sure you have at least gcc 3.2 available.
   For more information, refer to Documentation/Changes.

   Please note that you can still run a.out user programs with this kernel.

 - Do a "make" to create a compressed kernel image. It is also
   possible to do "make install" if you have lilo installed to suit the
   kernel makefiles, but you may want to check your particular lilo setup first.

   To do the actual install, you have to be root, but none of the normal
   build should require that. Don't take the name of root in vain.

 - If you configured any of the parts of the kernel as `modules', you
   will also have to do "make modules_install".

 - Verbose kernel compile/build output:

   Normally, the kernel build system runs in a fairly quiet mode (but not
   totally silent).  However, sometimes you or other kernel developers need
   to see compile, link, or other commands exactly as they are executed.
   For this, use "verbose" build mode.  This is done by passing
   "V=1" to the "make" command, e.g.

     make V=1 all

   To have the build system also tell the reason for the rebuild of each
   target, use "V=2".  The default is "V=0".

 - Keep a backup kernel handy in case something goes wrong.  This is
   especially true for the development releases, since each new release
   contains new code which has not been debugged.  Make sure you keep a
   backup of the modules corresponding to that kernel, as well.  If you
   are installing a new kernel with the same version number as your
   working kernel, make a backup of your modules directory before you
   do a "make modules_install".

   Alternatively, before compiling, use the kernel config option
   "LOCALVERSION" to append a unique suffix to the regular kernel version.
   LOCALVERSION can be set in the "General Setup" menu.

 - In order to boot your new kernel, you'll need to copy the kernel
   image (e.g. .../linux/arch/x86/boot/bzImage after compilation)
   to the place where your regular bootable kernel is found.

 - Booting a kernel directly from a floppy without the assistance of a
   bootloader such as LILO, is no longer supported.

   If you boot Linux from the hard drive, chances are you use LILO, which
   uses the kernel image as specified in the file /etc/lilo.conf.  The
   kernel image file is usually /vmlinuz, /boot/vmlinuz, /bzImage or
   /boot/bzImage.  To use the new kernel, save a copy of the old image
   and copy the new image over the old one.  Then, you MUST RERUN LILO
   to update the loading map! If you don't, you won't be able to boot
   the new kernel image.

   Reinstalling LILO is usually a matter of running /sbin/lilo.
   You may wish to edit /etc/lilo.conf to specify an entry for your
   old kernel image (say, /vmlinux.old) in case the new one does not
   work.  See the LILO docs for more information.

   After reinstalling LILO, you should be all set.  Shutdown the system,
   reboot, and enjoy!

   If you ever need to change the default root device, video mode,
   ramdisk size, etc.  in the kernel image, use the 'rdev' program (or
   alternatively the LILO boot options when appropriate).  No need to
   recompile the kernel to change these parameters.

 - Reboot with the new kernel and enjoy.

IF SOMETHING GOES WRONG:

 - If you have problems that seem to be due to kernel bugs, please check
   the file MAINTAINERS to see if there is a particular person associated
   with the part of the kernel that you are having trouble with. If there
   isn't anyone listed there, then the second best thing is to mail
   them to me ([email protected]), and possibly to any other
   relevant mailing-list or to the newsgroup.

 - In all bug-reports, *please* tell what kernel you are talking about,
   how to duplicate the problem, and what your setup is (use your common
   sense).  If the problem is new, tell me so, and if the problem is
   old, please try to tell me when you first noticed it.

 - If the bug results in a message like

     unable to handle kernel paging request at address C0000010
     Oops: 0002
     EIP:   0010:XXXXXXXX
     eax: xxxxxxxx   ebx: xxxxxxxx   ecx: xxxxxxxx   edx: xxxxxxxx
     esi: xxxxxxxx   edi: xxxxxxxx   ebp: xxxxxxxx
     ds: xxxx  es: xxxx  fs: xxxx  gs: xxxx
     Pid: xx, process nr: xx
     xx xx xx xx xx xx xx xx xx xx

   or similar kernel debugging information on your screen or in your
   system log, please duplicate it *exactly*.  The dump may look
   incomprehensible to you, but it does contain information that may
   help debugging the problem.  The text above the dump is also
   important: it tells something about why the kernel dumped code (in
   the above example, it's due to a bad kernel pointer). More information
   on making sense of the dump is in Documentation/oops-tracing.txt

 - If you compiled the kernel with CONFIG_KALLSYMS you can send the dump
   as is, otherwise you will have to use the "ksymoops" program to make
   sense of the dump (but compiling with CONFIG_KALLSYMS is usually preferred).
   This utility can be downloaded from
   ftp://ftp.<country>.kernel.org/pub/linux/utils/kernel/ksymoops/ .
   Alternatively, you can do the dump lookup by hand:

 - In debugging dumps like the above, it helps enormously if you can
   look up what the EIP value means.  The hex value as such doesn't help
   me or anybody else very much: it will depend on your particular
   kernel setup.  What you should do is take the hex value from the EIP
   line (ignore the "0010:"), and look it up in the kernel namelist to
   see which kernel function contains the offending address.

   To find out the kernel function name, you'll need to find the system
   binary associated with the kernel that exhibited the symptom.  This is
   the file 'linux/vmlinux'.  To extract the namelist and match it against
   the EIP from the kernel crash, do:

     nm vmlinux | sort | less

   This will give you a list of kernel addresses sorted in ascending
   order, from which it is simple to find the function that contains the
   offending address.  Note that the address given by the kernel
   debugging messages will not necessarily match exactly with the
   function addresses (in fact, that is very unlikely), so you can't
   just 'grep' the list: the list will, however, give you the starting
   point of each kernel function, so by looking for the function that
   has a starting address lower than the one you are searching for but
   is followed by a function with a higher address you will find the one
   you want.  In fact, it may be a good idea to include a bit of
   "context" in your problem report, giving a few lines around the
   interesting one.

   If you for some reason cannot do the above (you have a pre-compiled
   kernel image or similar), telling me as much about your setup as
   possible will help.  Please read the REPORTING-BUGS document for details.

 - Alternatively, you can use gdb on a running kernel. (read-only; i.e. you
   cannot change values or set break points.) To do this, first compile the
   kernel with -g; edit arch/x86/Makefile appropriately, then do a "make
   clean". You'll also need to enable CONFIG_PROC_FS (via "make config").

   After you've rebooted with the new kernel, do "gdb vmlinux /proc/kcore".
   You can now use all the usual gdb commands. The command to look up the
   point where your system crashed is "l *0xXXXXXXXX". (Replace the XXXes
   with the EIP value.)

   gdb'ing a non-running kernel currently fails because gdb (wrongly)
   disregards the starting offset for which the kernel is compiled.

jetson-nano's People

Contributors

Stargazers

Watchers

Forkers

meteorza garyang gcsuri terry2droid xderecx garymathews cibyyang n0n3m4 paweldefee g4bwy jojapoppa sk039 pcoultha javatmn isjerryxiao littlestardust 0xm3r black3806 seungmannlee zys1310992814 octane70 vaginessa hwjpeter hanhandan bigbendrugs indiewebconsulting amergnat anonymouscyberwarrior wjn740 abceset pulento egolboy xichuangxue zhfreal jackyzhangyc pauljflo shellsec fengjixuchui osdu power535 carollwell spikerguy jshensh siven-kang chudnovs checkm4te sangood yousirui1 dirkgroenen shantigilbert zhiyongni chilauhe vivau smsource webbbn alexgreench kittyhome5520 sturdycat wang007987 ljliux hoockoo lokenk spackevxb be286 1847123212 hejoin aksqcy liuyk0321 sady2009-wq lalelu68 codesnas jethome-ru eternalfs povlhp jiangcaijun1 luigicalligaris romangrechin seregega a1ezh olegator77 zhou-peter abt12680 uboborov mfkiwl rangamloki dieselnutjob djqlyy cslily gyillikci yc66542260 nhathoangbui123 shumov-ag yjchungdevgdr

jetson-nano's Issues

meson-drm d0100000.vpu: [drm:drm_fbdev_client_hotplug] ERROR fbdev: Failed to setup generic emulation (ret=-22)

1，Ask how to solve the above errors

2，HDMI has no output, is it related to this error?

[ 0.000000] Booting Linux on physical CPU 0x0000000000 [0x410fd034]
[ 0.000000] Linux version 5.2.0-aml-s9xxx (root@Hsy) (gcc version 7.3.1 20180425 [linaro-7.3-2018.05 revision d29120a424ecfbc167ef90065c0eeb7f91977701] (Linaro GCC 7.3-2018.05)) #1 SMP PREEMPT Sat Jul 13 11:38:07 CST 2019
[ 0.000000] Machine model: Phicomm N1
[ 0.000000] efi: Getting EFI parameters from FDT:
[ 0.000000] efi: UEFI not found.
[ 0.000000] Reserved memory: created CMA memory pool at 0x000000003b800000, size 896 MiB
[ 0.000000] OF: reserved mem: initialized node linux,cma, compatible id shared-dma-pool
[ 0.000000] On node 0 totalpages: 477952
[ 0.000000] DMA32 zone: 7616 pages used for memmap
[ 0.000000] DMA32 zone: 0 pages reserved
[ 0.000000] DMA32 zone: 477952 pages, LIFO batch:63
[ 0.000000] psci: probing for conduit method from DT.
[ 0.000000] psci: PSCIv0.2 detected in firmware.
[ 0.000000] psci: Using standard PSCI v0.2 function IDs
[ 0.000000] psci: Trusted OS migration not required
[ 0.000000] percpu: Embedded 23 pages/cpu s56088 r8192 d29928 u94208
[ 0.000000] pcpu-alloc: s56088 r8192 d29928 u94208 alloc=23*4096
[ 0.000000] pcpu-alloc: [0] 0 [0] 1 [0] 2 [0] 3
[ 0.000000] Detected VIPT I-cache on CPU0
[ 0.000000] CPU features: detected: ARM erratum 845719
[ 0.000000] Built 1 zonelists, mobility grouping on. Total pages: 470336
[ 0.000000] Kernel command line: root=/dev/mmcblk1p2 rootflags=data=writeback rw console=ttyAML0,115200n8 console=tty0 no_console_suspend consoleblank=0 fsck.fix=yes fsck.repair=yes net.ifnames=0
[ 0.000000] Dentry cache hash table entries: 262144 (order: 9, 2097152 bytes)
[ 0.000000] Inode-cache hash table entries: 131072 (order: 8, 1048576 bytes)
[ 0.000000] Memory: 930108K/1911808K available (12476K kernel code, 1038K rwdata, 4256K rodata, 640K init, 519K bss, 64196K reserved, 917504K cma-reserved)
[ 0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=4, Nodes=1
[ 0.000000] rcu: Preemptible hierarchical RCU implementation.
[ 0.000000] rcu: RCU restricting CPUs from NR_CPUS=64 to nr_cpu_ids=4.
[ 0.000000] Tasks RCU enabled.
[ 0.000000] rcu: RCU calculated value of scheduler-enlistment delay is 25 jiffies.
[ 0.000000] rcu: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=4
[ 0.000000] NR_IRQS: 64, nr_irqs: 64, preallocated irqs: 0
[ 0.000000] GIC: Using split EOI/Deactivate mode
[ 0.000000] irq_meson_gpio: 110 to 8 gpio interrupt mux initialized
[ 0.000000] random: get_random_bytes called from start_kernel+0x2b4/0x45c with crng_init=0
[ 0.000000] arch_timer: cp15 timer(s) running at 24.00MHz (phys).
[ 0.000000] clocksource: arch_sys_counter: mask: 0xffffffffffffff max_cycles: 0x588fe9dc0, max_idle_ns: 440795202592 ns
[ 0.000003] sched_clock: 56 bits at 24MHz, resolution 41ns, wraps every 4398046511097ns
[ 0.000278] Console: colour dummy device 80x25
[ 0.000563] printk: console [tty0] enabled
[ 0.000598] Calibrating delay loop (skipped), value calculated using timer frequency.. 48.00 BogoMIPS (lpj=96000)
[ 0.000618] pid_max: default: 32768 minimum: 301
[ 0.000708] LSM: Security Framework initializing
[ 0.000764] Mount-cache hash table entries: 4096 (order: 3, 32768 bytes)
[ 0.000785] Mountpoint-cache hash table entries: 4096 (order: 3, 32768 bytes)
[ 0.024002] ASID allocator initialised with 32768 entries
[ 0.031985] rcu: Hierarchical SRCU implementation.
[ 0.041308] EFI services will not be available.
[ 0.048029] smp: Bringing up secondary CPUs ...
[ 0.080234] Detected VIPT I-cache on CPU1
[ 0.080279] CPU1: Booted secondary processor 0x0000000001 [0x410fd034]
[ 0.112268] Detected VIPT I-cache on CPU2
[ 0.112303] CPU2: Booted secondary processor 0x0000000002 [0x410fd034]
[ 0.144311] Detected VIPT I-cache on CPU3
[ 0.144344] CPU3: Booted secondary processor 0x0000000003 [0x410fd034]
[ 0.144409] smp: Brought up 1 node, 4 CPUs
[ 0.144472] SMP: Total of 4 processors activated.
[ 0.144483] CPU features: detected: 32-bit EL0 Support
[ 0.144494] CPU features: detected: CRC32 instructions
[ 0.144831] CPU: All CPU(s) started at EL2
[ 0.144854] alternatives: patching kernel code
[ 0.145671] devtmpfs: initialized
[ 0.150010] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 7645041785100000 ns
[ 0.150044] futex hash table entries: 1024 (order: 4, 65536 bytes)
[ 0.173120] xor: measuring software checksum speed
[ 0.212337] 8regs : 2303.000 MB/sec
[ 0.252363] 32regs : 2831.000 MB/sec
[ 0.292397] arm64_neon: 2461.000 MB/sec
[ 0.292408] xor: using function: 32regs (2831.000 MB/sec)
[ 0.292424] pinctrl core: initialized pinctrl subsystem
[ 0.293248] DMI not present or invalid.
[ 0.293561] NET: Registered protocol family 16
[ 0.293981] audit: initializing netlink subsys (disabled)
[ 0.294095] audit: type=2000 audit(0.292:1): state=initialized audit_enabled=0 res=1
[ 0.294780] cpuidle: using governor menu
[ 0.295063] hw-breakpoint: found 6 breakpoint and 4 watchpoint registers.
[ 0.297226] DMA: preallocated 256 KiB pool for atomic allocations
[ 0.297352] Serial: AMBA PL011 UART driver
[ 0.313278] HugeTLB registered 1.00 GiB page size, pre-allocated 0 pages
[ 0.313302] HugeTLB registered 32.0 MiB page size, pre-allocated 0 pages
[ 0.313315] HugeTLB registered 2.00 MiB page size, pre-allocated 0 pages
[ 0.313328] HugeTLB registered 64.0 KiB page size, pre-allocated 0 pages
[ 0.314726] cryptd: max_cpu_qlen set to 1000
[ 0.384641] raid6: neonx8 gen() 1727 MB/s
[ 0.452681] raid6: neonx8 xor() 1572 MB/s
[ 0.520791] raid6: neonx4 gen() 1581 MB/s
[ 0.588842] raid6: neonx4 xor() 1482 MB/s
[ 0.656876] raid6: neonx2 gen() 1229 MB/s
[ 0.724935] raid6: neonx2 xor() 1238 MB/s
[ 0.793012] raid6: neonx1 gen() 765 MB/s
[ 0.861037] raid6: neonx1 xor() 874 MB/s
[ 0.929085] raid6: int64x8 gen() 1006 MB/s
[ 0.997132] raid6: int64x8 xor() 759 MB/s
[ 1.065197] raid6: int64x4 gen() 1092 MB/s
[ 1.133237] raid6: int64x4 xor() 777 MB/s
[ 1.201301] raid6: int64x2 gen() 728 MB/s
[ 1.269327] raid6: int64x2 xor() 615 MB/s
[ 1.337414] raid6: int64x1 gen() 486 MB/s
[ 1.405456] raid6: int64x1 xor() 451 MB/s
[ 1.405466] raid6: using algorithm neonx8 gen() 1727 MB/s
[ 1.405476] raid6: .... xor() 1572 MB/s, rmw enabled
[ 1.405486] raid6: using neon recovery algorithm
[ 1.407290] SCSI subsystem initialized
[ 1.407579] usbcore: registered new interface driver usbfs
[ 1.407646] usbcore: registered new interface driver hub
[ 1.407735] usbcore: registered new device driver usb
[ 1.408102] media: Linux media interface: v0.10
[ 1.408151] videodev: Linux video capture interface: v2.00
[ 1.408256] pps_core: LinuxPPS API ver. 1 registered
[ 1.408270] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti [email protected]
[ 1.408313] PTP clock support registered
[ 1.408647] Advanced Linux Sound Architecture Driver Initialized.
[ 1.409381] clocksource: Switched to clocksource arch_sys_counter
[ 1.409589] VFS: Disk quotas dquot_6.6.0
[ 1.409651] VFS: Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
[ 1.415167] NET: Registered protocol family 2
[ 1.415587] tcp_listen_portaddr_hash hash table entries: 1024 (order: 2, 16384 bytes)
[ 1.415631] TCP established hash table entries: 16384 (order: 5, 131072 bytes)
[ 1.415746] TCP bind hash table entries: 16384 (order: 6, 262144 bytes)
[ 1.415950] TCP: Hash tables configured (established 16384 bind 16384)
[ 1.416065] UDP hash table entries: 1024 (order: 3, 32768 bytes)
[ 1.416117] UDP-Lite hash table entries: 1024 (order: 3, 32768 bytes)
[ 1.416264] NET: Registered protocol family 1
[ 1.416618] RPC: Registered named UNIX socket transport module.
[ 1.416635] RPC: Registered udp transport module.
[ 1.416645] RPC: Registered tcp transport module.
[ 1.416654] RPC: Registered tcp NFSv4.1 backchannel transport module.
[ 1.416802] Unpacking initramfs...
[ 1.548517] Freeing initrd memory: 3220K
[ 1.549207] hw perfevents: enabled with armv8_cortex_a53 PMU driver, 7 counters available
[ 1.549537] kvm [1]: IPA Size Limit: 40bits
[ 1.550038] kvm [1]: vgic interrupt IRQ1
[ 1.550141] kvm [1]: Hyp mode initialized successfully
[ 1.668846] Initialise system trusted keyrings
[ 1.668987] workingset: timestamp_bits=46 max_order=19 bucket_order=0
[ 1.674875] squashfs: version 4.0 (2009/01/31) Phillip Lougher
[ 1.675471] NFS: Registering the id_resolver key type
[ 1.675509] Key type id_resolver registered
[ 1.675519] Key type id_legacy registered
[ 1.675534] nfs4filelayout_init: NFSv4 File Layout Driver Registering...
[ 1.675567] ntfs: driver 2.1.32 [Flags: R/W].
[ 1.676071] JFS: nTxBlock = 8192, nTxLock = 65536
[ 1.679872] SGI XFS with security attributes, no debug enabled
[ 1.681025] 9p: Installing v9fs 9p2000 file system support
[ 1.681353] ocfs2: Registered cluster interface o2cb
[ 1.681588] OCFS2 User DLM kernel interface loaded
[ 1.683025] gfs2: GFS2 installed
[ 1.686763] Key type asymmetric registered
[ 1.686785] Asymmetric key parser 'x509' registered
[ 1.686853] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 245)
[ 1.702855] soc soc0: Amlogic Meson GXL (S905D) Revision 21:d (4:2) Detected
[ 1.706646] Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled
[ 1.708487] c11084c0.serial: ttyAML6 at MMIO 0xc11084c0 (irq = 10, base_baud = 1500000) is a meson_uart
[ 1.708655] serial serial0: tty port ttyAML6 registered
[ 1.708909] c81004c0.serial: ttyAML0 at MMIO 0xc81004c0 (irq = 13, base_baud = 1500000) is a meson_uart
[ 2.540951] printk: console [ttyAML0] enabled
[ 2.550506] loop: module loaded
[ 2.551767] libphy: Fixed MDIO Bus: probed
[ 2.552937] tun: Universal TUN/TAP device driver, 1.6
[ 2.559222] meson8b-dwmac c9410000.ethernet: PTP uses main clock
[ 2.563384] meson8b-dwmac c9410000.ethernet: no reset control found
[ 2.570011] meson8b-dwmac c9410000.ethernet: User ID: 0x11, Synopsys ID: 0x37
[ 2.576654] meson8b-dwmac c9410000.ethernet: DWMAC1000
[ 2.581820] meson8b-dwmac c9410000.ethernet: DMA HW capability register supported
[ 2.589234] meson8b-dwmac c9410000.ethernet: RX Checksum Offload Engine supported
[ 2.596651] meson8b-dwmac c9410000.ethernet: COE Type 2
[ 2.601826] meson8b-dwmac c9410000.ethernet: TX Checksum insertion supported
[ 2.608811] meson8b-dwmac c9410000.ethernet: Wake-Up On Lan supported
[ 2.615231] meson8b-dwmac c9410000.ethernet: Normal descriptors
[ 2.621060] meson8b-dwmac c9410000.ethernet: Ring mode enabled
[ 2.626838] meson8b-dwmac c9410000.ethernet: Enable RX Mitigation via HW Watchdog Timer
[ 3.685405] libphy: stmmac: probed
[ 3.687042] dwc3 c9000000.dwc3: Failed to get clk 'ref': -2
[ 3.690313] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[ 3.695244] ehci-platform: EHCI generic platform driver
[ 3.700572] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
[ 3.706501] ohci-platform: OHCI generic platform driver
[ 3.712280] usbcore: registered new interface driver usb-storage
[ 3.719033] mousedev: PS/2 mouse device common for all mice
[ 3.723837] i2c /dev entries driver
[ 3.728201] sdhci: Secure Digital Host Controller Interface driver
[ 3.732712] sdhci: Copyright(c) Pierre Ossman
[ 3.737051] Synopsys Designware Multimedia Card Interface Driver
[ 3.744414] meson-gx-mmc d0072000.mmc: Got CD GPIO
[ 3.773969] meson-gx-mmc d0074000.mmc: allocated mmc-pwrseq
[ 3.800947] sdhci-pltfm: SDHCI platform and OF driver helper
[ 3.802068] ledtrig-cpu: registered to indicate activity on CPUs
[ 3.807474] meson-sm: secure-monitor enabled
[ 3.812155] usbcore: registered new interface driver usbhid
[ 3.816761] usbhid: USB HID core driver
[ 3.820843] platform-mhu c883c404.mailbox: Platform MHU Mailbox registered
[ 3.833223] NET: Registered protocol family 10
[ 3.834372] Segment Routing with IPv6
[ 3.837431] NET: Registered protocol family 17
[ 3.841689] 9pnet: Installing 9P2000 support
[ 3.845817] Key type dns_resolver registered
[ 3.850628] registered taskstats version 1
[ 3.854133] Loading compiled-in X.509 certificates
[ 3.859710] Btrfs loaded, crc32c=crc32c-generic
[ 3.873965] meson-drm d0100000.vpu: Queued 2 outputs on vpu
[ 3.874223] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
[ 3.880484] [drm] No driver support for vblank timestamp query.
[ 3.886527] meson-drm d0100000.vpu: CVBS Output connector not available
[ 3.917433] meson-dw-hdmi c883a000.hdmi-tx: Detected HDMI TX controller v2.01a with HDCP (meson_dw_hdmi_phy)
[ 3.922039] meson-dw-hdmi c883a000.hdmi-tx: registered DesignWare HDMI I2C bus driver
[ 3.930362] meson-drm d0100000.vpu: bound c883a000.hdmi-tx (ops meson_dw_hdmi_ops)
[ 3.937541] [drm] Initialized meson 1.0.0 20161109 for d0100000.vpu on minor 0
[ 3.947458] mmc1: new HS200 MMC card at address 0001
[ 3.949559] mmcblk1: mmc1:0001 CJNB4R 58.2 GiB
[ 3.953716] mmcblk1boot0: mmc1:0001 CJNB4R partition 1 4.00 MiB
[ 3.959579] mmcblk1boot1: mmc1:0001 CJNB4R partition 2 4.00 MiB
[ 3.965347] mmcblk1rpmb: mmc1:0001 CJNB4R partition 3 4.00 MiB, chardev (243:0)
[ 3.977184] mmcblk1: p1 p2
[ 4.056204] random: fast init done
[ 4.079636] meson-drm d0100000.vpu: [drm:drm_fbdev_client_hotplug] ERROR fbdev: Failed to setup generic emulation (ret=-22)
[ 4.085727] libphy: mdio_mux: probed
[ 4.091469] libphy: mdio_mux: probed
[ 4.097288] phy phy-d0078080.phy.2: unsupported PHY mode 5
[ 4.099831] xhci-hcd xhci-hcd.0.auto: xHCI Host Controller
[ 4.103243] xhci-hcd xhci-hcd.0.auto: new USB bus registered, assigned bus number 1
[ 4.111629] xhci-hcd xhci-hcd.0.auto: hcc params 0x0228f664 hci version 0x100 quirks 0x0000000002010010
[ 4.120196] xhci-hcd xhci-hcd.0.auto: irq 37, io mem 0xc9000000
[ 4.126667] hub 1-0:1.0: USB hub found
[ 4.129748] hub 1-0:1.0: 2 ports detected
[ 4.133999] xhci-hcd xhci-hcd.0.auto: xHCI Host Controller
[ 4.139125] xhci-hcd xhci-hcd.0.auto: new USB bus registered, assigned bus number 2
[ 4.146708] xhci-hcd xhci-hcd.0.auto: Host supports USB 3.0 SuperSpeed
[ 4.153217] usb usb2: We don't know the algorithms for LPM for this host, disabling LPM.
[ 4.161674] hub 2-0:1.0: USB hub found
[ 4.164910] hub 2-0:1.0: config failed, hub doesn't have any ports! (err -19)
[ 4.173713] scpi_protocol scpi: SCP Protocol legacy pre-1.0 firmware
[ 4.191729] hctosys: unable to open rtc device (rtc0)
[ 4.192007] VDDAO_3V3: disabling
[ 4.194385] ALSA device list:
[ 4.197280] No soundcards found.
[ 4.200930] Freeing unused kernel memory: 640K
[ 4.225703] Run /init as init process
[ 4.283766] random: systemd-udevd: uninitialized urandom read (16 bytes read)
[ 4.285728] random: systemd-udevd: uninitialized urandom read (16 bytes read)
[ 4.288364] random: udevadm: uninitialized urandom read (16 bytes read)
[ 4.469433] usb 1-1: new low-speed USB device number 2 using xhci-hcd
[ 4.654975] input: SEM USB Keyboard as /devices/platform/soc/soc:usb@c9000000/c9000000.dwc3/xhci-hcd.0.auto/usb1/1-1/1-1:1.0/0003:1A2C:2124.0001/input/input0
[ 4.722936] hid-generic 0003:1A2C:2124.0001: input: USB HID v1.10 Keyboard [SEM USB Keyboard] on usb-xhci-hcd.0.auto-1/input0
[ 4.747838] input: SEM USB Keyboard Consumer Control as /devices/platform/soc/soc:usb@c9000000/c9000000.dwc3/xhci-hcd.0.auto/usb1/1-1/1-1:1.1/0003:1A2C:2124.0002/input/input1
[ 4.818751] input: SEM USB Keyboard System Control as /devices/platform/soc/soc:usb@c9000000/c9000000.dwc3/xhci-hcd.0.auto/usb1/1-1/1-1:1.1/0003:1A2C:2124.0002/input/input2
[ 4.829234] hid-generic 0003:1A2C:2124.0002: input: USB HID v1.10 Device [SEM USB Keyboard] on usb-xhci-hcd.0.auto-1/input1
[ 5.100632] EXT4-fs (mmcblk1p2): mounted filesystem with writeback data mode. Opts: data=writeback
[ 5.259590] systemd[1]: System time before build time, advancing clock.
[ 5.271512] systemd[1]: systemd 232 running in system mode. (+PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD +IDN)
[ 5.284589] systemd[1]: Detected architecture arm64.
[ 5.290231] systemd[1]: Set hostname to .
[ 5.440360] systemd[1]: Created slice System Slice.
[ 5.442932] systemd[1]: Mounting POSIX Message Queue File System...
[ 5.446449] systemd[1]: Listening on udev Control Socket.
[ 5.451592] systemd[1]: Reached target Remote File Systems.
[ 5.457268] systemd[1]: Started Forward Password Requests to Wall Directory Watch.
[ 5.464725] systemd[1]: Listening on udev Kernel Socket.
[ 5.470000] systemd[1]: Listening on /dev/initctl Compatibility Named Pipe.
[ 5.522504] EXT4-fs (mmcblk1p2): re-mounted. Opts: (null)
[ 5.603170] systemd-journald[1412]: Received request to flush runtime journal from PID 1
[ 5.781021] input: adc-keys as /devices/platform/adc-keys/input/input3
[ 5.806396] meson-gx-mmc d0070000.mmc: allocated mmc-pwrseq
[ 5.868363] Bluetooth: Core ver 2.22
[ 5.868477] NET: Registered protocol family 31
[ 5.871392] Bluetooth: HCI device and connection manager initialized
[ 5.873369] mmc2: new high speed SDIO card at address 0001
[ 5.877931] Bluetooth: HCI socket layer initialized
[ 5.887629] Bluetooth: L2CAP socket layer initialized
[ 5.892656] Bluetooth: SCO socket layer initialized
[ 5.897468] Registered IR keymap rc-geekbox
[ 5.907015] IR NEC protocol handler initialized
[ 5.914307] Bluetooth: HCI UART driver ver 2.3
[ 5.914348] Bluetooth: HCI UART protocol H4 registered
[ 5.918439] Bluetooth: HCI UART protocol LL registered
[ 5.925967] Bluetooth: HCI UART protocol Three-wire (H5) registered
[ 5.933555] rc rc0: meson-ir as /devices/platform/soc/c8100000.bus/c8100580.ir/rc/rc0
[ 5.937521] input: meson-ir as /devices/platform/soc/c8100000.bus/c8100580.ir/rc/rc0/input4
[ 5.939407] Bluetooth: HCI UART protocol Broadcom registered
[ 5.939610] hci_uart_bcm serial0-0: serial0-0 supply vbat not found, using dummy regulator
[ 5.939739] hci_uart_bcm serial0-0: serial0-0 supply vddio not found, using dummy regulator
[ 5.952955] meson-ir c8100580.ir: receiver initialized
[ 5.971102] Bluetooth: HCI UART protocol QCA registered
[ 6.003103] FAT-fs (mmcblk1p1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
[ 6.114047] Bluetooth: hci0: BCM: chip id 107
[ 6.114354] Bluetooth: hci0: BCM: features 0x2f
[ 6.118796] Bluetooth: hci0: BCM4345C0
[ 6.120989] Bluetooth: hci0: BCM4345C0 (003.001.025) build 0000
[ 6.137908] RTL8211F Gigabit Ethernet 0.2009087f:00: attached PHY driver [RTL8211F Gigabit Ethernet] (mii_bus:phy_addr=0.2009087f:00, irq=39)
[ 6.157595] meson8b-dwmac c9410000.ethernet eth0: No Safety Features support found
[ 6.160745] meson8b-dwmac c9410000.ethernet eth0: PTP not supported by HW
[ 6.184465] cfg80211: Loading compiled-in X.509 certificates for regulatory database
[ 6.196843] cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7'
[ 6.224176] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43455-sdio for chip BCM4345/6
[ 6.228157] usbcore: registered new interface driver brcmfmac
[ 6.235746] brcmfmac mmc2:0001:1: Direct firmware load for brcm/brcmfmac43455-sdio.phicomm,n1.txt failed with error -2
[ 6.286313] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[ 6.286362] Bluetooth: BNEP filters: protocol multicast
[ 6.292238] Bluetooth: BNEP socket layer initialized
[ 6.333520] random: crng init done
[ 6.333526] random: 7 urandom warning(s) missed due to ratelimiting
[ 6.937789] Bluetooth: hci0: BCM4345C0 (003.001.025) build 0252
[ 8.350012] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43455-sdio for chip BCM4345/6
[ 8.401500] brcmfmac: brcmf_c_preinit_dcmds: Firmware: BCM4345/6 wl0: Aug 25 2015 18:58:57 version 7.45.69 (r581703) FWID 01-24037f6e
[ 10.180574] meson8b-dwmac c9410000.ethernet eth0: Link is Up - 100Mbps/Full - flow control off
[ 10.183818] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready

Hello, can you provide a branch to support the real-time kernel?

When Phicomm-n1 is under no load, the system load is around 2

When Phicomm-n1 is under no load, the system load is around 2
Is there a patch that can be fixed?

kernel panic about v4l2-ioctl.c

hi,I got in trouble when the S905D run armbian.The kernel log is below.
[ 22.356805] fuse init (API version 7.27)
[ 22.879434] ------------[ cut here ]------------
[ 22.879443] Unknown pixelformat 0x31324d41
[ 22.879504] WARNING: CPU: 0 PID: 2935 at drivers/media/v4l2-core/v4l2-ioctl.c:1340 v4l_enum_fmt+0x1558/0x1850
[ 22.879507] Modules linked in: fuse bnep btsdio bluetooth ecdh_generic brcmfmac brcmutil cfg80211 rfkill asix usbnet meson_ir ao_cec rc_core meson_gxbb_wdt pwm_meson meson_rng rng_core adc_keys input_polldev ip_tables x_tables ipv6 realtek
[ 22.879556] CPU: 0 PID: 2935 Comm: gst-plugin-scan Not tainted 4.19.0-rc7-aml-s9xxx #7
[ 22.879558] Hardware name: Phicomm N1 (DT)
[ 22.879562] pstate: 40000005 (nZcv daif -PAN -UAO)
[ 22.879566] pc : v4l_enum_fmt+0x1558/0x1850
[ 22.879569] lr : v4l_enum_fmt+0x1558/0x1850
[ 22.879571] sp : ffff00000de93b80
[ 22.879573] x29: ffff00000de93b80 x28: 00000000c0405602
[ 22.879578] x27: ffff000009da9b68 x26: ffff800025e6d008
[ 22.879582] x25: 0000000000000000 x24: ffff8000103ea100
[ 22.879587] x23: ffff800025e6d008 x22: ffff000009da9b68
[ 22.879591] x21: ffff800025e4c600 x20: ffff00000de93cf8
[ 22.879596] x19: 0000000000000000 x18: ffffffffffffffff
[ 22.879600] x17: 0000000000000000 x16: 0000000000000000
[ 22.879605] x15: ffff00000a17a000 x14: 00000000fffffff0
[ 22.879610] x13: ffff00000a24e6e0 x12: ffff00000a17a000
[ 22.879614] x11: 0000000000000000 x10: ffff00000a24d000
[ 22.879619] x9 : 0000000000000000 x8 : 0000000000000003
[ 22.879623] x7 : 0000000000000000 x6 : 0000000000000173
[ 22.879627] x5 : 0000000000000000 x4 : 0000000000000001
[ 22.879631] x3 : 0000000000000007 x2 : 0000000000000007
[ 22.879636] x1 : a37cf81da9540f00 x0 : 0000000000000000
[ 22.879641] Call trace:
[ 22.879645] v4l_enum_fmt+0x1558/0x1850
[ 22.879648] __video_do_ioctl+0x358/0x4b0
[ 22.879652] video_usercopy+0x284/0x4e8
[ 22.879655] video_ioctl2+0x14/0x20
[ 22.879659] v4l2_ioctl+0x38/0x58
[ 22.879665] do_vfs_ioctl+0xb8/0x8e0
[ 22.879669] ksys_ioctl+0x80/0xb8
[ 22.879673] __arm64_sys_ioctl+0x1c/0x28
[ 22.879679] el0_svc_common+0x60/0xe8
[ 22.879682] el0_svc_handler+0x24/0x80
[ 22.879686] el0_svc+0x8/0xc
[ 22.879689] ---[ end trace 00d2ceae7bd14dde ]---
[ 23.713892] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready

Source for the old kernel khadas-3.14

Please, could you provide the source for the old kernel khadas-3.14? I need it and with a
git clone -b khadas-3.14 https://github.com/150balbes/Amlogic_s905-kernel.git
I'm not more able to get it.
Where can I find it? I used it in the past from your repo but I haven't saved it.

Thanks a lot.

could you add NFS Kernel module ?

Hello.
the kernel is very great, but we need the nfs kernel module in phicomm-n1 box, can you complex it within to 5.1 kernel ?
thank you.

config v20190319 has a problem

When I compile kernel with "config v20190319" , it will report an error:" ‘kernel/config_data.gz’ need a target ‘.config’ ". It can be solved by choose "Kernel .config support".

Contact

Hello, I did not find another way to contact you regarding building kernel for S905 box. So, let me try here. I am working with 2016-05-04 amlogic release to build ubuntu-kodi pack. But have some problems in result:

network and wifi modules do not working yet
kodi 17.0a crashes on start with SIGSEGV (not sure why) with log record "ERROR: InitWindowSystem: Could not initialize"

Если у вас есть полчаса времени - напишите письмо, пожалуйта, на grimaz---yandex.ua
Расскажу подробней со всякими логами.

how to acctive /etc/udev/udev.conf

i have write the rules want to auto mount usb,but it does not work..how can i do to let it work

How to get uInitrd; How to compile uInitrd?

How to get uInitrd;
How to compile uInitrd?

[ 4.162374] meson-drm d0100000.vpu: [drm:drm_fb_helper_fbdev_setup] ERROR Failed to set fbdev configuration

[ 3.930310] [drm] Initialized meson 1.0.0 20161109 for d0100000.vpu on minor 0
[ 4.021154] random: fast init done
[ 4.162374] meson-drm d0100000.vpu: [drm:drm_fb_helper_fbdev_setup] ERROR Failed to set fbdev configuration
[ 4.167011] libphy: mdio_mux: probed
[ 4.172914] libphy: mdio_mux: probed

1，Ask how to solve the above errors

2，HDMI has no output, is it related to this error?

U boot

Can u-boot from one working image be edited so i can boot a odroid c2 image on a s905w tv box

boot from internal mmc

Hi 150balbes,

could you enable the following config options to the kernel, please?
CONFIG_BLK_CMDLINE_PARSER=y
CONFIG_CMDLINE_PARTITION=y
CONFIG_MTD_CMDLINE_PARTS=y
So with this options there can be boot the box from internal mmc with the old partition layout.
example: blkdevparts=mmcblk1:0x0800000@0x027400000(env),0x0800000@0x02e400000(dtb),0x02000000@0x034400000(boot),0x080000000@0x036c00000(swap),0x02eca00000@0x0b7400000(data) root=/dev/mmcblk1p5 ...

thanks you
best regards, Gabor

GPIO/UART access once booted

Not sure if this is the right place to post, but I would like to use the UART interface of my X96 mini in Linux userspace. Long story short I would like to use the GPIO for a dedicated serial link between the X96 and an arduino pro mini. How would this be possible?

could you add bbr support for kernel 5.0 stable release ?

No bbr support in kernel 5.0 rc8 version,could you add bbr support for kernel 5.0 stable release?thanks

Activate IFB for traffic shaping

Hello,

Please can you add CONFIG_IFB=m ( https://cateee.net/lkddb/web-lkddb/IFB.html ) to be able to use traffic shaping on s905 boxes ?

Thanks for your hard work btw

Monitor not working

Hi,
I tried the master branch of this repo using the config from your armbian repo:
https://github.com/150balbes/Build-Armbian/blob/master/config/kernel/linux-aml-s905-dev.config
and I don't get output through HDMI
The /dev/dri/card0 exists but the screen is not detecting a signal.
testing the mainline torvalds tree works fine and i get output through HDMI.

My device is KII pro and I use the meson_gxbb_p201.dtb

Is it possible to add an ARM mali GPU driver to the kernel

Please consider to merge newer upstream source

The Linux Kernel has released the 5.8 and the mainline was changed to 5.8-rc2.
The stable version was changed to 5.7.6.
Please consider to merge newer upstream source.
Or you may create a script for auto merging upstream source and execute it when upstream source has updated.
Thank you~

The wired network is not available

Hi, I use
Armbian_5.87_Aml-s905_Debian_buster_default_5.1.0_desktop_20190521 + phicomm-n1
It seems that the wired network is not available but wireless is fine.

Android serial pl2303.ko or ch341.ko

sorry if this question is off topic
I'm looking for the way to compile the Android driver module (.ko) for this SOC (Amlogic 905)
Can you recommend a proper way to do this please?
Do you have a kernel source from Amlogic and proper toolchain to do this?

Thanks in advance :)

use correct git practises

Hi @150balbes ,
thanks for your good work on Amlogic platform.It's a bit hard to follow your work on git hub since your commits don't have a meaningful names and comments, also you seem to commit your updates from Torvalds tree without using rebase which mixes the commits.
If you could please use correct git practices (add Torvalds remote to your local repo, use git pull to merge upstream changes and also add meaningful and memorable commits comments instead of just the date ) it would make it easy for us to benefit from your work.

Thanks

Thanks for your hard work

Thanks to your repo.
I could self compile and use the newer linux kernel than AMLOGIC provided one.
It brings my tv box up and work very smoothly without any problem for a few month.
It's a great work that I must say thanks to you.
Thanks again!!