I compiled 4.9 image for R7800 based on blogic's code, but the result is the same.
The router does not boot properly. It actually ends up in the u-boot TFTP recovery mode (power led slowly blinking), so that I can just send a new firmware image via TFTP without needing to touch the reset button.
That makes me to think that somehow the kernel image gets invalidated very early. By u-boot?
That has now happened with both alternative 4.9 approaches.
But I have no serial console attached, so no additional info at this point.
I know how to handle scm, there's only 1 clock and that is <&rpmcc RPM_DAYTONA_FABRIC_CLK>, but your commit is missing 3xx patches that adds support for ipq806x rpm clock controller
looks like there are no ipq4xxx patches. can you update your tree with the missing patches you listed above so i can pull this lot into trunk as a replacement of what we have right now ? i'd like to start testing ipq4xxx after that
The clocks fix patch has been submitted to upstream kernel after I've found that upstream clocks are incorrect, so it's in 305 patch along with rpmcc node.
Btw qcom-scm driver doesn't contain ipq806x compatibility string, so in DT it should be set as apq8064 or I'll made a patch to add the compatibility into the driver.
I'll rebase upon current head and make PR in a while
I'll rearrange your patches and make it a single commit on top of a current head.
Will also add 4.9 files and config symbols.
At the moment I have no means to make it bootable as I cannot verify the error because neither me nor anyone I know have access to serial console on the device.
I'm almost done, verifying the compilation and editing patch headers to reflect real commits in linaro repo on code-aurora.
Well bad quality or not, but those patches that are not upstream make the device work rock steady actually.
That's definitely nand issues or smth in device tree not corresponding to new nand driver though I've updated it as well.
Backporting the nand driver into k4.4 leads to a boot loop.
In: serial
Out: serial
Err: serial
Net: MAC1 addr:0:3:7f:ba:db:1
athrs17_reg_init: complete
athrs17_vlan_config ...done
S17c init done
MAC2 addr:0:3:7f:ba:db:2
eth0, eth1
boot in 2 seconds
FirmwareRecovery: Now doing bootipq
MMC Device 0 not found
MMC Device 0 not found
Loading from nand1, offset 0x1f0000
Image Name: ARM LEDE Linux-4.9.10
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 1921894 Bytes = 1.8 MiB
Load Address: 42208000
Entry Point: 42208000
Automatic boot of image at addr 0x44000000 ...
Image Name: ARM LEDE Linux-4.9.10
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 1921894 Bytes = 1.8 MiB
Load Address: 42208000
Entry Point: 42208000
Verifying Checksum ... OK
Loading Kernel Image ... OK
OK
info: "mtdparts" not set
Using machid 0x1260 from environment