[LEDE-DEV] [PATCH v3 1/5] ipq806x/nbg6817: add support for ZyXEL NBG6817

[André Valentin]

Hi!

Am 23.10.2016 um 16:38 schrieb Felix Fietkau:
> On 2016-10-23 16:25, André Valentin wrote:
>> CPU: 2x1.8GHz ARM, RAM: 512MiB
>> Storage: 4MiB serial Flash, 3.9GiB MMC
>> NIC: 2x1GBit/s, Switch with 5 external and 2 internal ports
>> WiFi: Dualband, ath10k 2.4GHz, 5GHz MU-MIMO
>>
>> For installation copy xx-mmcblk0p4-kernel.bin and xx-mmcblk0p5-rootfs-full.bin
>> to device. Then run:
>> cat xx-mmcblk0p4-kernel.bin > /dev/mmc0blk0p4
>> cat xx-mmcblk0p5-rootfs-full.bin > /dev/mmc0blk0p5
>> reboot -f
>>
>> For debugging serial console is easily visible on board, no soldering needed.
>>
>> Signed-off-by: André Valentin <avalentin at marcant.net>
>> ---
>>  .../linux/ipq806x/base-files/etc/board.d/01_leds   |   5 +
>>  .../ipq806x/base-files/etc/board.d/02_network      |   7 +
>>  .../etc/hotplug.d/firmware/11-ath10k-caldata       |   6 +
>>  target/linux/ipq806x/base-files/lib/ipq806x.sh     |   3 +
>>  target/linux/ipq806x/config-4.4                    |  18 +-
>>  .../arch/arm/boot/dts/qcom-ipq8065-nbg6817.dts     | 341 +++++++++++++++++++++
>>  target/linux/ipq806x/image/Makefile                |  26 +-
>>  .../linux/ipq806x/patches-4.4/800-devicetree.patch |   3 +-
>>  8 files changed, 401 insertions(+), 8 deletions(-)
>>  create mode 100644 target/linux/ipq806x/files/arch/arm/boot/dts/qcom-ipq8065-nbg6817.dts
>>
> 
>> diff --git a/target/linux/ipq806x/image/Makefile b/target/linux/ipq806x/image/Makefile
>> index b74f1a7..e7d4bf2 100644
>> --- a/target/linux/ipq806x/image/Makefile
>> +++ b/target/linux/ipq806x/image/Makefile
>> @@ -90,6 +90,19 @@ define Device/TpSafeImage
>>  endef
>>  DEVICE_VARS += TPLINK_BOARD_NAME
>>  
>> +define Device/ZyXELImage
>> +	PROFILES += $$(DEVICE_NAME)
>> +	FILESYSTEMS := squashfs
>> +	KERNEL_SUFFIX := -uImage
>> +	KERNEL = kernel-bin | append-dtb | uImage none | pad-to $$(KERNEL_SIZE)
>> +	KERNEL_NAME := zImage
>> +	IMAGES := sysupgrade.tar mmcblk0p5-rootfs.bin mmcblk0p5-rootfs-full.bin mmcblk0p4-kernel.bin
>> +	IMAGE/sysupgrade.tar := sysupgrade-tar
>> +	IMAGE/mmcblk0p5-rootfs.bin := append-rootfs | pad-rootfs | pad-to $$(BLOCKSIZE)
>> +	IMAGE/mmcblk0p5-rootfs-full.bin := append-rootfs | pad-rootfs | pad-to $$(ROOTFS_SIZE)
> Please drop the -full.bin, it wastes space.
> Change -rootfs.bin to append-rootfs | pad-extra 128k, similar to how it
> is handled on the octeon target. That is enough to ensure that it
> re-creates the overlay filesystem on first boot.
> Change the sysupgrade.tar image to:
> 
> IMAGE/sysupgrade.tar/squashfs := append-rootfs | pad-extra 128k | sysupgrade-tar rootfs=$$$$@
> 
I would not pad more than the blocksize to the rootfs. My sysupgrade process calculates the offset for the rootfs_data.
That would break.

That's why I added the full bin, for recovery cases. But I'll drop it.


> 
> - Felix
> 

-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 3691 bytes
Desc: S/MIME Cryptographic Signature
URL: <http://lists.infradead.org/pipermail/lede-dev/attachments/20161024/0bcfaac5/attachment.p7s>