armada 370 (88f6710) mainline uboot support
Posted by wacke
|
armada 370 (88f6710) mainline uboot support November 25, 2017 08:30PM |
Registered: 8 years ago Posts: 166 |
Hi bodhi,
I have a device use the armada 370 soc,but there is no mainline uboot support.And I found someone make some patch to support the armada 370 see: https://sites.google.com/site/shihsung/88fxxxx-soc
Is there anyway to port that patch to the mainline uboot?
My device hardware info:
see also : https://forum.openwrt.org/viewtopic.php?pid=237049#p237049
Edited 1 time(s). Last edit at 11/25/2017 08:31PM by wacke.
I have a device use the armada 370 soc,but there is no mainline uboot support.And I found someone make some patch to support the armada 370 see: https://sites.google.com/site/shihsung/88fxxxx-soc
Is there anyway to port that patch to the mainline uboot?
My device hardware info:
Soc :Marvell armada370 ARMv7 1.2G Switch: Marvell 88E6171R 100/1000M 5 Port DDR3 1G or 512MB NAND FLASH 4GB SATA2: 2 Port and 12V power Port: 2 socket Minipci-e: 2 slot (include 4G LTE support) SIM : 1 socket GPIO .......
see also : https://forum.openwrt.org/viewtopic.php?pid=237049#p237049
Edited 1 time(s). Last edit at 11/25/2017 08:31PM by wacke.
|
Re: armada 370 (88f6710) mainline uboot support November 25, 2017 09:59PM |
Admin Registered: 13 years ago Posts: 18,543 |
wacke,
> I have a device use the armada 370 soc,but there
> is no mainline uboot support.And I found someone
> make some patch to support the armada 370 see:
> https://sites.google.com/site/shihsung/88fxxxx-soc
>
> Is there anyway to port that patch to the mainline
> uboot?
That patch seems to be on top of a very old u-boot. So I'd rather not try to fit it into mainline code.
> see also :
> https://forum.openwrt.org/viewtopic.php?pid=237049#p237049
This Openwrt info also does not seems helpful!
Currently, I don't have any Armada 37x or 38x SoC device that I can run kwboot (my NAS326 kwboot is till an issue to solve). So that's one of the reasons. The other reason is lack of free time :)
In January, I'm going to get another Armada based board which has kwboot capability and start on building u-boot for it. Once I have one board working using the latest mainline u-boot code, then other Armada boards will be the next step..
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
> I have a device use the armada 370 soc,but there
> is no mainline uboot support.And I found someone
> make some patch to support the armada 370 see:
> https://sites.google.com/site/shihsung/88fxxxx-soc
>
> Is there anyway to port that patch to the mainline
> uboot?
That patch seems to be on top of a very old u-boot. So I'd rather not try to fit it into mainline code.
> see also :
> https://forum.openwrt.org/viewtopic.php?pid=237049#p237049
This Openwrt info also does not seems helpful!
Currently, I don't have any Armada 37x or 38x SoC device that I can run kwboot (my NAS326 kwboot is till an issue to solve). So that's one of the reasons. The other reason is lack of free time :)
In January, I'm going to get another Armada based board which has kwboot capability and start on building u-boot for it. Once I have one board working using the latest mainline u-boot code, then other Armada boards will be the next step..
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: armada 370 (88f6710) mainline uboot support November 25, 2017 10:10PM |
Registered: 8 years ago Posts: 166 |
bodhi Wrote:
-------------------------------------------------------
> In January, I'm going to get another Armada based
> board which has kwboot capability and start on
> building u-boot for it. Once I have one board
> working using the latest mainline u-boot code,
> then other Armada boards will be the next step..
Thanks for your reply,I've tried to port that patch to mainline uboot,there are too much errors when compiling.....
-------------------------------------------------------
> In January, I'm going to get another Armada based
> board which has kwboot capability and start on
> building u-boot for it. Once I have one board
> working using the latest mainline u-boot code,
> then other Armada boards will be the next step..
Thanks for your reply,I've tried to port that patch to mainline uboot,there are too much errors when compiling.....
|
Re: armada 370 (88f6710) mainline uboot support November 25, 2017 10:15PM |
Admin Registered: 13 years ago Posts: 18,543 |
wacke,
> Thanks for your reply,I've tried to port that
> patch to mainline uboot,there are too much errors
> when compiling.....
Like I said, it is based on a quite old u-boot, so it will be too much works to build.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
> Thanks for your reply,I've tried to port that
> patch to mainline uboot,there are too much errors
> when compiling.....
Like I said, it is based on a quite old u-boot, so it will be too much works to build.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: armada 370 (88f6710) mainline uboot support December 12, 2017 02:18PM |
Registered: 6 years ago Posts: 119 |
Quote
bodhi
In January, I'm going to get another Armada based board which has kwboot capability and start on building u-boot for it. Once I have one board working using the latest mainline u-boot code, then other Armada boards will be the next step..
This is great news! I noticed that recently Turris Omnia (Armada 385) support was added to mainline u-boot. Unfortunately, trying to kwboot my EX2100 with a slightly modified Turris Omnia board results in kwboot crashing out around the time the SPL is supposed to execute:
Sending boot image...
0 % [......................................................................]
1 % [......................................................................]
3 % [......................................................................]
4 % [......................................................................]
6 % [......................................................................]
7 % [......................................................................]
9 % [......................................................................]
10 % [......................................................................]
12 % [......................................................................]
13 % [......................................................................]
15 % [......................................................................]
16 % [......................................................................]
18 % [......................................................................]
19 % [......................................................................]
21 % [......................................................................]
22 % [......................................................................]
24 % [...............................k�d��ct
d����lt�c�hs�dd���d�d������ltkkc
�
��kl��t���d���+xmodem: Protocol error
Output in hexadecimal:
24 % [...............................1b146beb64fbfb63374bb1464414f4e4931494136c74e4638b341368738731464464414f4494136446474f46484e41493108394976c177436b6b6334b94b9413e46b6c9c9c749ff393464e413941083+xmodem: Protocol error
I'm at a loss about where to go next. It seems that u-boot is not even executing, there is some issue in the SPL causing the SoC to barf.
Edited 2 time(s). Last edit at 12/12/2017 02:41PM by hmartin.
|
Re: armada 370 (88f6710) mainline uboot support January 31, 2018 11:38PM |
Registered: 8 years ago Posts: 166 |
bodhi Wrote:
-------------------------------------------------------
> In January, I'm going to get another Armada based
> board which has kwboot capability and start on
> building u-boot for it. Once I have one board
> working using the latest mainline u-boot code,
> then other Armada boards will be the next step..
Hi bodhi,
How about your Armada based board?
-------------------------------------------------------
> In January, I'm going to get another Armada based
> board which has kwboot capability and start on
> building u-boot for it. Once I have one board
> working using the latest mainline u-boot code,
> then other Armada boards will be the next step..
Hi bodhi,
How about your Armada based board?
|
Re: armada 370 (88f6710) mainline uboot support February 01, 2018 12:50AM |
Admin Registered: 13 years ago Posts: 18,543 |
Hi wacke,
> How about your Armada based board?
It has not happened yet! I have been preoccupied with other more important matters.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
> How about your Armada based board?
It has not happened yet! I have been preoccupied with other more important matters.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: armada 370 (88f6710) mainline uboot support June 07, 2018 08:04PM |
Registered: 8 years ago Posts: 166 |
|
Re: armada 370 (88f6710) mainline uboot support June 07, 2018 10:06PM |
Admin Registered: 13 years ago Posts: 18,543 |
wacke Wrote:
-------------------------------------------------------
> bodhi Wrote:
> -------------------------------------------------------
> > Hi wacke,
> >
> > > How about your Armada based board?
> >
> > It has not happened yet! I have been
> preoccupied
> > with other more important matters.
>
> Hi bodhi,
>
> Any update for your Armada based board?
wacke,
I have not done much. Just reading and thinking how best to tackle this subject. The Thecus N2350 (or NAS326) box, both of which are Armada 38x, will be my testbed. I can do UART booting on the Thecus N2350 (with stock uboot) but not yet with NAS326 (my serial connection might be not stable, seeing some characters dropped).
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Edited 2 time(s). Last edit at 06/07/2018 10:13PM by bodhi.
-------------------------------------------------------
> bodhi Wrote:
> -------------------------------------------------------
> > Hi wacke,
> >
> > > How about your Armada based board?
> >
> > It has not happened yet! I have been
> preoccupied
> > with other more important matters.
>
> Hi bodhi,
>
> Any update for your Armada based board?
wacke,
I have not done much. Just reading and thinking how best to tackle this subject. The Thecus N2350 (or NAS326) box, both of which are Armada 38x, will be my testbed. I can do UART booting on the Thecus N2350 (with stock uboot) but not yet with NAS326 (my serial connection might be not stable, seeing some characters dropped).
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Edited 2 time(s). Last edit at 06/07/2018 10:13PM by bodhi.
|
Re: armada 370 (88f6710) mainline uboot support June 08, 2018 03:09AM |
Registered: 8 years ago Posts: 166 |
bodhi Wrote:
-------------------------------------------------------
>
> wacke,
>
> I have not done much. Just reading and thinking
> how best to tackle this subject. The Thecus N2350
> (or NAS326) box, both of which are Armada 38x,
> will be my testbed. I can do UART booting on the
> Thecus N2350 (with stock uboot) but not yet with
> NAS326 (my serial connection might be not stable,
> seeing some characters dropped).
Thank you for your works,I can only wait for you.
-------------------------------------------------------
>
> wacke,
>
> I have not done much. Just reading and thinking
> how best to tackle this subject. The Thecus N2350
> (or NAS326) box, both of which are Armada 38x,
> will be my testbed. I can do UART booting on the
> Thecus N2350 (with stock uboot) but not yet with
> NAS326 (my serial connection might be not stable,
> seeing some characters dropped).
Thank you for your works,I can only wait for you.
|
Re: armada 370 (88f6710) mainline uboot support August 25, 2018 11:09AM |
Registered: 8 years ago Posts: 166 |
Hi, Bodhi
Any update for your Armada based board?
And these days I'm trying to port new DSA bindings to this armada 370 board (I want to use the dsa driver in the kernel),but no lucky...
The DTS I've modified:
And the boot log of your debain:
Any idea about this? Thanks!
Any update for your Armada based board?
And these days I'm trying to port new DSA bindings to this armada 370 board (I want to use the dsa driver in the kernel),but no lucky...
The DTS I've modified:
/*
* Device Tree file for Marvell Armada 370 Reference Design board
* (RD-88F6710-A1)
*
* Copied from arch/arm/boot/dts/armada-370-db.dts
*
* Copyright (C) 2013 Florian Fainelli <florian@openwrt.org>
*
* This file is dual-licensed: you can use it either under the terms
* of the GPL or the X11 license, at your option. Note that this dual
* licensing only applies to this file, and not this project as a
* whole.
*
* a) This file is free software; you can redistribute it and/or
* modify it under the terms of the GNU General Public License as
* published by the Free Software Foundation; either version 2 of the
* License, or (at your option) any later version.
*
* This file is distributed in the hope that it will be useful,
* but WITHOUT ANY WARRANTY; without even the implied warranty of
* MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
* GNU General Public License for more details.
*
* Or, alternatively,
*
* b) Permission is hereby granted, free of charge, to any person
* obtaining a copy of this software and associated documentation
* files (the "Software"), to deal in the Software without
* restriction, including without limitation the rights to use,
* copy, modify, merge, publish, distribute, sublicense, and/or
* sell copies of the Software, and to permit persons to whom the
* Software is furnished to do so, subject to the following
* conditions:
*
* The above copyright notice and this permission notice shall be
* included in all copies or substantial portions of the Software.
*
* THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,
* EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES
* OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND
* NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT
* HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY,
* WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING
* FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR
* OTHER DEALINGS IN THE SOFTWARE.
*
* Note: this Device Tree assumes that the bootloader has remapped the
* internal registers to 0xf1000000 (instead of the default
* 0xd0000000). The 0xf1000000 is the default used by the recent,
* DT-capable, U-Boot bootloaders provided by Marvell. Some earlier
* boards were delivered with an older version of the bootloader that
* left internal registers mapped at 0xd0000000. If you are in this
* situation, you should either update your bootloader (preferred
* solution) or the below Device Tree should be adjusted.
*/
/dts-v1/;
#include <dt-bindings/input/input.h>
#include <dt-bindings/gpio/gpio.h>
#include "armada-370.dtsi"
/ {
model = "RTNAS V3";
compatible = "marvell,armada-370-rtnasv3","marvell,a370-rd", "marvell,armada370", "marvell,armada-370-xp";
chosen {
stdout-path = "serial0:115200n8";
};
memory@0 {
device_type = "memory";
reg = <0x00000000 0x40000000>; /* 1024 MB */
};
soc {
ranges = <MBUS_ID(0xf0, 0x01) 0 0xf1000000 0x100000
MBUS_ID(0x01, 0xe0) 0 0xfff00000 0x100000
MBUS_ID(0x09, 0x01) 0 0xf1100000 0x10000>;
internal-regs {
serial@12000 {
status = "okay";
};
sata@a0000 {
nr-ports = <2>;
status = "okay";
};
ethernet@70000 {
status = "disabled";
phy-mode = "sgmii";
};
ethernet@74000 {
pinctrl-0 = <&ge1_rgmii_pins>;
pinctrl-names = "default";
status = "okay";
phy-mode = "rgmii-id";
fixed-link {
speed = <1000>;
full-duplex;
};
};
mvsdio@d4000 {
pinctrl-0 = <&sdio_pins1>;
pinctrl-names = "default";
status = "disabled";
/* No CD or WP GPIOs */
broken-cd;
};
usb@50000 {
status = "okay";
};
usb@51000 {
status = "okay";
};
nand@d0000 {
status = "okay";
num-cs = <2>;
marvell,nand-keep-config;
marvell,nand-enable-arbiter;
nand-on-flash-bbt;
nand-ecc-strength = <0x4>;
nand-ecc-step-size = <0x200>;
partition@0 {
label = "u-boot";
reg = <0x0 0x400000>;
};
partition@400000 {
label = "uboot_env";
reg = <0x400000 0x400000>;
};
partition@800000 {
label = "vendor";
reg = <0x800000 0x400000>;
};
partition@c00000 {
label = "unused";
reg = <0xc00000 0xc00000>;
};
partition@1800000 {
label = "kernel";
reg = <0x1800000 0x400000>;
};
partition@1c00000 {
label = "ubi";
reg = <0x1c00000 0x3e400000>;
};
partition@40000000 {
label = "syscfg";
reg = <0x40000000 0xbbc00000>;
};
};
};
};
dsa {
status = "disabled";
compatible = "marvell,dsa";
#address-cells = <2>;
#size-cells = <0>;
dsa,ethernet = <ð1>;
dsa,mii-bus = <&mdio>;
switch@0 {
#address-cells = <1>;
#size-cells = <0>;
reg = <0x10 0>; /* MDIO address 16, switch 0 in tree */
port@0 {
reg = <0>;
label = "lan0";
};
port@1 {
reg = <1>;
label = "lan1";
};
port@2 {
reg = <2>;
label = "lan2";
};
port@3 {
reg = <3>;
label = "lan3";
};
port@4 {
reg = <4>;
label = "wan";
};
port@5 {
reg = <5>;
label = "cpu";
};
};
};
};
&pciec {
status = "okay";
/* Internal mini-PCIe connector */
pcie@1,0 {
/* Port 0, Lane 0 */
status = "okay";
};
/* Internal mini-PCIe connector */
pcie@2,0 {
/* Port 1, Lane 0 */
status = "okay";
};
};
&mdio {
pinctrl-0 = <&mdio_pins>;
pinctrl-names = "default";
phy1: ethernet-phy@1 {
reg = <1>;
};
switch0@10 {
compatible = "marvell,mv88e6085";
#address-cells = <1>;
#size-cells = <0>;
reg = <0x10>;
ports {
#address-cells = <1>;
#size-cells = <0>;
port@0 {
reg = <0>;
label = "lan0";
};
port@1 {
reg = <1>;
label = "lan1";
};
port@2 {
reg = <2>;
label = "lan2";
};
port@3 {
reg = <3>;
label = "lan3";
};
port@4 {
reg = <4>;
label = "wan";
};
port@5 {
reg = <5>;
label = "cpu";
ethernet = <ð1>;
fixed-link {
speed = <1000>;
full-duplex;
};
};
};
};
};
And the boot log of your debain:
Loading file "/boot/uImage" from ide device 1:1 (hdb1) 4343577 bytes read ## Booting kernel from Legacy Image at 00800000 ... Image Name: Linux-4.16.7-mvebu-tld-1 Created: 1970-01-01 0:12:06 UTC Image Type: ARM Linux Kernel Image (uncompressed) Data Size: 4343513 Bytes = 4.1 MiB Load Address: 00008000 Entry Point: 00008000 Verifying Checksum ... OK Loading Kernel Image ... OK OK Starting kernel ... Uncompressing Linux... done, booting the kernel. [ 0.000000] Booting Linux on physical CPU 0x0 [ 0.000000] Linux version 4.16.7-mvebu-tld-1 (root@tldDebianVM) (gcc version 5.4.0 20160609 (Ubuntu/Linaro 5.4.0-6ubuntu1~16.04.9)) #1 SMP PREEMPT Fri May 4 21:09:30 PDT 2018 [ 0.000000] CPU: ARMv7 Processor [561f5811] revision 1 (ARMv7), cr=10c5387d [ 0.000000] CPU: PIPT / VIPT nonaliasing data cache, PIPT instruction cache [ 0.000000] OF: fdt: Machine model: RTNAS V3 [ 0.000000] Memory policy: Data cache writeback [ 0.000000] CPU: All CPU(s) started in SVC mode. [ 0.000000] random: get_random_bytes called from start_kernel+0x80/0x404 with crng_init=0 [ 0.000000] percpu: Embedded 18 pages/cpu @(ptrval) s40972 r8192 d24564 u73728 [ 0.000000] Built 1 zonelists, mobility grouping on. Total pages: 260608 [ 0.000000] Kernel command line: rootdelay=10 root=/dev/sda1 console=ttyS0,115200 [ 0.000000] Dentry cache hash table entries: 131072 (order: 7, 524288 bytes) [ 0.000000] Inode-cache hash table entries: 65536 (order: 6, 262144 bytes) [ 0.000000] Memory: 1025016K/1048576K available (9216K kernel code, 762K rwdata, 2236K rodata, 1024K init, 335K bss, 23560K reserved, 0K cma-reserved, 262144K highmem) [ 0.000000] Virtual kernel memory layout: [ 0.000000] vector : 0xffff0000 - 0xffff1000 ( 4 kB) [ 0.000000] fixmap : 0xffc00000 - 0xfff00000 (3072 kB) [ 0.000000] vmalloc : 0xf0800000 - 0xff800000 ( 240 MB) [ 0.000000] lowmem : 0xc0000000 - 0xf0000000 ( 768 MB) [ 0.000000] pkmap : 0xbfe00000 - 0xc0000000 ( 2 MB) [ 0.000000] modules : 0xbf000000 - 0xbfe00000 ( 14 MB) [ 0.000000] .text : 0x(ptrval) - 0x(ptrval) (10208 kB) [ 0.000000] .init : 0x(ptrval) - 0x(ptrval) (1024 kB) [ 0.000000] .data : 0x(ptrval) - 0x(ptrval) ( 763 kB) [ 0.000000] .bss : 0x(ptrval) - 0x(ptrval) ( 336 kB) [ 0.000000] Preemptible hierarchical RCU implementation. [ 0.000000] RCU restricting CPUs from NR_CPUS=4 to nr_cpu_ids=1. [ 0.000000] Tasks RCU enabled. [ 0.000000] RCU: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=1 [ 0.000000] NR_IRQS: 16, nr_irqs: 16, preallocated irqs: 16 [ 0.000000] L2C: DT/platform modifies aux control register: 0x12086302 -> 0x1a086302 [ 0.000000] Aurora cache controller enabled, 4 ways, 256 kB [ 0.000000] Aurora: CACHE_ID 0x00000100, AUX_CTRL 0x1a086302 [ 0.000000] Switching to timer-based delay loop, resolution 53ns [ 0.000006] sched_clock: 32 bits at 18MHz, resolution 53ns, wraps every 114840871909ns [ 0.000023] clocksource: armada_370_xp_clocksource: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 102208375848 ns [ 0.000632] Console: colour dummy device 80x30 [ 0.000661] Calibrating delay loop (skipped), value calculated using timer frequency.. 37.39 BogoMIPS (lpj=186996) [ 0.000677] pid_max: default: 32768 minimum: 301 [ 0.000831] Security Framework initialized [ 0.000924] Mount-cache hash table entries: 2048 (order: 1, 8192 bytes) [ 0.000940] Mountpoint-cache hash table entries: 2048 (order: 1, 8192 bytes) [ 0.001625] CPU: Testing write buffer coherency: ok [ 0.001913] CPU0: thread -1, cpu 0, socket -1, mpidr 0 [ 0.040159] Setting up static identity map for 0x100000 - 0x100060 [ 0.040481] mvebu-soc-id: MVEBU SoC ID=0x6710, Rev=0x1 [ 0.040581] mvebu-pmsu: Initializing Power Management Service Unit [ 0.060095] Hierarchical SRCU implementation. [ 0.100099] smp: Bringing up secondary CPUs ... [ 0.100117] smp: Brought up 1 node, 1 CPU [ 0.100126] SMP: Total of 1 processors activated (37.39 BogoMIPS). [ 0.100134] CPU: All CPU(s) started in SVC mode. [ 0.100904] devtmpfs: initialized [ 0.110230] VFP support v0.3: implementor 56 architecture 2 part 20 variant 9 rev 6 [ 0.110701] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns [ 0.110720] futex hash table entries: 256 (order: 2, 16384 bytes) [ 0.110936] prandom: seed boundary self test passed [ 0.113200] prandom: 100 self tests passed [ 0.113208] pinctrl core: initialized pinctrl subsystem [ 0.114080] NET: Registered protocol family 16 [ 0.114492] DMA: preallocated 256 KiB pool for atomic coherent allocations [ 0.114916] audit: initializing netlink subsys (disabled) [ 0.115194] audit: type=2000 audit(0.110:1): state=initialized audit_enabled=0 res=1 [ 0.120978] cpuidle: using governor ladder [ 0.121019] cpuidle: using governor menu [ 0.121158] hw-breakpoint: debug architecture 0x4 unsupported. [ 0.220804] vgaarb: loaded [ 0.221120] SCSI subsystem initialized [ 0.230460] usbcore: registered new interface driver usbfs [ 0.230514] usbcore: registered new interface driver hub [ 0.230578] usbcore: registered new device driver usb [ 0.230788] media: Linux media interface: v0.10 [ 0.230828] Linux video capture interface: v2.00 [ 0.230900] rc_core: IR Remote Control driver registered, major 250 [ 0.234865] clocksource: Switched to clocksource armada_370_xp_clocksource [ 0.299992] VFS: Disk quotas dquot_6.6.0 [ 0.300081] VFS: Dquot-cache hash table entries: 1024 (order 0, 4096 bytes) [ 0.321348] NET: Registered protocol family 2 [ 0.322583] tcp_listen_portaddr_hash hash table entries: 512 (order: 0, 6144 bytes) [ 0.322607] TCP established hash table entries: 8192 (order: 3, 32768 bytes) [ 0.322662] TCP bind hash table entries: 8192 (order: 4, 65536 bytes) [ 0.322733] TCP: Hash tables configured (established 8192 bind 8192) [ 0.322834] UDP hash table entries: 512 (order: 2, 16384 bytes) [ 0.322858] UDP-Lite hash table entries: 512 (order: 2, 16384 bytes) [ 0.323019] NET: Registered protocol family 1 [ 0.353739] RPC: Registered named UNIX socket transport module. [ 0.353753] RPC: Registered udp transport module. [ 0.353760] RPC: Registered tcp transport module. [ 0.353766] RPC: Registered tcp NFSv4.1 backchannel transport module. [ 0.354100] NetWinder Floating Point Emulator V0.97 (double precision) [ 0.354396] hw perfevents: enabled with armv7_cortex_a9 PMU driver, 7 counters available [ 0.357108] Initialise system trusted keyrings [ 0.357168] Key type blacklist registered [ 0.358138] workingset: timestamp_bits=30 max_order=18 bucket_order=0 [ 0.358256] zbud: loaded [ 0.359230] NFS: Registering the id_resolver key type [ 0.359257] Key type id_resolver registered [ 0.359265] Key type id_legacy registered [ 0.359280] nfs4filelayout_init: NFSv4 File Layout Driver Registering... [ 0.359289] Installing knfsd (copyright (C) 1996 okir@monad.swb.de). [ 0.359544] jffs2: version 2.2. (NAND) (SUMMARY) �© 2001-2006 Red Hat, Inc. [ 0.360426] orangefs_debugfs_init: called with debug mask: :none: :0: [ 0.360607] orangefs_init: module version upstream loaded [ 0.366404] Key type asymmetric registered [ 0.366419] Asymmetric key parser 'x509' registered [ 0.366486] bounce: pool size: 64 pages [ 0.366571] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 246) [ 0.366582] io scheduler noop registered [ 0.366590] io scheduler deadline registered [ 0.366683] io scheduler cfq registered (default) [ 0.368278] armada-370-pinctrl f1018000.pin-ctrl: registered pinctrl driver [ 0.372668] mvebu-gpio: probe of f1018180.gpio failed with error -2 [ 0.376415] mvebu-pcie soc:pcie@82000000: PCI host bridge to bus 0000:00 [ 0.376437] pci_bus 0000:00: root bus resource [io 0x1000-0xfffff] [ 0.376448] pci_bus 0000:00: root bus resource [mem 0xf8000000-0xffdfffff] [ 0.376460] pci_bus 0000:00: root bus resource [bus 00-ff] [ 0.377648] PCI: bus0: Fast back to back transfers disabled [ 0.377671] pci 0000:00:01.0: bridge configuration invalid ([bus 00-00]), reconfiguring [ 0.377694] pci 0000:00:02.0: bridge configuration invalid ([bus 00-00]), reconfiguring [ 0.404884] PCI: bus1: Fast back to back transfers enabled [ 0.434832] PCI: bus2: Fast back to back transfers enabled [ 0.434909] pci 0000:00:01.0: BAR 14: assigned [mem 0xf8000000-0xf80fffff] [ 0.434922] pci 0000:00:02.0: BAR 14: assigned [mem 0xf8200000-0xf84fffff] [ 0.434938] pci 0000:01:00.0: BAR 0: assigned [mem 0xf8000000-0xf801ffff 64bit] [ 0.434952] pci 0000:01:00.0: BAR 0: error updating (0xf8000004 != 0xffffffff) [ 0.434964] pci 0000:01:00.0: BAR 0: error updating (high 0x000000 != 0xffffffff) [ 0.434976] pci 0000:01:00.0: BAR 6: assigned [mem 0xf8020000-0xf802ffff pref] [ 0.434987] pci 0000:00:01.0: PCI bridge to [bus 01] [ 0.435001] pci 0000:00:01.0: bridge window [mem 0xf8000000-0xf80fffff] [ 0.435019] pci 0000:02:00.0: BAR 0: assigned [mem 0xf8200000-0xf83fffff 64bit] [ 0.435031] pci 0000:02:00.0: BAR 0: error updating (0xf8200004 != 0xffffffff) [ 0.435042] pci 0000:02:00.0: BAR 0: error updating (high 0x000000 != 0xffffffff) [ 0.435054] pci 0000:02:00.0: BAR 6: assigned [mem 0xf8400000-0xf840ffff pref] [ 0.435065] pci 0000:00:02.0: PCI bridge to [bus 02] [ 0.435076] pci 0000:00:02.0: bridge window [mem 0xf8200000-0xf84fffff] [ 0.435199] pcieport 0000:00:01.0: enabling device (0140 -> 0142) [ 0.435309] pcieport 0000:00:02.0: enabling device (0140 -> 0142) [ 0.436212] mv_xor f1060800.xor: Marvell shared XOR driver [ 0.495807] mv_xor f1060800.xor: Marvell XOR (Registers Mode): ( xor cpy intr ) [ 0.496228] mv_xor f1060900.xor: Marvell shared XOR driver [ 0.555811] mv_xor f1060900.xor: Marvell XOR (Registers Mode): ( xor cpy intr ) [ 0.694162] Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled [ 0.698331] console [ttyS0] disabled [ 0.719352] f1012000.serial: ttyS0 at MMIO 0xf1012000 (irq = 19, base_baud = 12500000) is a 16550A [ 1.589652] console [ttyS0] enabled [ 1.595360] sata_mv f10a0000.sata: slots 32 ports 2 [ 1.613473] scsi host0: sata_mv [ 1.627547] scsi host1: sata_mv [ 1.631168] ata1: SATA max UDMA/133 irq 28 [ 1.635520] ata2: SATA max UDMA/133 irq 28 [ 1.640486] pxa3xx-nand f10d0000.nand: This platform can't do DMA on this device [ 1.648968] pxa3xx-nand f10d0000.nand: non-supported command 5 [ 1.654909] nand: Failed to detect ONFI extended param page [ 1.660636] nand: device found, Manufacturer ID: 0x2c, Chip ID: 0x68 [ 1.667125] nand: Micron MT29F32G08CBACAWP [ 1.671248] nand: 4096 MiB, MLC, erase size: 1024 KiB, page size: 4096, OOB size: 224 [ 1.679437] pxa3xx-nand f10d0000.nand: ECC strength 16, ECC step size 2048 [ 1.687598] Bad block table found at page 1048320, version 0x01 [ 1.694370] Bad block table found at page 1048064, version 0x01 [ 1.700809] nand_read_bbt: bad block at 0x000005a00000 [ 1.706026] nand_read_bbt: bad block at 0x000005b00000 [ 1.711432] 7 ofpart partitions found on MTD device pxa3xx_nand-0 [ 1.717708] Creating 7 MTD partitions on "pxa3xx_nand-0": [ 1.723143] 0x000000000000-0x000000400000 : "u-boot" [ 1.729666] 0x000000400000-0x000000800000 : "uboot_env" [ 1.736622] 0x000000800000-0x000000c00000 : "vendor" [ 1.743250] 0x000000c00000-0x000001800000 : "unused" [ 1.749963] 0x000001800000-0x000001c00000 : "kernel" [ 1.756689] 0x000001c00000-0x000040000000 : "ubi" [ 1.764000] 0x000040000000-0x0000fbc00000 : "syscfg" [ 1.773932] nand: No NAND device found [ 1.778208] pxa3xx-nand f10d0000.nand: failed to scan nand at cs 1 [ 1.787305] libphy: Fixed MDIO Bus: probed [ 1.794961] libphy: orion_mdio_bus: probed [ 1.800222] mdio_bus f1072004.mdio-mii: MDIO device at address 1 is missing. [ 1.810930] mvneta f1074000.ethernet eth0: Using random mac address fa:2f:1e:ba:22:2d [ 1.821393] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver [ 1.828357] ehci-pci: EHCI PCI platform driver [ 1.832985] ehci-orion: EHCI orion driver [ 1.837641] orion-ehci f1050000.usb: EHCI Host Controller [ 1.843115] orion-ehci f1050000.usb: new USB bus registered, assigned bus number 1 [ 1.851039] orion-ehci f1050000.usb: irq 25, io mem 0xf1050000 [ 1.884788] orion-ehci f1050000.usb: USB 2.0 started, EHCI 1.00 [ 1.891005] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002 [ 1.897881] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [ 1.905180] usb usb1: Product: EHCI Host Controller [ 1.910084] usb usb1: Manufacturer: Linux 4.16.7-mvebu-tld-1 ehci_hcd [ 1.916595] usb usb1: SerialNumber: f1050000.usb [ 1.922044] hub 1-0:1.0: USB hub found [ 1.926103] hub 1-0:1.0: 1 port detected [ 1.930870] orion-ehci f1051000.usb: EHCI Host Controller [ 1.936659] orion-ehci f1051000.usb: new USB bus registered, assigned bus number 2 [ 1.944459] orion-ehci f1051000.usb: irq 26, io mem 0xf1051000 [ 1.974804] orion-ehci f1051000.usb: USB 2.0 started, EHCI 1.00 [ 1.980792] ata1: SATA link down (SStatus 0 SControl F300) [ 1.986580] usb usb2: New USB device found, idVendor=1d6b, idProduct=0002 [ 1.993405] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [ 2.000758] usb usb2: Product: EHCI Host Controller [ 2.005686] usb usb2: Manufacturer: Linux 4.16.7-mvebu-tld-1 ehci_hcd [ 2.012296] usb usb2: SerialNumber: f1051000.usb [ 2.017729] hub 2-0:1.0: USB hub found [ 2.021717] hub 2-0:1.0: 1 port detected [ 2.027121] usbcore: registered new interface driver usblp [ 2.033355] usbcore: registered new interface driver usb-storage [ 2.040391] mousedev: PS/2 mouse device common for all mice [ 2.514812] ata2: SATA link up 3.0 Gbps (SStatus 123 SControl F300) [ 2.523440] ata2.00: ATA-7: JMicron, 100415, max UDMA/133 [ 2.528898] ata2.00: 7856128 sectors, multi 1: LBA48 [ 2.536397] ata2.00: configured for UDMA/133 [ 2.551337] scsi 1:0:0:0: Direct-Access ATA JMicron 15 PQ: 0 ANSI: 5 [ 2.560699] sd 1:0:0:0: [sda] 7856128 512-byte logical blocks: (4.02 GB/3.75 GiB) [ 2.569367] sd 1:0:0:0: [sda] Write Protect is off [ 2.574313] sd 1:0:0:0: [sda] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA [ 2.585524] sda: sda1 sda2 [ 2.590037] sd 1:0:0:0: [sda] Attached SCSI disk [ 3.124811] rtc-mv f1010300.rtc: internal RTC not ticking [ 3.130477] i2c /dev entries driver [ 3.156028] orion_wdt: Initial timeout 229 sec [ 3.164757] marvell-cesa f1090000.crypto: CESA device successfully registered [ 3.172681] hidraw: raw HID events driver (C) Jiri Kosina [ 3.179004] usbcore: registered new interface driver usbhid [ 3.184609] usbhid: USB HID core driver [ 3.189659] drop_monitor: Initializing network drop monitor service [ 3.196790] NET: Registered protocol family 10 [ 3.212289] Segment Routing with IPv6 [ 3.216232] sit: IPv6, IPv4 and MPLS over IPv4 tunneling driver [ 3.224064] NET: Registered protocol family 17 [ 3.229057] 8021q: 802.1Q VLAN Support v1.8 [ 3.233310] Key type dns_resolver registered [ 3.237801] ThumbEE CPU extension supported. [ 3.242102] Registering SWP/SWPB emulation handler [ 3.247948] registered taskstats version 1 [ 3.252070] Loading compiled-in X.509 certificates [ 3.257409] zswap: loaded using pool lzo/zbud [ 3.263730] Key type big_key registered [ 3.268334] Key type encrypted registered [ 3.274325] hctosys: unable to open rtc device (rtc0) [ 3.280456] Waiting 10 sec before mounting root device... [ 13.926260] EXT4-fs (sda1): mounting ext3 file system using the ext4 subsystem [ 13.951739] EXT4-fs (sda1): mounted filesystem with ordered data mode. Opts: (null) [ 13.959677] VFS: Mounted root (ext3 filesystem) readonly on device 8:1. [ 13.971777] devtmpfs: mounted [ 13.976688] Freeing unused kernel memory: 1024K [ 13.982926] Checked W+X mappings: passed, no W+X pages found INIT: version 2.88 booting [ 14.211337] random: fast init done [info] Using makefile-style concurrent boot in runlevel S. ERROR: could not open /proc/stat: No such file or directory findfs: unable to resolve 'LABEL=rootfs' [....] Files under mount point '/run' will be hidden. ... (warning). [....] Starting the hotplug events dispatcher: systemd-udevdstarting version 232 [ 15.535449] random: systemd-udevd: uninitialized urandom read (16 bytes read) [ 15.557197] random: systemd-udevd: uninitialized urandom read (16 bytes read) [ 15.564552] random: systemd-udevd: uninitialized urandom read (16 bytes read) . ok [....] Synthesizing the initial hotplug events...done. [....] Waiting for /dev to be fully populated...[ 17.215218] sd 1:0:0:0: Attached scsi generic sg0 type 0 [ 17.724628] cfg80211: Loading compiled-in X.509 certificates for regulatory database [ 17.855915] cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7' [ 17.863355] platform regulatory.0: Direct firmware load for regulatory.db failed with error -2 [ 17.879844] cfg80211: failed to load regulatory.db [ 18.124141] ath10k_pci 0000:02:00.0: of_irq_parse_pci: failed with rc=134 [ 18.200982] ath9k 0000:01:00.0: enabling device (0000 -> 0002) [ 18.215062] ath10k_pci 0000:02:00.0: Refused to change power state, currently in D3 [ 18.265308] ath: phy1: Mac Chip Rev 0xfffc0.f is not supported by this driver [ 18.272491] ath: phy1: Unable to initialize hardware; initialization status: -95 [ 18.332334] ath9k 0000:01:00.0: Failed to initialize device [ 18.357790] ath9k: probe of 0000:01:00.0 failed with error -95 [ 18.402130] ath10k_pci 0000:02:00.0: failed to wake up device : -110 [ 18.432841] ath10k_pci: probe of 0000:02:00.0 failed with error -110 done. [....] Setting hostname to 'debian'...done. [....] Activating swap:. ok [ 21.875703] EXT4-fs (sda1): re-mounted. Opts: (null) [....] Will now check root file system:fsck from util-linux 2.29.2 [/sbin/fsck.ext3 (1) -- /] fsck.ext3 -y -C0 /dev/sda1 e2fsck 1.43.4 (31-Jan-2017) rootfs: clean, 24748/196608 files, 291690/786432 blocks . ok [ 22.189656] EXT4-fs (sda1): re-mounted. Opts: errors=remount-ro [....] Will now activate lvm and md swap:done. [info] Will now check all file systems. fsck from util-linux 2.29.2 Checking all file systems. LABEL=rootfs is mounted [....] Done checking file systems. A log is being saved in /var/log/fsck/checkfs if that location is writable.. ok [....] Cleaning up temporary files.... ok [....] Will now mount local filesystems:. ok [....] Will now activate swapfile swap:done. [....] Checking minimum space in /tmp...done. [....] Cleaning up temporary files.... ok [....] Setting kernel variables...done. [....] Initializing random number generator...done. [ 26.547099] mvneta f1074000.ethernet eth0: configuring for fixed/rgmii-id link mode [ 26.555600] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready [ 26.561576] mvneta f1074000.ethernet eth0: Link is Up - 1Gbps/Full - flow control off [ 26.571777] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready [....] Configuring network interfaces...Internet Systems Consortium DHCP Client 4.3.5 Copyright 2004-2016 Internet Systems Consortium. All rights reserved. For info, please visit https://www.isc.org/software/dhcp/ Listening on LPF/eth0/fa:2f:1e:ba:22:2d Sending on LPF/eth0/fa:2f:1e:ba:22:2d Sending on Socket/fallback DHCPREQUEST of 192.168.0.17 on eth0 to 255.255.255.255 port 67 DHCPNAK from 192.168.1.1 DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 5 DHCPREQUEST of 192.168.1.116 on eth0 to 255.255.255.255 port 67 DHCPOFFER of 192.168.1.116 from 192.168.1.1 DHCPACK of 192.168.1.116 from 192.168.1.1 bound to 192.168.1.116 -- renewal in 19391 seconds. done. [....] Starting RPC port mapper daemon: rpcbind. ok [....] Starting NFS common utilities: statd idmapd. ok [....] Cleaning up temporary files.... ok INIT: Entering runlevel: 2 [info] Using makefile-style concurrent boot in runlevel 2. [....] Starting busybox' syslogd implementation : syslogdStarting /sbin/syslogd... 2525 (syslogd) . ok [....] Not starting NFS kernel daemon: no exports. ... (warning). [....] Starting periodic command scheduler: cron. ok [....] Starting busybox' klogd implementation : klogdStarting /sbin/klogd... 2520 (klogd) . ok [....] Starting system message bus: dbus. ok [....] Starting Avahi mDNS/DNS-SD Daemon: avahi-daemon. ok [....] Starting OpenBSD Secure Shell server: sshd. ok [....] Starting NTP server: ntpd. ok [....] Running local boot scripts (/etc/rc.local). ok Debian GNU/Linux 9 debian ttyS0
Any idea about this? Thanks!
|
Re: armada 370 (88f6710) mainline uboot support August 25, 2018 03:08PM |
Admin Registered: 13 years ago Posts: 18,543 |
Hi wacke,
> Any update for your Armada based board?
As you can see, there always seems to be some new and interesting boards requests for kernel supports in the forum, so I can't find free time to work on u-boot :))
Is this the mv88e6085 switch, and do you know if register 0x10 is correct? your dmesg showed no activity at all regarding DSA.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
> Any update for your Armada based board?
As you can see, there always seems to be some new and interesting boards requests for kernel supports in the forum, so I can't find free time to work on u-boot :))
switch0@10 {
compatible = "marvell,mv88e6085";
#address-cells = <1>;
#size-cells = <0>;
reg = <0x10>;
Is this the mv88e6085 switch, and do you know if register 0x10 is correct? your dmesg showed no activity at all regarding DSA.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: armada 370 (88f6710) mainline uboot support August 25, 2018 07:02PM |
Registered: 8 years ago Posts: 166 |
bodhi Wrote:
-------------------------------------------------------
> Is this the mv88e6085 switch, and do you know if
> register 0x10 is correct? your dmesg showed no
> activity at all regarding DSA.
The switch chip is 88E6171R,and the register 0x10 was copied from "armada-370-rd" board. So I should change the register?
-------------------------------------------------------
> Is this the mv88e6085 switch, and do you know if
> register 0x10 is correct? your dmesg showed no
> activity at all regarding DSA.
The switch chip is 88E6171R,and the register 0x10 was copied from "armada-370-rd" board. So I should change the register?
|
Re: armada 370 (88f6710) mainline uboot support August 25, 2018 07:33PM |
Admin Registered: 13 years ago Posts: 18,543 |
wacke Wrote:
-------------------------------------------------------
> bodhi Wrote:
> -------------------------------------------------------
> > Is this the mv88e6085 switch, and do you know
> if
> > register 0x10 is correct? your dmesg showed no
> > activity at all regarding DSA.
>
> The switch chip is 88E6171R,and the register 0x10
> was copied from "armada-370-rd" board. So I should
> change the register?
Keep the register as 0x10, but change the compatible to MV88E6171
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
-------------------------------------------------------
> bodhi Wrote:
> -------------------------------------------------------
> > Is this the mv88e6085 switch, and do you know
> if
> > register 0x10 is correct? your dmesg showed no
> > activity at all regarding DSA.
>
> The switch chip is 88E6171R,and the register 0x10
> was copied from "armada-370-rd" board. So I should
> change the register?
Keep the register as 0x10, but change the compatible to MV88E6171
switch0@10 {
compatible = "marvell,mv88e6171";
#address-cells = <1>;
#size-cells = <0>;
reg = <0x10>;
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: armada 370 (88f6710) mainline uboot support August 25, 2018 08:02PM |
Registered: 8 years ago Posts: 166 |
bodhi Wrote:
-------------------------------------------------------
> wacke Wrote:
> -------------------------------------------------------
> > bodhi Wrote:
> >
> -------------------------------------------------------
> > > Is this the mv88e6085 switch, and do you know
> > if
> > > register 0x10 is correct? your dmesg showed
> no
> > > activity at all regarding DSA.
> >
> > The switch chip is 88E6171R,and the register
> 0x10
> > was copied from "armada-370-rd" board. So I
> should
> > change the register?
>
> Keep the register as 0x10, but change the
> compatible to MV88E6171
>
>
Hi,bodhi
After change the register to 0x0, the switch working properly now:
And the DTS:
But the MDIO still have error:
-------------------------------------------------------
> wacke Wrote:
> -------------------------------------------------------
> > bodhi Wrote:
> >
> -------------------------------------------------------
> > > Is this the mv88e6085 switch, and do you know
> > if
> > > register 0x10 is correct? your dmesg showed
> no
> > > activity at all regarding DSA.
> >
> > The switch chip is 88E6171R,and the register
> 0x10
> > was copied from "armada-370-rd" board. So I
> should
> > change the register?
>
> Keep the register as 0x10, but change the
> compatible to MV88E6171
>
>
> switch0@10 {
> compatible = "marvell,mv88e6171";
> #address-cells = <1>;
> #size-cells = <0>;
> reg = <0x10>;
>
Hi,bodhi
After change the register to 0x0, the switch working properly now:
Loading file "/boot/uImage" from ide device 1:1 (hdb1) 4343493 bytes read ## Booting kernel from Legacy Image at 00800000 ... Image Name: Linux-4.16.7-mvebu-tld-1 Created: 2018-08-26 0:48:59 UTC Image Type: ARM Linux Kernel Image (uncompressed) Data Size: 4343429 Bytes = 4.1 MiB Load Address: 00008000 Entry Point: 00008000 Verifying Checksum ... OK Loading Kernel Image ... OK OK Starting kernel ... Uncompressing Linux... done, booting the kernel. [ 0.000000] Booting Linux on physical CPU 0x0 [ 0.000000] Linux version 4.16.7-mvebu-tld-1 (root@tldDebianVM) (gcc version 5.4.0 20160609 (Ubuntu/Linaro 5.4.0-6ubuntu1~16.04.9)) #1 SMP PREEMPT Fri May 4 21:09:30 PDT 2018 [ 0.000000] CPU: ARMv7 Processor [561f5811] revision 1 (ARMv7), cr=10c5387d [ 0.000000] CPU: PIPT / VIPT nonaliasing data cache, PIPT instruction cache [ 0.000000] OF: fdt: Machine model: RTNAS V3 [ 0.000000] Memory policy: Data cache writeback [ 0.000000] CPU: All CPU(s) started in SVC mode. [ 0.000000] random: get_random_bytes called from start_kernel+0x80/0x404 with crng_init=0 [ 0.000000] percpu: Embedded 18 pages/cpu @(ptrval) s40972 r8192 d24564 u73728 [ 0.000000] Built 1 zonelists, mobility grouping on. Total pages: 260608 [ 0.000000] Kernel command line: rootdelay=10 root=/dev/sda1 console=ttyS0,115200 [ 0.000000] Dentry cache hash table entries: 131072 (order: 7, 524288 bytes) [ 0.000000] Inode-cache hash table entries: 65536 (order: 6, 262144 bytes) [ 0.000000] Memory: 1025016K/1048576K available (9216K kernel code, 762K rwdata, 2236K rodata, 1024K init, 335K bss, 23560K reserved, 0K cma-reserved, 262144K highmem) [ 0.000000] Virtual kernel memory layout: [ 0.000000] vector : 0xffff0000 - 0xffff1000 ( 4 kB) [ 0.000000] fixmap : 0xffc00000 - 0xfff00000 (3072 kB) [ 0.000000] vmalloc : 0xf0800000 - 0xff800000 ( 240 MB) [ 0.000000] lowmem : 0xc0000000 - 0xf0000000 ( 768 MB) [ 0.000000] pkmap : 0xbfe00000 - 0xc0000000 ( 2 MB) [ 0.000000] modules : 0xbf000000 - 0xbfe00000 ( 14 MB) [ 0.000000] .text : 0x(ptrval) - 0x(ptrval) (10208 kB) [ 0.000000] .init : 0x(ptrval) - 0x(ptrval) (1024 kB) [ 0.000000] .data : 0x(ptrval) - 0x(ptrval) ( 763 kB) [ 0.000000] .bss : 0x(ptrval) - 0x(ptrval) ( 336 kB) [ 0.000000] Preemptible hierarchical RCU implementation. [ 0.000000] RCU restricting CPUs from NR_CPUS=4 to nr_cpu_ids=1. [ 0.000000] Tasks RCU enabled. [ 0.000000] RCU: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=1 [ 0.000000] NR_IRQS: 16, nr_irqs: 16, preallocated irqs: 16 [ 0.000000] L2C: DT/platform modifies aux control register: 0x12086302 -> 0x1a086302 [ 0.000000] Aurora cache controller enabled, 4 ways, 256 kB [ 0.000000] Aurora: CACHE_ID 0x00000100, AUX_CTRL 0x1a086302 [ 0.000000] Switching to timer-based delay loop, resolution 53ns [ 0.000007] sched_clock: 32 bits at 18MHz, resolution 53ns, wraps every 114840871909ns [ 0.000023] clocksource: armada_370_xp_clocksource: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 102208375848 ns [ 0.000631] Console: colour dummy device 80x30 [ 0.000660] Calibrating delay loop (skipped), value calculated using timer frequency.. 37.39 BogoMIPS (lpj=186996) [ 0.000675] pid_max: default: 32768 minimum: 301 [ 0.000829] Security Framework initialized [ 0.000922] Mount-cache hash table entries: 2048 (order: 1, 8192 bytes) [ 0.000939] Mountpoint-cache hash table entries: 2048 (order: 1, 8192 bytes) [ 0.001624] CPU: Testing write buffer coherency: ok [ 0.001913] CPU0: thread -1, cpu 0, socket -1, mpidr 0 [ 0.040158] Setting up static identity map for 0x100000 - 0x100060 [ 0.040479] mvebu-soc-id: MVEBU SoC ID=0x6710, Rev=0x1 [ 0.040579] mvebu-pmsu: Initializing Power Management Service Unit [ 0.060094] Hierarchical SRCU implementation. [ 0.100098] smp: Bringing up secondary CPUs ... [ 0.100116] smp: Brought up 1 node, 1 CPU [ 0.100125] SMP: Total of 1 processors activated (37.39 BogoMIPS). [ 0.100133] CPU: All CPU(s) started in SVC mode. [ 0.100907] devtmpfs: initialized [ 0.110228] VFP support v0.3: implementor 56 architecture 2 part 20 variant 9 rev 6 [ 0.110697] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns [ 0.110717] futex hash table entries: 256 (order: 2, 16384 bytes) [ 0.110932] prandom: seed boundary self test passed [ 0.113196] prandom: 100 self tests passed [ 0.113204] pinctrl core: initialized pinctrl subsystem [ 0.114076] NET: Registered protocol family 16 [ 0.114487] DMA: preallocated 256 KiB pool for atomic coherent allocations [ 0.114911] audit: initializing netlink subsys (disabled) [ 0.115188] audit: type=2000 audit(0.110:1): state=initialized audit_enabled=0 res=1 [ 0.120975] cpuidle: using governor ladder [ 0.121016] cpuidle: using governor menu [ 0.121153] hw-breakpoint: debug architecture 0x4 unsupported. [ 0.220849] vgaarb: loaded [ 0.221160] SCSI subsystem initialized [ 0.230471] usbcore: registered new interface driver usbfs [ 0.230524] usbcore: registered new interface driver hub [ 0.230592] usbcore: registered new device driver usb [ 0.230810] media: Linux media interface: v0.10 [ 0.230852] Linux video capture interface: v2.00 [ 0.230927] rc_core: IR Remote Control driver registered, major 250 [ 0.234856] clocksource: Switched to clocksource armada_370_xp_clocksource [ 0.300088] VFS: Disk quotas dquot_6.6.0 [ 0.300179] VFS: Dquot-cache hash table entries: 1024 (order 0, 4096 bytes) [ 0.320028] NET: Registered protocol family 2 [ 0.321425] tcp_listen_portaddr_hash hash table entries: 512 (order: 0, 6144 bytes) [ 0.321451] TCP established hash table entries: 8192 (order: 3, 32768 bytes) [ 0.321506] TCP bind hash table entries: 8192 (order: 4, 65536 bytes) [ 0.321577] TCP: Hash tables configured (established 8192 bind 8192) [ 0.321678] UDP hash table entries: 512 (order: 2, 16384 bytes) [ 0.321702] UDP-Lite hash table entries: 512 (order: 2, 16384 bytes) [ 0.321862] NET: Registered protocol family 1 [ 0.353541] RPC: Registered named UNIX socket transport module. [ 0.353557] RPC: Registered udp transport module. [ 0.353564] RPC: Registered tcp transport module. [ 0.353570] RPC: Registered tcp NFSv4.1 backchannel transport module. [ 0.353899] NetWinder Floating Point Emulator V0.97 (double precision) [ 0.354191] hw perfevents: enabled with armv7_cortex_a9 PMU driver, 7 counters available [ 0.356863] Initialise system trusted keyrings [ 0.356910] Key type blacklist registered [ 0.357881] workingset: timestamp_bits=30 max_order=18 bucket_order=0 [ 0.357997] zbud: loaded [ 0.358958] NFS: Registering the id_resolver key type [ 0.358995] Key type id_resolver registered [ 0.359003] Key type id_legacy registered [ 0.359018] nfs4filelayout_init: NFSv4 File Layout Driver Registering... [ 0.359026] Installing knfsd (copyright (C) 1996 okir@monad.swb.de). [ 0.359280] jffs2: version 2.2. (NAND) (SUMMARY) �© 2001-2006 Red Hat, Inc. [ 0.360101] orangefs_debugfs_init: called with debug mask: :none: :0: [ 0.360297] orangefs_init: module version upstream loaded [ 0.366141] Key type asymmetric registered [ 0.366155] Asymmetric key parser 'x509' registered [ 0.366223] bounce: pool size: 64 pages [ 0.366307] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 246) [ 0.366318] io scheduler noop registered [ 0.366326] io scheduler deadline registered [ 0.366424] io scheduler cfq registered (default) [ 0.368025] armada-370-pinctrl f1018000.pin-ctrl: registered pinctrl driver [ 0.372419] mvebu-gpio: probe of f1018180.gpio failed with error -2 [ 0.376301] mvebu-pcie soc:pcie@82000000: PCI host bridge to bus 0000:00 [ 0.376322] pci_bus 0000:00: root bus resource [io 0x1000-0xfffff] [ 0.376333] pci_bus 0000:00: root bus resource [mem 0xf8000000-0xffdfffff] [ 0.376344] pci_bus 0000:00: root bus resource [bus 00-ff] [ 0.377106] PCI: bus0: Fast back to back transfers disabled [ 0.377129] pci 0000:00:01.0: bridge configuration invalid ([bus 00-00]), reconfiguring [ 0.377152] pci 0000:00:02.0: bridge configuration invalid ([bus 00-00]), reconfiguring [ 0.404883] PCI: bus1: Fast back to back transfers enabled [ 0.434829] PCI: bus2: Fast back to back transfers enabled [ 0.434905] pci 0000:00:01.0: BAR 14: assigned [mem 0xf8000000-0xf80fffff] [ 0.434918] pci 0000:00:02.0: BAR 14: assigned [mem 0xf8200000-0xf84fffff] [ 0.434934] pci 0000:01:00.0: BAR 0: assigned [mem 0xf8000000-0xf801ffff 64bit] [ 0.434948] pci 0000:01:00.0: BAR 0: error updating (0xf8000004 != 0xffffffff) [ 0.434960] pci 0000:01:00.0: BAR 0: error updating (high 0x000000 != 0xffffffff) [ 0.434972] pci 0000:01:00.0: BAR 6: assigned [mem 0xf8020000-0xf802ffff pref] [ 0.434983] pci 0000:00:01.0: PCI bridge to [bus 01] [ 0.434997] pci 0000:00:01.0: bridge window [mem 0xf8000000-0xf80fffff] [ 0.435014] pci 0000:02:00.0: BAR 0: assigned [mem 0xf8200000-0xf83fffff 64bit] [ 0.435027] pci 0000:02:00.0: BAR 0: error updating (0xf8200004 != 0xffffffff) [ 0.435038] pci 0000:02:00.0: BAR 0: error updating (high 0x000000 != 0xffffffff) [ 0.435050] pci 0000:02:00.0: BAR 6: assigned [mem 0xf8400000-0xf840ffff pref] [ 0.435061] pci 0000:00:02.0: PCI bridge to [bus 02] [ 0.435072] pci 0000:00:02.0: bridge window [mem 0xf8200000-0xf84fffff] [ 0.435194] pcieport 0000:00:01.0: enabling device (0140 -> 0142) [ 0.435305] pcieport 0000:00:02.0: enabling device (0140 -> 0142) [ 0.436201] mv_xor f1060800.xor: Marvell shared XOR driver [ 0.495805] mv_xor f1060800.xor: Marvell XOR (Registers Mode): ( xor cpy intr ) [ 0.496226] mv_xor f1060900.xor: Marvell shared XOR driver [ 0.555816] mv_xor f1060900.xor: Marvell XOR (Registers Mode): ( xor cpy intr ) [ 0.694567] Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled [ 0.698295] console [ttyS0] disabled [ 0.719527] f1012000.serial: ttyS0 at MMIO 0xf1012000 (irq = 19, base_baud = 12500000) is a 16550A [ 1.589837] console [ttyS0] enabled [ 1.595555] sata_mv f10a0000.sata: slots 32 ports 2 [ 1.613673] scsi host0: sata_mv [ 1.627734] scsi host1: sata_mv [ 1.631381] ata1: SATA max UDMA/133 irq 28 [ 1.635731] ata2: SATA max UDMA/133 irq 28 [ 1.640709] pxa3xx-nand f10d0000.nand: This platform can't do DMA on this device [ 1.649192] pxa3xx-nand f10d0000.nand: non-supported command 5 [ 1.655137] nand: Failed to detect ONFI extended param page [ 1.660863] nand: device found, Manufacturer ID: 0x2c, Chip ID: 0x68 [ 1.667352] nand: Micron MT29F32G08CBACAWP [ 1.671473] nand: 4096 MiB, MLC, erase size: 1024 KiB, page size: 4096, OOB size: 224 [ 1.679663] pxa3xx-nand f10d0000.nand: ECC strength 16, ECC step size 2048 [ 1.687818] Bad block table found at page 1048320, version 0x01 [ 1.694594] Bad block table found at page 1048064, version 0x01 [ 1.701035] nand_read_bbt: bad block at 0x000005a00000 [ 1.706250] nand_read_bbt: bad block at 0x000005b00000 [ 1.711656] 7 ofpart partitions found on MTD device pxa3xx_nand-0 [ 1.717926] Creating 7 MTD partitions on "pxa3xx_nand-0": [ 1.723362] 0x000000000000-0x000000400000 : "u-boot" [ 1.729859] 0x000000400000-0x000000800000 : "uboot_env" [ 1.736831] 0x000000800000-0x000000c00000 : "vendor" [ 1.743453] 0x000000c00000-0x000001800000 : "unused" [ 1.750181] 0x000001800000-0x000001c00000 : "kernel" [ 1.756882] 0x000001c00000-0x000040000000 : "ubi" [ 1.764207] 0x000040000000-0x0000fbc00000 : "syscfg" [ 1.774154] nand: No NAND device found [ 1.778428] pxa3xx-nand f10d0000.nand: failed to scan nand at cs 1 [ 1.787450] libphy: Fixed MDIO Bus: probed [ 1.795093] libphy: orion_mdio_bus: probed [ 1.800355] mdio_bus f1072004.mdio-mii: MDIO device at address 0 is missing. [ 1.811296] mvneta f1074000.ethernet eth0: Using random mac address 5e:e5:7a:38:3a:d7 [ 1.821570] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver [ 1.828538] ehci-pci: EHCI PCI platform driver [ 1.833169] ehci-orion: EHCI orion driver [ 1.837783] orion-ehci f1050000.usb: EHCI Host Controller [ 1.843248] orion-ehci f1050000.usb: new USB bus registered, assigned bus number 1 [ 1.851176] orion-ehci f1050000.usb: irq 25, io mem 0xf1050000 [ 1.884786] orion-ehci f1050000.usb: USB 2.0 started, EHCI 1.00 [ 1.891001] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002 [ 1.897879] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [ 1.905179] usb usb1: Product: EHCI Host Controller [ 1.910083] usb usb1: Manufacturer: Linux 4.16.7-mvebu-tld-1 ehci_hcd [ 1.916595] usb usb1: SerialNumber: f1050000.usb [ 1.922027] hub 1-0:1.0: USB hub found [ 1.926111] hub 1-0:1.0: 1 port detected [ 1.930875] orion-ehci f1051000.usb: EHCI Host Controller [ 1.936666] orion-ehci f1051000.usb: new USB bus registered, assigned bus number 2 [ 1.944466] orion-ehci f1051000.usb: irq 26, io mem 0xf1051000 [ 1.974801] orion-ehci f1051000.usb: USB 2.0 started, EHCI 1.00 [ 1.980790] ata1: SATA link down (SStatus 0 SControl F300) [ 1.986578] usb usb2: New USB device found, idVendor=1d6b, idProduct=0002 [ 1.993403] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [ 2.000755] usb usb2: Product: EHCI Host Controller [ 2.005683] usb usb2: Manufacturer: Linux 4.16.7-mvebu-tld-1 ehci_hcd [ 2.012291] usb usb2: SerialNumber: f1051000.usb [ 2.017736] hub 2-0:1.0: USB hub found [ 2.021723] hub 2-0:1.0: 1 port detected [ 2.027122] usbcore: registered new interface driver usblp [ 2.033358] usbcore: registered new interface driver usb-storage [ 2.040528] mousedev: PS/2 mouse device common for all mice [ 2.514807] ata2: SATA link up 3.0 Gbps (SStatus 123 SControl F300) [ 2.523436] ata2.00: ATA-7: JMicron, 100415, max UDMA/133 [ 2.528893] ata2.00: 7856128 sectors, multi 1: LBA48 [ 2.536392] ata2.00: configured for UDMA/133 [ 2.551327] scsi 1:0:0:0: Direct-Access ATA JMicron 15 PQ: 0 ANSI: 5 [ 2.560661] sd 1:0:0:0: [sda] 7856128 512-byte logical blocks: (4.02 GB/3.75 GiB) [ 2.569326] sd 1:0:0:0: [sda] Write Protect is off [ 2.574269] sd 1:0:0:0: [sda] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA [ 2.585470] sda: sda1 sda2 [ 2.590000] sd 1:0:0:0: [sda] Attached SCSI disk [ 3.124805] rtc-mv f1010300.rtc: internal RTC not ticking [ 3.130473] i2c /dev entries driver [ 3.156031] orion_wdt: Initial timeout 229 sec [ 3.164722] marvell-cesa f1090000.crypto: CESA device successfully registered [ 3.172599] hidraw: raw HID events driver (C) Jiri Kosina [ 3.179195] usbcore: registered new interface driver usbhid [ 3.185172] usbhid: USB HID core driver [ 3.189642] drop_monitor: Initializing network drop monitor service [ 3.196771] NET: Registered protocol family 10 [ 3.212264] Segment Routing with IPv6 [ 3.216200] sit: IPv6, IPv4 and MPLS over IPv4 tunneling driver [ 3.224021] NET: Registered protocol family 17 [ 3.229019] 8021q: 802.1Q VLAN Support v1.8 [ 3.233267] Key type dns_resolver registered [ 3.237758] ThumbEE CPU extension supported. [ 3.242059] Registering SWP/SWPB emulation handler [ 3.247883] registered taskstats version 1 [ 3.252004] Loading compiled-in X.509 certificates [ 3.257347] zswap: loaded using pool lzo/zbud [ 3.263695] Key type big_key registered [ 3.268302] Key type encrypted registered [ 3.274298] hctosys: unable to open rtc device (rtc0) [ 3.280428] Waiting 10 sec before mounting root device... [ 13.926260] EXT4-fs (sda1): mounting ext3 file system using the ext4 subsystem [ 13.952711] EXT4-fs (sda1): mounted filesystem with ordered data mode. Opts: (null) [ 13.960650] VFS: Mounted root (ext3 filesystem) readonly on device 8:1. [ 13.971912] devtmpfs: mounted [ 13.976847] Freeing unused kernel memory: 1024K [ 13.983123] Checked W+X mappings: passed, no W+X pages found INIT: version 2.88 booting [ 14.206001] random: fast init done [info] Using makefile-style concurrent boot in runlevel S. ERROR: could not open /proc/stat: No such file or directory findfs: unable to resolve 'LABEL=rootfs' [....] Files under mount point '/run' will be hidden. ... (warning). [....] Starting the hotplug events dispatcher: systemd-udevdstarting version 232 [ 15.538563] random: systemd-udevd: uninitialized urandom read (16 bytes read) [ 15.560150] random: systemd-udevd: uninitialized urandom read (16 bytes read) [ 15.575249] random: systemd-udevd: uninitialized urandom read (16 bytes read) . ok [....] Synthesizing the initial hotplug events...done. [....] Waiting for /dev to be fully populated...[ 17.163520] mv88e6085 f1072004.mdio-mii:00: switch 0x1710 detected: Marvell 88E6171, revision 2 [ 17.235925] sd 1:0:0:0: Attached scsi generic sg0 type 0 [ 17.496802] libphy: mv88e6xxx SMI: probed [ 17.793303] cfg80211: Loading compiled-in X.509 certificates for regulatory database [ 17.934230] cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7' [ 17.969869] platform regulatory.0: Direct firmware load for regulatory.db failed with error -2 [ 17.986428] cfg80211: failed to load regulatory.db [ 18.139885] ath9k 0000:01:00.0: enabling device (0000 -> 0002) [ 18.194736] ath10k_pci 0000:02:00.0: of_irq_parse_pci: failed with rc=134 [ 18.235475] ath: phy0: Mac Chip Rev 0xfffc0.f is not supported by this driver [ 18.242660] ath: phy0: Unable to initialize hardware; initialization status: -95 [ 18.345040] ath10k_pci 0000:02:00.0: Refused to change power state, currently in D3 [ 18.414967] ath9k 0000:01:00.0: Failed to initialize device [ 18.437355] ath9k: probe of 0000:01:00.0 failed with error -95 [ 18.475755] Generic PHY mv88e6xxx-0:00: attached PHY driver [Generic PHY] (mii_bus:phy_addr=mv88e6xxx-0:00, irq=POLL) [ 18.539417] Generic PHY mv88e6xxx-0:01: attached PHY driver [Generic PHY] (mii_bus:phy_addr=mv88e6xxx-0:01, irq=POLL) [ 18.571949] ath10k_pci 0000:02:00.0: failed to wake up device : -110 [ 18.600721] ath10k_pci: probe of 0000:02:00.0 failed with error -110 [ 18.607551] Generic PHY mv88e6xxx-0:02: attached PHY driver [Generic PHY] (mii_bus:phy_addr=mv88e6xxx-0:02, irq=POLL) [ 18.667830] Generic PHY mv88e6xxx-0:03: attached PHY driver [Generic PHY] (mii_bus:phy_addr=mv88e6xxx-0:03, irq=POLL) [ 18.724669] Generic PHY mv88e6xxx-0:04: attached PHY driver [Generic PHY] (mii_bus:phy_addr=mv88e6xxx-0:04, irq=POLL) [ 18.784361] DSA: tree 0 setup done. [....] Setting hostname to 'debian'...done. [....] Activating swap:. ok [ 22.561316] EXT4-fs (sda1): re-mounted. Opts: (null) [....] Will now check root file system:fsck from util-linux 2.29.2 [/sbin/fsck.ext3 (1) -- /] fsck.ext3 -y -C0 /dev/sda1 e2fsck 1.43.4 (31-Jan-2017) rootfs: clean, 24750/196608 files, 291699/786432 blocks . ok [ 22.877015] EXT4-fs (sda1): re-mounted. Opts: errors=remount-ro [....] Will now activate lvm and md swap:done. [info] Will now check all file systems. fsck from util-linux 2.29.2 Checking all file systems. LABEL=rootfs is mounted [....] Done checking file systems. A log is being saved in /var/log/fsck/checkfs if that location is writable.. ok [....] Cleaning up temporary files.... ok [....] Will now mount local filesystems:. ok [....] Will now activate swapfile swap:done. [....] Checking minimum space in /tmp...done. [....] Cleaning up temporary files.... ok [....] Setting kernel variables...done. [....] Initializing random number generator...done. [ 27.123359] mvneta f1074000.ethernet eth0: configuring for fixed/rgmii-id link mode [ 27.131714] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready [ 27.138030] mvneta f1074000.ethernet eth0: Link is Up - 1Gbps/Full - flow control off [ 27.153596] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready [....] Configuring network interfaces...Internet Systems Consortium DHCP Client 4.3.5 Copyright 2004-2016 Internet Systems Consortium. All rights reserved. For info, please visit https://www.isc.org/software/dhcp/ Listening on LPF/eth0/5e:e5:7a:38:3a:d7 Sending on LPF/eth0/5e:e5:7a:38:3a:d7 Sending on Socket/fallback DHCPREQUEST of 192.168.1.116 on eth0 to 255.255.255.255 port 67 DHCPREQUEST of 192.168.1.116 on eth0 to 255.255.255.255 port 67 DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 7 DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 9 DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 12 DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 10 DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 10 DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 8 DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 5 No DHCPOFFERS received. Trying recorded lease 192.168.1.116 PING 192.168.1.1 (192.168.1.1) 56(84) bytes of data. --- 192.168.1.1 ping statistics --- 1 packets transmitted, 0 received, +1 errors, 100% packet loss, time 0ms No working leases in persistent database - sleeping. done. [....] Starting RPC port mapper daemon: rpcbind. ok [....] Starting NFS common utilities: statd idmapd. ok [....] Cleaning up temporary files.... ok INIT: Entering runlevel: 2 [info] Using makefile-style concurrent boot in runlevel 2. [....] Starting busybox' syslogd implementation : syslogdStarting /sbin/syslogd... 2546 (syslogd) . ok [....] Not starting NFS kernel daemon: no exports. ... (warning). [....] Starting periodic command scheduler: cron. ok [....] Starting busybox' klogd implementation : klogdStarting /sbin/klogd... 2544 (klogd) . ok [....] Starting system message bus: dbus. ok [....] Starting Avahi mDNS/DNS-SD Daemon: avahi-daemon. ok [....] Starting NTP server: ntpd. ok [....] Starting OpenBSD Secure Shell server: sshd. ok [....] Running local boot scripts (/etc/rc.local). ok Debian GNU/Linux 9 debian ttyS0 debian login: Debian GNU/Linux 9 debian ttyS0 debian login: Debian GNU/Linux 9 debian ttyS0 debian login: root Password: Last login: Sat Aug 25 17:48:24 PDT 2018 on ttyS0 Linux debian 4.16.7-mvebu-tld-1 #1 SMP PREEMPT Fri May 4 21:09:30 PDT 2018 armv7l The programs included with the Debian GNU/Linux system are free software; the exact distribution terms for each program are described in the individual files in /usr/share/doc/*/copyright. Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent permitted by applicable law. debian RTNAS V3 Linux version 4.16.7-mvebu-tld-1 (root@tldDebianVM) (gcc version 5.4.0 20160609 (Ubuntu/Linaro 5.4.0-6ubuntu1~16.04.9)) #1 SMP PREEMPT Fri May 4 21:09:30 PDT 2018 Debian 9.1 Wed Dec 31 16:05:27 PST 1969 up 5 minutes root@debian:~# root@debian:~# root@debian:~# root@debian:~# ifconfig -a eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet6 fe80::5ce5:7aff:fe38:3ad7 prefixlen 64 scopeid 0x20<link> ether 5e:e5:7a:38:3a:d7 txqueuelen 532 (Ethernet) RX packets 253 bytes 107250 (104.7 KiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 52 bytes 9344 (9.1 KiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 device interrupt 27 ip6tnl0: flags=128<NOARP> mtu 1452 unspec 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 txqueuelen 1000 (UNSPEC) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 0 bytes 0 (0.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 lan0: flags=4098<BROADCAST,MULTICAST> mtu 1500 ether 5e:e5:7a:38:3a:d7 txqueuelen 1000 (Ethernet) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 0 bytes 0 (0.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 lan1: flags=4098<BROADCAST,MULTICAST> mtu 1500 ether 5e:e5:7a:38:3a:d7 txqueuelen 1000 (Ethernet) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 0 bytes 0 (0.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 lan2: flags=4098<BROADCAST,MULTICAST> mtu 1500 ether 5e:e5:7a:38:3a:d7 txqueuelen 1000 (Ethernet) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 0 bytes 0 (0.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 lan3: flags=4098<BROADCAST,MULTICAST> mtu 1500 ether 5e:e5:7a:38:3a:d7 txqueuelen 1000 (Ethernet) RX packets 253 bytes 101684 (99.3 KiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 0 bytes 0 (0.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536 inet 127.0.0.1 netmask 255.0.0.0 inet6 ::1 prefixlen 128 scopeid 0x10<host> loop txqueuelen 1000 (Local Loopback) RX packets 4 bytes 364 (364.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 4 bytes 364 (364.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 sit0: flags=128<NOARP> mtu 1480 sit txqueuelen 1000 (IPv6-in-IPv4) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 0 bytes 0 (0.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 wan: flags=4098<BROADCAST,MULTICAST> mtu 1500 ether 5e:e5:7a:38:3a:d7 txqueuelen 1000 (Ethernet) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 0 bytes 0 (0.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 root@debian:~# ping 192.168.1.1 connect: Network is unreachable root@debian:~# ifconfig -a eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet6 fe80::5ce5:7aff:fe38:3ad7 prefixlen 64 scopeid 0x20<link> ether 5e:e5:7a:38:3a:d7 txqueuelen 532 (Ethernet) RX packets 267 bytes 108202 (105.6 KiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 52 bytes 9344 (9.1 KiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 device interrupt 27 ip6tnl0: flags=128<NOARP> mtu 1452 unspec 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 txqueuelen 1000 (UNSPEC) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 0 bytes 0 (0.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 lan0: flags=4098<BROADCAST,MULTICAST> mtu 1500 ether 5e:e5:7a:38:3a:d7 txqueuelen 1000 (Ethernet) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 0 bytes 0 (0.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 lan1: flags=4098<BROADCAST,MULTICAST> mtu 1500 ether 5e:e5:7a:38:3a:d7 txqueuelen 1000 (Ethernet) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 0 bytes 0 (0.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 lan2: flags=4098<BROADCAST,MULTICAST> mtu 1500 ether 5e:e5:7a:38:3a:d7 txqueuelen 1000 (Ethernet) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 0 bytes 0 (0.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 lan3: flags=4098<BROADCAST,MULTICAST> mtu 1500 ether 5e:e5:7a:38:3a:d7 txqueuelen 1000 (Ethernet) RX packets 267 bytes 102328 (99.9 KiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 0 bytes 0 (0.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536 inet 127.0.0.1 netmask 255.0.0.0 inet6 ::1 prefixlen 128 scopeid 0x10<host> loop txqueuelen 1000 (Local Loopback) RX packets 4 bytes 364 (364.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 4 bytes 364 (364.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 sit0: flags=128<NOARP> mtu 1480 sit txqueuelen 1000 (IPv6-in-IPv4) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 0 bytes 0 (0.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 wan: flags=4098<BROADCAST,MULTICAST> mtu 1500 ether 5e:e5:7a:38:3a:d7 txqueuelen 1000 (Ethernet) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 0 bytes 0 (0.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
And the DTS:
/*
* Device Tree file for Marvell Armada 370 Reference Design board
* (RD-88F6710-A1)
*
* Copied from arch/arm/boot/dts/armada-370-db.dts
*
* Copyright (C) 2013 Florian Fainelli <florian@openwrt.org>
*
* This file is dual-licensed: you can use it either under the terms
* of the GPL or the X11 license, at your option. Note that this dual
* licensing only applies to this file, and not this project as a
* whole.
*
* a) This file is free software; you can redistribute it and/or
* modify it under the terms of the GNU General Public License as
* published by the Free Software Foundation; either version 2 of the
* License, or (at your option) any later version.
*
* This file is distributed in the hope that it will be useful,
* but WITHOUT ANY WARRANTY; without even the implied warranty of
* MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
* GNU General Public License for more details.
*
* Or, alternatively,
*
* b) Permission is hereby granted, free of charge, to any person
* obtaining a copy of this software and associated documentation
* files (the "Software"), to deal in the Software without
* restriction, including without limitation the rights to use,
* copy, modify, merge, publish, distribute, sublicense, and/or
* sell copies of the Software, and to permit persons to whom the
* Software is furnished to do so, subject to the following
* conditions:
*
* The above copyright notice and this permission notice shall be
* included in all copies or substantial portions of the Software.
*
* THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,
* EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES
* OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND
* NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT
* HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY,
* WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING
* FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR
* OTHER DEALINGS IN THE SOFTWARE.
*
* Note: this Device Tree assumes that the bootloader has remapped the
* internal registers to 0xf1000000 (instead of the default
* 0xd0000000). The 0xf1000000 is the default used by the recent,
* DT-capable, U-Boot bootloaders provided by Marvell. Some earlier
* boards were delivered with an older version of the bootloader that
* left internal registers mapped at 0xd0000000. If you are in this
* situation, you should either update your bootloader (preferred
* solution) or the below Device Tree should be adjusted.
*/
/dts-v1/;
#include <dt-bindings/input/input.h>
#include <dt-bindings/gpio/gpio.h>
#include "armada-370.dtsi"
/ {
model = "RTNAS V3";
compatible = "marvell,armada-370-rtnasv3","marvell,a370-rd", "marvell,armada370", "marvell,armada-370-xp";
chosen {
stdout-path = "serial0:115200n8";
};
memory@0 {
device_type = "memory";
reg = <0x00000000 0x40000000>; /* 1024 MB */
};
soc {
ranges = <MBUS_ID(0xf0, 0x01) 0 0xf1000000 0x100000
MBUS_ID(0x01, 0xe0) 0 0xfff00000 0x100000
MBUS_ID(0x09, 0x01) 0 0xf1100000 0x10000>;
internal-regs {
serial@12000 {
status = "okay";
};
sata@a0000 {
nr-ports = <2>;
status = "okay";
};
ethernet@70000 {
status = "disabled";
phy-mode = "sgmii";
};
ethernet@74000 {
pinctrl-0 = <&ge1_rgmii_pins>;
pinctrl-names = "default";
status = "okay";
phy-mode = "rgmii-id";
fixed-link {
speed = <1000>;
full-duplex;
};
};
mvsdio@d4000 {
pinctrl-0 = <&sdio_pins1>;
pinctrl-names = "default";
status = "disabled";
/* No CD or WP GPIOs */
broken-cd;
};
usb@50000 {
status = "okay";
};
usb@51000 {
status = "okay";
};
nand@d0000 {
status = "okay";
num-cs = <2>;
marvell,nand-keep-config;
marvell,nand-enable-arbiter;
nand-on-flash-bbt;
nand-ecc-strength = <0x4>;
nand-ecc-step-size = <0x200>;
partition@0 {
label = "u-boot";
reg = <0x0 0x400000>;
};
partition@400000 {
label = "uboot_env";
reg = <0x400000 0x400000>;
};
partition@800000 {
label = "vendor";
reg = <0x800000 0x400000>;
};
partition@c00000 {
label = "unused";
reg = <0xc00000 0xc00000>;
};
partition@1800000 {
label = "kernel";
reg = <0x1800000 0x400000>;
};
partition@1c00000 {
label = "ubi";
reg = <0x1c00000 0x3e400000>;
};
partition@40000000 {
label = "syscfg";
reg = <0x40000000 0xbbc00000>;
};
};
};
};
dsa {
status = "disabled";
compatible = "marvell,dsa";
#address-cells = <2>;
#size-cells = <0>;
dsa,ethernet = <ð1>;
dsa,mii-bus = <&mdio>;
switch@0 {
#address-cells = <1>;
#size-cells = <0>;
reg = <0x10 0>; /* MDIO address 16, switch 0 in tree */
port@0 {
reg = <0>;
label = "lan0";
};
port@1 {
reg = <1>;
label = "lan1";
};
port@2 {
reg = <2>;
label = "lan2";
};
port@3 {
reg = <3>;
label = "lan3";
};
port@4 {
reg = <4>;
label = "wan";
};
port@5 {
reg = <5>;
label = "cpu";
};
};
};
};
&pciec {
status = "okay";
/* Internal mini-PCIe connector */
pcie@1,0 {
/* Port 0, Lane 0 */
status = "okay";
};
/* Internal mini-PCIe connector */
pcie@2,0 {
/* Port 1, Lane 0 */
status = "okay";
};
};
&mdio {
pinctrl-0 = <&mdio_pins>;
pinctrl-names = "default";
phy0: ethernet-phy@0 {
reg = <0>;
};
switch0@0 {
compatible = "marvell,mv88e6085";
#address-cells = <1>;
#size-cells = <0>;
reg = <0x0>;
ports {
#address-cells = <1>;
#size-cells = <0>;
port@0 {
reg = <0>;
label = "lan0";
};
port@1 {
reg = <1>;
label = "lan1";
};
port@2 {
reg = <2>;
label = "lan2";
};
port@3 {
reg = <3>;
label = "lan3";
};
port@4 {
reg = <4>;
label = "wan";
};
port@5 {
reg = <5>;
label = "cpu";
ethernet = <ð1>;
fixed-link {
speed = <1000>;
full-duplex;
};
};
};
};
};
But the MDIO still have error:
mdio_bus f1072004.mdio-mii: MDIO device at address 0 is missing.
|
Re: armada 370 (88f6710) mainline uboot support August 25, 2018 08:46PM |
Admin Registered: 13 years ago Posts: 18,543 |
wacke,
Try changing the compatible attribute to to 6171.
They use common code, but there should be some differences.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Edited 1 time(s). Last edit at 08/25/2018 08:47PM by bodhi.
Try changing the compatible attribute to to 6171.
They use common code, but there should be some differences.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Edited 1 time(s). Last edit at 08/25/2018 08:47PM by bodhi.
|
Re: armada 370 (88f6710) mainline uboot support August 25, 2018 09:56PM |
Registered: 8 years ago Posts: 166 |
bodhi Wrote:
-------------------------------------------------------
> wacke,
>
> Try changing the compatible attribute to to 6171.
>
> They use common code, but there should be some
> differences.
But Documentation/devicetree/bindings/net/dsa/marvell.txt says:
And all the interfaces working properly.So just ignore this MDIO error?
-------------------------------------------------------
> wacke,
>
> Try changing the compatible attribute to to 6171.
>
> They use common code, but there should be some
> differences.
But Documentation/devicetree/bindings/net/dsa/marvell.txt says:
The compatibility string is used only to find an identification register, which is at a different MDIO base address in different switch families. - "marvell,mv88e6085" : Switch has base address 0x10. Use with models: 6085, 6095, 6097, 6123, 6131, 6141, 6161, 6165, 6171, 6172, 6175, 6176, 6185, 6240, 6320, 6321, 6341, 6350, 6351, 6352 - "marvell,mv88e6190" : Switch has base address 0x00. Use with models: 6190, 6190X, 6191, 6290, 6390, 6390X
And all the interfaces working properly.So just ignore this MDIO error?
|
Re: armada 370 (88f6710) mainline uboot support August 25, 2018 10:21PM |
Admin Registered: 13 years ago Posts: 18,543 |
Actually, that error should not be ignored.
So I've checked the Linksys EA4500 which has 6171 switch chip. Try that definition :)
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
So I've checked the Linksys EA4500 which has 6171 switch chip. Try that definition :)
switch@16,0 {
#address-cells = <1>;
#size-cells = <0>;
reg = <16 0>; /* MDIO address 16, switch 0 in tree */
&mdio {
status = "okay";
switch@10 {
compatible = "marvell,mv88e6085";
#address-cells = <1>;
#size-cells = <0>;
reg = <16>;
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: armada 370 (88f6710) mainline uboot support August 25, 2018 11:39PM |
Registered: 8 years ago Posts: 166 |
bodhi Wrote:
-------------------------------------------------------
> Actually, that error should not be ignored.
>
> So I've checked the Linksys EA4500 which has 6171
> switch chip. Try that definition :)
>
>
>
>
>
Hi,bodhi,
After change the reg to 16,the DSA driver got no activity again...
Then I just remove the phy node:
Edited 1 time(s). Last edit at 08/25/2018 11:59PM by wacke.
-------------------------------------------------------
> Actually, that error should not be ignored.
>
> So I've checked the Linksys EA4500 which has 6171
> switch chip. Try that definition :)
>
>
>
> switch@16,0 {
> #address-cells = <1>;
> #size-cells = <0>;
> reg = <16 0>; /* MDIO
> address 16, switch 0 in tree */
>
>
>
>
>
> &mdio {
> status = "okay";
>
> switch@10 {
> compatible = "marvell,mv88e6085";
> #address-cells = <1>;
> #size-cells = <0>;
> reg = <16>;
>
Hi,bodhi,
After change the reg to 16,the DSA driver got no activity again...
Then I just remove the phy node:
&mdio {
pinctrl-0 = <&mdio_pins>;
pinctrl-names = "default";
switch0@0 {
compatible = "marvell,mv88e6085";
#address-cells = <1>;
#size-cells = <0>;
reg = <0x0>;
ports {
#address-cells = <1>;
#size-cells = <0>;
port@0 {
reg = <0>;
label = "lan0";
};
port@1 {
reg = <1>;
label = "lan1";
};
port@2 {
reg = <2>;
label = "lan2";
};
port@3 {
reg = <3>;
label = "lan3";
};
port@4 {
reg = <4>;
label = "wan";
};
port@5 {
reg = <5>;
label = "cpu";
ethernet = <ð1>;
fixed-link {
speed = <1000>;
full-duplex;
};
};
};
};
};
And that MDIO error was gone(all ports working properly)....
Loading file "/boot/uImage" from ide device 1:1 (hdb1) 4343453 bytes read ## Booting kernel from Legacy Image at 00800000 ... Image Name: Linux-4.16.7-mvebu-tld-1 Created: 1970-01-01 0:03:30 UTC Image Type: ARM Linux Kernel Image (uncompressed) Data Size: 4343389 Bytes = 4.1 MiB Load Address: 00008000 Entry Point: 00008000 Verifying Checksum ... OK Loading Kernel Image ... OK OK Starting kernel ... Uncompressing Linux... done, booting the kernel. [ 0.000000] Booting Linux on physical CPU 0x0 [ 0.000000] Linux version 4.16.7-mvebu-tld-1 (root@tldDebianVM) (gcc version 5.4.0 20160609 (Ubuntu/Linaro 5.4.0-6ubuntu1~16.04.9)) #1 SMP PREEMPT Fri May 4 21:09:30 PDT 2018 [ 0.000000] CPU: ARMv7 Processor [561f5811] revision 1 (ARMv7), cr=10c5387d [ 0.000000] CPU: PIPT / VIPT nonaliasing data cache, PIPT instruction cache [ 0.000000] OF: fdt: Machine model: RTNAS V3 [ 0.000000] Memory policy: Data cache writeback [ 0.000000] CPU: All CPU(s) started in SVC mode. [ 0.000000] random: get_random_bytes called from start_kernel+0x80/0x404 with crng_init=0 [ 0.000000] percpu: Embedded 18 pages/cpu @(ptrval) s40972 r8192 d24564 u73728 [ 0.000000] Built 1 zonelists, mobility grouping on. Total pages: 260608 [ 0.000000] Kernel command line: rootdelay=10 root=/dev/sda1 console=ttyS0,115200 [ 0.000000] Dentry cache hash table entries: 131072 (order: 7, 524288 bytes) [ 0.000000] Inode-cache hash table entries: 65536 (order: 6, 262144 bytes) [ 0.000000] Memory: 1025016K/1048576K available (9216K kernel code, 762K rwdata, 2236K rodata, 1024K init, 335K bss, 23560K reserved, 0K cma-reserved, 262144K highmem) [ 0.000000] Virtual kernel memory layout: [ 0.000000] vector : 0xffff0000 - 0xffff1000 ( 4 kB) [ 0.000000] fixmap : 0xffc00000 - 0xfff00000 (3072 kB) [ 0.000000] vmalloc : 0xf0800000 - 0xff800000 ( 240 MB) [ 0.000000] lowmem : 0xc0000000 - 0xf0000000 ( 768 MB) [ 0.000000] pkmap : 0xbfe00000 - 0xc0000000 ( 2 MB) [ 0.000000] modules : 0xbf000000 - 0xbfe00000 ( 14 MB) [ 0.000000] .text : 0x(ptrval) - 0x(ptrval) (10208 kB) [ 0.000000] .init : 0x(ptrval) - 0x(ptrval) (1024 kB) [ 0.000000] .data : 0x(ptrval) - 0x(ptrval) ( 763 kB) [ 0.000000] .bss : 0x(ptrval) - 0x(ptrval) ( 336 kB) [ 0.000000] Preemptible hierarchical RCU implementation. [ 0.000000] RCU restricting CPUs from NR_CPUS=4 to nr_cpu_ids=1. [ 0.000000] Tasks RCU enabled. [ 0.000000] RCU: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=1 [ 0.000000] NR_IRQS: 16, nr_irqs: 16, preallocated irqs: 16 [ 0.000000] L2C: DT/platform modifies aux control register: 0x12086302 -> 0x1a086302 [ 0.000000] Aurora cache controller enabled, 4 ways, 256 kB [ 0.000000] Aurora: CACHE_ID 0x00000100, AUX_CTRL 0x1a086302 [ 0.000000] Switching to timer-based delay loop, resolution 53ns [ 0.000006] sched_clock: 32 bits at 18MHz, resolution 53ns, wraps every 114840871909ns [ 0.000024] clocksource: armada_370_xp_clocksource: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 102208375848 ns [ 0.000629] Console: colour dummy device 80x30 [ 0.000659] Calibrating delay loop (skipped), value calculated using timer frequency.. 37.39 BogoMIPS (lpj=186996) [ 0.000674] pid_max: default: 32768 minimum: 301 [ 0.000827] Security Framework initialized [ 0.000921] Mount-cache hash table entries: 2048 (order: 1, 8192 bytes) [ 0.000937] Mountpoint-cache hash table entries: 2048 (order: 1, 8192 bytes) [ 0.001619] CPU: Testing write buffer coherency: ok [ 0.001908] CPU0: thread -1, cpu 0, socket -1, mpidr 0 [ 0.040159] Setting up static identity map for 0x100000 - 0x100060 [ 0.040482] mvebu-soc-id: MVEBU SoC ID=0x6710, Rev=0x1 [ 0.040582] mvebu-pmsu: Initializing Power Management Service Unit [ 0.060096] Hierarchical SRCU implementation. [ 0.100100] smp: Bringing up secondary CPUs ... [ 0.100118] smp: Brought up 1 node, 1 CPU [ 0.100127] SMP: Total of 1 processors activated (37.39 BogoMIPS). [ 0.100136] CPU: All CPU(s) started in SVC mode. [ 0.100907] devtmpfs: initialized [ 0.110231] VFP support v0.3: implementor 56 architecture 2 part 20 variant 9 rev 6 [ 0.110703] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns [ 0.110723] futex hash table entries: 256 (order: 2, 16384 bytes) [ 0.110941] prandom: seed boundary self test passed [ 0.113203] prandom: 100 self tests passed [ 0.113212] pinctrl core: initialized pinctrl subsystem [ 0.114079] NET: Registered protocol family 16 [ 0.114490] DMA: preallocated 256 KiB pool for atomic coherent allocations [ 0.114916] audit: initializing netlink subsys (disabled) [ 0.115194] audit: type=2000 audit(0.110:1): state=initialized audit_enabled=0 res=1 [ 0.120978] cpuidle: using governor ladder [ 0.121019] cpuidle: using governor menu [ 0.121156] hw-breakpoint: debug architecture 0x4 unsupported. [ 0.220804] vgaarb: loaded [ 0.221108] SCSI subsystem initialized [ 0.230465] usbcore: registered new interface driver usbfs [ 0.230518] usbcore: registered new interface driver hub [ 0.230584] usbcore: registered new device driver usb [ 0.230799] media: Linux media interface: v0.10 [ 0.230842] Linux video capture interface: v2.00 [ 0.230921] rc_core: IR Remote Control driver registered, major 250 [ 0.234869] clocksource: Switched to clocksource armada_370_xp_clocksource [ 0.300003] VFS: Disk quotas dquot_6.6.0 [ 0.300092] VFS: Dquot-cache hash table entries: 1024 (order 0, 4096 bytes) [ 0.321493] NET: Registered protocol family 2 [ 0.322716] tcp_listen_portaddr_hash hash table entries: 512 (order: 0, 6144 bytes) [ 0.322741] TCP established hash table entries: 8192 (order: 3, 32768 bytes) [ 0.322796] TCP bind hash table entries: 8192 (order: 4, 65536 bytes) [ 0.322867] TCP: Hash tables configured (established 8192 bind 8192) [ 0.322966] UDP hash table entries: 512 (order: 2, 16384 bytes) [ 0.322990] UDP-Lite hash table entries: 512 (order: 2, 16384 bytes) [ 0.323156] NET: Registered protocol family 1 [ 0.353881] RPC: Registered named UNIX socket transport module. [ 0.353896] RPC: Registered udp transport module. [ 0.353903] RPC: Registered tcp transport module. [ 0.353910] RPC: Registered tcp NFSv4.1 backchannel transport module. [ 0.354243] NetWinder Floating Point Emulator V0.97 (double precision) [ 0.354542] hw perfevents: enabled with armv7_cortex_a9 PMU driver, 7 counters available [ 0.357263] Initialise system trusted keyrings [ 0.357310] Key type blacklist registered [ 0.358282] workingset: timestamp_bits=30 max_order=18 bucket_order=0 [ 0.358397] zbud: loaded [ 0.359365] NFS: Registering the id_resolver key type [ 0.359395] Key type id_resolver registered [ 0.359403] Key type id_legacy registered [ 0.359419] nfs4filelayout_init: NFSv4 File Layout Driver Registering... [ 0.359427] Installing knfsd (copyright (C) 1996 okir@monad.swb.de). [ 0.359680] jffs2: version 2.2. (NAND) (SUMMARY) �© 2001-2006 Red Hat, Inc. [ 0.360444] orangefs_debugfs_init: called with debug mask: :none: :0: [ 0.360625] orangefs_init: module version upstream loaded [ 0.366546] Key type asymmetric registered [ 0.366562] Asymmetric key parser 'x509' registered [ 0.366629] bounce: pool size: 64 pages [ 0.366718] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 246) [ 0.366729] io scheduler noop registered [ 0.366737] io scheduler deadline registered [ 0.366830] io scheduler cfq registered (default) [ 0.368437] armada-370-pinctrl f1018000.pin-ctrl: registered pinctrl driver [ 0.372833] mvebu-gpio: probe of f1018180.gpio failed with error -2 [ 0.376514] mvebu-pcie soc:pcie@82000000: PCI host bridge to bus 0000:00 [ 0.376535] pci_bus 0000:00: root bus resource [io 0x1000-0xfffff] [ 0.376546] pci_bus 0000:00: root bus resource [mem 0xf8000000-0xffdfffff] [ 0.376557] pci_bus 0000:00: root bus resource [bus 00-ff] [ 0.377324] PCI: bus0: Fast back to back transfers disabled [ 0.377347] pci 0000:00:01.0: bridge configuration invalid ([bus 00-00]), reconfiguring [ 0.377369] pci 0000:00:02.0: bridge configuration invalid ([bus 00-00]), reconfiguring [ 0.404896] PCI: bus1: Fast back to back transfers enabled [ 0.434843] PCI: bus2: Fast back to back transfers enabled [ 0.434919] pci 0000:00:01.0: BAR 14: assigned [mem 0xf8000000-0xf80fffff] [ 0.434932] pci 0000:00:02.0: BAR 14: assigned [mem 0xf8200000-0xf84fffff] [ 0.434948] pci 0000:01:00.0: BAR 0: assigned [mem 0xf8000000-0xf801ffff 64bit] [ 0.434963] pci 0000:01:00.0: BAR 0: error updating (0xf8000004 != 0xffffffff) [ 0.434975] pci 0000:01:00.0: BAR 0: error updating (high 0x000000 != 0xffffffff) [ 0.434987] pci 0000:01:00.0: BAR 6: assigned [mem 0xf8020000-0xf802ffff pref] [ 0.434998] pci 0000:00:01.0: PCI bridge to [bus 01] [ 0.435012] pci 0000:00:01.0: bridge window [mem 0xf8000000-0xf80fffff] [ 0.435029] pci 0000:02:00.0: BAR 0: assigned [mem 0xf8200000-0xf83fffff 64bit] [ 0.435042] pci 0000:02:00.0: BAR 0: error updating (0xf8200004 != 0xffffffff) [ 0.435053] pci 0000:02:00.0: BAR 0: error updating (high 0x000000 != 0xffffffff) [ 0.435064] pci 0000:02:00.0: BAR 6: assigned [mem 0xf8400000-0xf840ffff pref] [ 0.435074] pci 0000:00:02.0: PCI bridge to [bus 02] [ 0.435086] pci 0000:00:02.0: bridge window [mem 0xf8200000-0xf84fffff] [ 0.435208] pcieport 0000:00:01.0: enabling device (0140 -> 0142) [ 0.435319] pcieport 0000:00:02.0: enabling device (0140 -> 0142) [ 0.436231] mv_xor f1060800.xor: Marvell shared XOR driver [ 0.495803] mv_xor f1060800.xor: Marvell XOR (Registers Mode): ( xor cpy intr ) [ 0.496228] mv_xor f1060900.xor: Marvell shared XOR driver [ 0.555816] mv_xor f1060900.xor: Marvell XOR (Registers Mode): ( xor cpy intr ) [ 0.696093] Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled [ 0.698702] console [ttyS0] disabled [ 0.720131] f1012000.serial: ttyS0 at MMIO 0xf1012000 (irq = 19, base_baud = 12500000) is a 16550A [ 1.590484] console [ttyS0] enabled [ 1.596190] sata_mv f10a0000.sata: slots 32 ports 2 [ 1.614314] scsi host0: sata_mv [ 1.628376] scsi host1: sata_mv [ 1.632013] ata1: SATA max UDMA/133 irq 28 [ 1.636363] ata2: SATA max UDMA/133 irq 28 [ 1.641347] pxa3xx-nand f10d0000.nand: This platform can't do DMA on this device [ 1.649833] pxa3xx-nand f10d0000.nand: non-supported command 5 [ 1.655776] nand: Failed to detect ONFI extended param page [ 1.661501] nand: device found, Manufacturer ID: 0x2c, Chip ID: 0x68 [ 1.667989] nand: Micron MT29F32G08CBACAWP [ 1.672101] nand: 4096 MiB, MLC, erase size: 1024 KiB, page size: 4096, OOB size: 224 [ 1.680292] pxa3xx-nand f10d0000.nand: ECC strength 16, ECC step size 2048 [ 1.688451] Bad block table found at page 1048320, version 0x01 [ 1.695297] Bad block table found at page 1048064, version 0x01 [ 1.701665] nand_read_bbt: bad block at 0x000005a00000 [ 1.706883] nand_read_bbt: bad block at 0x000005b00000 [ 1.712287] 7 ofpart partitions found on MTD device pxa3xx_nand-0 [ 1.718560] Creating 7 MTD partitions on "pxa3xx_nand-0": [ 1.723995] 0x000000000000-0x000000400000 : "u-boot" [ 1.730502] 0x000000400000-0x000000800000 : "uboot_env" [ 1.737458] 0x000000800000-0x000000c00000 : "vendor" [ 1.744086] 0x000000c00000-0x000001800000 : "unused" [ 1.750814] 0x000001800000-0x000001c00000 : "kernel" [ 1.757523] 0x000001c00000-0x000040000000 : "ubi" [ 1.765081] 0x000040000000-0x0000fbc00000 : "syscfg" [ 1.774992] nand: No NAND device found [ 1.778775] pxa3xx-nand f10d0000.nand: failed to scan nand at cs 1 [ 1.788099] libphy: Fixed MDIO Bus: probed [ 1.795714] libphy: orion_mdio_bus: probed [ 1.804460] mvneta f1074000.ethernet eth0: Using random mac address 3e:a7:47:c8:b0:a7 [ 1.814550] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver [ 1.821922] ehci-pci: EHCI PCI platform driver [ 1.826899] ehci-orion: EHCI orion driver [ 1.831142] orion-ehci f1050000.usb: EHCI Host Controller [ 1.836905] orion-ehci f1050000.usb: new USB bus registered, assigned bus number 1 [ 1.844656] orion-ehci f1050000.usb: irq 25, io mem 0xf1050000 [ 1.874814] orion-ehci f1050000.usb: USB 2.0 started, EHCI 1.00 [ 1.881031] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002 [ 1.887929] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [ 1.895231] usb usb1: Product: EHCI Host Controller [ 1.900134] usb usb1: Manufacturer: Linux 4.16.7-mvebu-tld-1 ehci_hcd [ 1.906645] usb usb1: SerialNumber: f1050000.usb [ 1.912084] hub 1-0:1.0: USB hub found [ 1.916144] hub 1-0:1.0: 1 port detected [ 1.920915] orion-ehci f1051000.usb: EHCI Host Controller [ 1.926710] orion-ehci f1051000.usb: new USB bus registered, assigned bus number 2 [ 1.934511] orion-ehci f1051000.usb: irq 26, io mem 0xf1051000 [ 1.964814] orion-ehci f1051000.usb: USB 2.0 started, EHCI 1.00 [ 1.971031] usb usb2: New USB device found, idVendor=1d6b, idProduct=0002 [ 1.977914] ata1: SATA link down (SStatus 0 SControl F300) [ 1.983481] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [ 1.990778] usb usb2: Product: EHCI Host Controller [ 1.995829] usb usb2: Manufacturer: Linux 4.16.7-mvebu-tld-1 ehci_hcd [ 2.002333] usb usb2: SerialNumber: f1051000.usb [ 2.007751] hub 2-0:1.0: USB hub found [ 2.011737] hub 2-0:1.0: 1 port detected [ 2.017137] usbcore: registered new interface driver usblp [ 2.023382] usbcore: registered new interface driver usb-storage [ 2.031010] mousedev: PS/2 mouse device common for all mice [ 2.494821] ata2: SATA link up 3.0 Gbps (SStatus 123 SControl F300) [ 2.503448] ata2.00: ATA-7: JMicron, 100415, max UDMA/133 [ 2.508906] ata2.00: 7856128 sectors, multi 1: LBA48 [ 2.516404] ata2.00: configured for UDMA/133 [ 2.531341] scsi 1:0:0:0: Direct-Access ATA JMicron 15 PQ: 0 ANSI: 5 [ 2.540667] sd 1:0:0:0: [sda] 7856128 512-byte logical blocks: (4.02 GB/3.75 GiB) [ 2.549344] sd 1:0:0:0: [sda] Write Protect is off [ 2.554289] sd 1:0:0:0: [sda] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA [ 2.565498] sda: sda1 sda2 [ 2.570016] sd 1:0:0:0: [sda] Attached SCSI disk [ 3.124818] rtc-mv f1010300.rtc: internal RTC not ticking [ 3.130483] i2c /dev entries driver [ 3.156047] orion_wdt: Initial timeout 229 sec [ 3.164871] marvell-cesa f1090000.crypto: CESA device successfully registered [ 3.172746] hidraw: raw HID events driver (C) Jiri Kosina [ 3.179286] usbcore: registered new interface driver usbhid [ 3.185272] usbhid: USB HID core driver [ 3.189749] drop_monitor: Initializing network drop monitor service [ 3.196871] NET: Registered protocol family 10 [ 3.212375] Segment Routing with IPv6 [ 3.216304] sit: IPv6, IPv4 and MPLS over IPv4 tunneling driver [ 3.224144] NET: Registered protocol family 17 [ 3.229141] 8021q: 802.1Q VLAN Support v1.8 [ 3.233392] Key type dns_resolver registered [ 3.237883] ThumbEE CPU extension supported. [ 3.242185] Registering SWP/SWPB emulation handler [ 3.248019] registered taskstats version 1 [ 3.252141] Loading compiled-in X.509 certificates [ 3.257484] zswap: loaded using pool lzo/zbud [ 3.263838] Key type big_key registered [ 3.268452] Key type encrypted registered [ 3.274446] hctosys: unable to open rtc device (rtc0) [ 3.280580] Waiting 10 sec before mounting root device... [ 13.926278] EXT4-fs (sda1): mounting ext3 file system using the ext4 subsystem [ 13.952257] EXT4-fs (sda1): mounted filesystem with ordered data mode. Opts: (null) [ 13.960199] VFS: Mounted root (ext3 filesystem) readonly on device 8:1. [ 13.972277] devtmpfs: mounted [ 13.977185] Freeing unused kernel memory: 1024K [ 13.983423] Checked W+X mappings: passed, no W+X pages found INIT: version 2.88 booting [ 14.176614] random: fast init done [info] Using makefile-style concurrent boot in runlevel S. ERROR: could not open /proc/stat: No such file or directory findfs: unable to resolve 'LABEL=rootfs' [....] Files under mount point '/run' will be hidden. ... (warning). [....] Starting the hotplug events dispatcher: systemd-udevdstarting version 232 [ 15.535415] random: systemd-udevd: uninitialized urandom read (16 bytes read) [ 15.559360] random: systemd-udevd: uninitialized urandom read (16 bytes read) [ 15.575333] random: systemd-udevd: uninitialized urandom read (16 bytes read) . ok [....] Synthesizing the initial hotplug events...done. [....] Waiting for /dev to be fully populated...[ 17.139698] mv88e6085 f1072004.mdio-mii:00: switch 0x1710 detected: Marvell 88E6171, revision 2 [ 17.268794] sd 1:0:0:0: Attached scsi generic sg0 type 0 [ 17.492358] libphy: mv88e6xxx SMI: probed [ 17.828516] cfg80211: Loading compiled-in X.509 certificates for regulatory database [ 17.933730] cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7' [ 17.974024] platform regulatory.0: Direct firmware load for regulatory.db failed with error -2 [ 17.990601] cfg80211: failed to load regulatory.db [ 18.241634] ath9k 0000:01:00.0: enabling device (0000 -> 0002) [ 18.288096] ath10k_pci 0000:02:00.0: of_irq_parse_pci: failed with rc=134 [ 18.319579] ath: phy0: Mac Chip Rev 0xfffc0.f is not supported by this driver [ 18.370424] ath: phy0: Unable to initialize hardware; initialization status: -95 [ 18.378138] ath10k_pci 0000:02:00.0: Refused to change power state, currently in D3 [ 18.450808] ath9k 0000:01:00.0: Failed to initialize device [ 18.480292] ath9k: probe of 0000:01:00.0 failed with error -95 [ 18.507744] Generic PHY mv88e6xxx-0:00: attached PHY driver [Generic PHY] (mii_bus:phy_addr=mv88e6xxx-0:00, irq=POLL) [ 18.571496] Generic PHY mv88e6xxx-0:01: attached PHY driver [Generic PHY] (mii_bus:phy_addr=mv88e6xxx-0:01, irq=POLL) [ 18.595053] ath10k_pci 0000:02:00.0: failed to wake up device : -110 [ 18.625638] ath10k_pci: probe of 0000:02:00.0 failed with error -110 [ 18.640429] Generic PHY mv88e6xxx-0:02: attached PHY driver [Generic PHY] (mii_bus:phy_addr=mv88e6xxx-0:02, irq=POLL) [ 18.702361] Generic PHY mv88e6xxx-0:03: attached PHY driver [Generic PHY] (mii_bus:phy_addr=mv88e6xxx-0:03, irq=POLL) [ 18.765134] Generic PHY mv88e6xxx-0:04: attached PHY driver [Generic PHY] (mii_bus:phy_addr=mv88e6xxx-0:04, irq=POLL) [ 18.825478] DSA: tree 0 setup done. [....] Setting hostname to 'debian'...done. [....] Activating swap:. ok [ 22.652822] EXT4-fs (sda1): re-mounted. Opts: (null) [....] Will now check root file system:fsck from util-linux 2.29.2 [/sbin/fsck.ext3 (1) -- /] fsck.ext3 -y -C0 /dev/sda1 e2fsck 1.43.4 (31-Jan-2017) rootfs: clean, 24752/196608 files, 291782/786432 blocks . ok [ 22.968999] EXT4-fs (sda1): re-mounted. Opts: errors=remount-ro [....] Will now activate lvm and md swap:done. [info] Will now check all file systems. fsck from util-linux 2.29.2 Checking all file systems. LABEL=rootfs is mounted [....] Done checking file systems. A log is being saved in /var/log/fsck/checkfs if that location is writable.. ok [....] Cleaning up temporary files.... ok [....] Will now mount local filesystems:. ok [....] Will now activate swapfile swap:done. [....] Checking minimum space in /tmp...done. [....] Cleaning up temporary files.... ok [....] Setting kernel variables...done. [....] Initializing random number generator...done. [ 27.200524] mvneta f1074000.ethernet eth0: configuring for fixed/rgmii-id link mode [ 27.208458] mvneta f1074000.ethernet eth0: Link is Up - 1Gbps/Full - flow control off [....] Configuring network interfaces...Internet Systems Consortium DHCP Client 4.3.5 Copyright 2004-2016 Internet Systems Consortium. All rights reserved. For info, please visit https://www.isc.org/software/dhcp/ Listening on LPF/eth0/3e:a7:47:c8:b0:a7 Sending on LPF/eth0/3e:a7:47:c8:b0:a7 Sending on Socket/fallback DHCPREQUEST of 192.168.1.116 on eth0 to 255.255.255.255 port 67
Edited 1 time(s). Last edit at 08/25/2018 11:59PM by wacke.
|
Re: armada 370 (88f6710) mainline uboot support October 25, 2018 07:29PM |
Registered: 8 years ago Posts: 166 |
|
Re: armada 370 (88f6710) mainline uboot support October 26, 2018 03:40AM |
Admin Registered: 13 years ago Posts: 18,543 |
Hi wacke,
> I've found that the hardware I/O coherency is
> currently disabled for armada 370 in the mainline
> kernel,and this caused the throughput of my device
> was limited at about 250Mbit.Is there anyway to
> get the hardware I/O coherency working with the
> mainline kernel?Thanks.
I've looked at the mainline source which claim that that feature is not enabled for the 370. But the information is conflicting with other parts of the mainline code somewhere else :) The documentation does not seem to be correct.
I suspected that if we use the right info in the DTS for the 370, it would activate the feature.
and
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Edited 1 time(s). Last edit at 10/26/2018 03:55AM by bodhi.
> I've found that the hardware I/O coherency is
> currently disabled for armada 370 in the mainline
> kernel,and this caused the throughput of my device
> was limited at about 250Mbit.Is there anyway to
> get the hardware I/O coherency working with the
> mainline kernel?Thanks.
I've looked at the mainline source which claim that that feature is not enabled for the 370. But the information is conflicting with other parts of the mainline code somewhere else :) The documentation does not seem to be correct.
I suspected that if we use the right info in the DTS for the 370, it would activate the feature.
./arch/arm/boot/dts/armada-370-xp.dtsi: compatible = "marvell,coherency-fabric";
and
./arch/arm/boot/dts/armada-xp.dtsi: compatible = "marvell,armada-xp-cpu-config";
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Edited 1 time(s). Last edit at 10/26/2018 03:55AM by bodhi.
|
Re: armada 370 (88f6710) mainline uboot support October 26, 2018 08:24AM |
Registered: 8 years ago Posts: 166 |
bodhi Wrote:
-------------------------------------------------------
> I suspected that if we use the right info in the
> DTS for the 370, it would activate the feature.
Hi bodhi,
But Thomas Petazzoni (thomas.petazzoni@bootlin.com) replied my email:
And I'll try to modify the DTS to see if it works.Thanks.
-------------------------------------------------------
> I suspected that if we use the right info in the
> DTS for the 370, it would activate the feature.
Hi bodhi,
But Thomas Petazzoni (thomas.petazzoni@bootlin.com) replied my email:
> Is there anyway to get the hardware I/O coherency working for > amrada 370 with mainline kernel? Thanks very much. With the mainline kernel as it is, no, it is not possible. It is however possible to do it with some changes. The main issue (if I remember correctly) was that enabling HW I/O coherency requires to have the "shareable" attribute in the page tables. This is the case on SMP platforms, but since Armada 370 is not SMP, this bit is not enabled by Linux. And at the time this decision is made in the kernel, we don't yet have any information about the SoC we're using. So to sum up, there was no easy solution to implement this in a way that can be accepted upstream. However, if you can carry some external patches, it is definitely possible to get HW I/O coherency with Armada 370. Best regards, Thomas
And I'll try to modify the DTS to see if it works.Thanks.
|
Re: armada 370 (88f6710) mainline uboot support October 26, 2018 04:21PM |
Admin Registered: 13 years ago Posts: 18,543 |
wacke,
What Thomas said was what I thought. Because we can patch the kernel at an earlier point to take care of the shareable attribute.
This is something that will need to be test very thoughroughly because of the potential to corrupt data. I would be very careful and not having important data on the HDD while testing.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Quote
Thomas Petazzoni
> However, if you can carry some external patches,
> it is definitely
> possible to get HW I/O coherency with Armada 370.
What Thomas said was what I thought. Because we can patch the kernel at an earlier point to take care of the shareable attribute.
This is something that will need to be test very thoughroughly because of the potential to corrupt data. I would be very careful and not having important data on the HDD while testing.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: armada 370 (88f6710) mainline uboot support October 27, 2018 12:42AM |
Registered: 8 years ago Posts: 166 |
bodhi Wrote:
-------------------------------------------------------
> This is something that will need to be test very
> thoughroughly because of the potential to corrupt
> data. I would be very careful and not having
> important data on the HDD while testing.
Hi bodhi,
Can you send the patch to me? I have idle HDD here, and I can test the patch.Thanks.
-------------------------------------------------------
> This is something that will need to be test very
> thoughroughly because of the potential to corrupt
> data. I would be very careful and not having
> important data on the HDD while testing.
Hi bodhi,
Can you send the patch to me? I have idle HDD here, and I can test the patch.Thanks.
|
Re: armada 370 (88f6710) mainline uboot support October 27, 2018 04:40AM |
Admin Registered: 13 years ago Posts: 18,543 |
Hi wacke,
> Can you send the patch to me? I have idle HDD
> here, and I can test the patch.Thanks.
I have not created a patch! that was my thought (that it could be done). Based on Thomas's documentation and his response to you, which clearly described how to make it work, I thought it is possible.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
> Can you send the patch to me? I have idle HDD
> here, and I can test the patch.Thanks.
I have not created a patch! that was my thought (that it could be done). Based on Thomas's documentation and his response to you, which clearly described how to make it work, I thought it is possible.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: armada 370 (88f6710) mainline uboot support October 27, 2018 05:19AM |
Registered: 8 years ago Posts: 166 |
bodhi Wrote:
-------------------------------------------------------
> I have not created a patch! that was my thought
> (that it could be done). Based on Thomas's
> documentation and his response to you, which
> clearly described how to make it work, I thought
> it is possible.
Hi bodhi,
Waiting for your good news,Thanks.
-------------------------------------------------------
> I have not created a patch! that was my thought
> (that it could be done). Based on Thomas's
> documentation and his response to you, which
> clearly described how to make it work, I thought
> it is possible.
Hi bodhi,
Waiting for your good news,Thanks.
|
Re: armada 370 (88f6710) mainline uboot support November 04, 2018 07:45AM |
Registered: 8 years ago Posts: 166 |
|
Re: armada 370 (88f6710) mainline uboot support November 04, 2018 04:41PM |
Admin Registered: 13 years ago Posts: 18,543 |
wacke,
Not really. I have not looked into this yet (I have this thread open in a broswer tab so I won't forget).
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Not really. I have not looked into this yet (I have this thread open in a broswer tab so I won't forget).
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: armada 370 (88f6710) mainline uboot support November 06, 2018 04:29PM |
Admin Registered: 13 years ago Posts: 18,543 |
wacke,
I've realized that I could also check it on my NAS326 (Armada 380). The behavior should be the same as the Armada 370. For they both run SMP kernel on single processor.
The patch will look a little quirky as mainline is concerned. At that point, we don't have the DTB loaded yet, so we cannot use OF calls to figure out the box CPU model.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
I've realized that I could also check it on my NAS326 (Armada 380). The behavior should be the same as the Armada 370. For they both run SMP kernel on single processor.
The patch will look a little quirky as mainline is concerned. At that point, we don't have the DTB loaded yet, so we cannot use OF calls to figure out the box CPU model.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: armada 370 (88f6710) mainline uboot support November 06, 2018 06:43PM |
Registered: 8 years ago Posts: 166 |
