bodhi Wrote: ------------------------------------------------------- > Hi wacke, > > Sorry I was thinking out loud above :) > > Yes, it is possible. I meant that I'm thinking I > could test it on my NSA326 before postign the > patch for you to test. > > And the patch will be a little bit hackish, > because it must be done at a much earlier time &by wacke - uBoot
Hi,bodhi So it's impossible to get HW I/O coherency working on armada 370?by wacke - uBoot
Hi,bodhi Is there any update about the HW I/O coherency patch for armada370? Thanks.by wacke - uBoot
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.by wacke - uBoot
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.by wacke - uBoot
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: > Is there anyway to get the hardware I/O coherency working for > amrada 370 with mainline kernel? Thanks very much.by wacke - uBoot
Hi 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.by wacke - uBoot
bodhi Wrote: ------------------------------------------------------- > 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>;by wacke - uBoot
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: The compatibility string is used only to find an identification register, which is at a different MDIby wacke - uBoot
bodhi Wrote: ------------------------------------------------------- > wacke Wrote: > ------------------------------------------------------- > > bodhi Wrote: > > > ------------------------------------------------------- > > > Is this the mv88e6085 switch, and do you know > > if > > > register 0x10 is correct? your dmesg showed > no >by wacke - uBoot
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?by wacke - uBoot
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: /* * 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)by wacke - uBoot
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 connby wacke - uBoot
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?by wacke - uBoot
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?by wacke - uBoot
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 thatby wacke - uBoot
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: Soc :Marvell armada370 ARMv7 1.2G Switch: Marvell 88E6171R 100/1000M 5 Port DDR3 1G or 512MB Nby wacke - uBoot
Hi bodhi, The DTS need to update,or the pcie controller won't work properly,my latest working DTS: /* Device tree file for the QiZhiTong 501M V2 box. * * Copyright (c) 2015-2017 bodhi <mibodhi@gmail.com> * wacke <cao88yu@gmail.com> * * Based on * Marvell RD88F6181 A Board descrition * Andrew Lunn <andrew@lunn.ch> */ /dts-vby wacke - Debian
Hi bodhi, I've treid your dts patch,seems that the eth1 is working properly now. bootm: BOOTCMD4 Reset IDE: Marvell Serial ATA Adapter Integrated Sata device found [0 0 0]: Enable DMA mode (6) Device 0 @ 0 0: Model: JMicron Firm: 100415 Ser#: 00000000002E9 Type: Hard Disk Supports 48-biby wacke - Debian
Hi bodhi, It booted finnally: bootm: BOOTCMD4 Reset IDE: Marvell Serial ATA Adapter Integrated Sata device found [0 0 0]: Enable DMA mode (6) Device 0 @ 0 0: Model: JMicron Firm: 100415 Ser#: 00000000002E9 Type: Hard Disk Supports 48-bit addressing Capacity: 3836.0 MB = 3.7 GB (by wacke - Debian
Hi bodhi I've tried to boot with uinitrd,but faild: bootm: BOOTCMD4 Reset IDE: Marvell Serial ATA Adapter Integrated Sata device found [0 0 0]: Enable DMA mode (6) Device 0 @ 0 0: Model: JMicron Firm: 100415 Ser#: 00000000002E9 Type: Hard Disk Supports 48-bit addressing Capby wacke - Debian
Hi bodhi, the uboot env: MB302>> pri bootdelay=5 baudrate=9600 loads_echo=0 rootpath=/mnt/ARM_FS/ netmask=255.255.255.0 run_diag=yes console=console=ttyS0,9600 CASset=min MALLOC_len=1 ethprime=egiga0 bootargs_root=mem=512M root=/dev/ram bootargs_end=:::DB88FXX81:eth0:none image_name=uImage boottitle1=QiZhiTong Bootup bootcmd2=ide reset; ext2load ide 0:c 0x2000000 /boot/uIby wacke - Debian
Hi bodhi I've tried your 4.12.8 kernel,but didn't find the switch at all...(DTS used the latest with switch@10 and reg=10) boot log: MB302>> run bootcmd4 Reset IDE: Marvell Serial ATA Adapter Integrated Sata device found [0 0 0]: Enable DMA mode (6) Device 0 @ 0 0: Model: JMicron Firm: 100415 Ser#: 00000000002E9by wacke - Debian
I downloaded the linux-4.12.7,and didn't find the phy_read and phy_write patch.... the driver still use .phy_read = mv88e6165_phy_read, .phy_write = mv88e6165_phy_write, not .phy_read = mv88e6xxx_g2_smi_phy_read, .phy_write = mv88e6xxx_g2_smi_phy_write,by wacke - Debian
Hi bodhi, I've tried the switch@16 with reg=<16> output: Uncompressing Linux... done, booting the kernel. [ 0.000000] Booting Linux on physical CPU 0x0 [ 0.000000] Linux version 4.12.1-kirkwood-tld-1 (root@tldDebian) (gcc version 4.9.2 (Debian 4.9.2-10) ) #1 PREEMPT Sat Jul 15 21:40:50 PDT 2017 [ 0.000000] CPU: Feroceon 88FR131 [56251311] revision 1 (ARMv5TE), cr=000by wacke - Debian
Hi dodhi, I found some patches: https://py3.patchwork.dja.id.au/cover/20383/ https://py3.patchwork.dja.id.au/patch/20381/ https://py3.patchwork.dja.id.au/patch/20382/ and apply one of patches to kernel 4.9.x: the lede bootlog: Starting kernel ... [ 0.000000] Booting Linux on physical CPU 0x0 [ 0.000000] Linux version 4.9.37 (Wacke@HOME-Server) (gcc version 7.1.0 (LEDE GCCby wacke - Debian
Hi bodhi, I've tried switch@10,switch@16 and switch@a,nothing changed: [ 30.098888] mv88e6085 f1072004.mdio-bus-mii:0a: switch 0x161 detected: Marvell 88E6161, revision 2 [ 30.213967] libphy: mv88e6xxx SMI: probed [ 30.214037] DSA: switch 0 0 parsed [ 30.214040] DSA: tree 0 parsed [ 31.329260] orion_wdt: Initial timeout 21 sec [ 31.385499] mvsdio f1090000.mvsdio: Gotby wacke - Debian
Hi bodhi, I've finally got the debian rootfs mounting,boot log: bootm: BOOTCMD4 Reset IDE: Marvell Serial ATA Adapter Integrated Sata device found [0 0 0]: Enable DMA mode (6) Device 0 @ 0 0: Model: JMicron Firm: 100415 Ser#: 00000000002E9 Type: Hard Disk Supports 48-bit addressingby wacke - Debian
bodhi Wrote: ------------------------------------------------------- > wacke, > > Your uInitrd might be a bad one? We might have bee > n on a wild goose chase if that is true :) Hi bodhi, I don't know what's wrong about your latest rootfs.It can't mount my sd card propely and cause a kernel panic....It can't boot from mmc or am I missconfigured?by wacke - Debian
Hi bodhi, bodhi Wrote: ------------------------------------------------------- > wacke, > > 1. Have you tried the other driver? > > > compatible = "marvell, mv88e6190"; > I've tried,and I also tried mv88e6165,but no lucky.... > 2. Do you have a serial boot log for kernel 4.4 wh > en it was working that you can post here? > > Iby wacke - Debian