08-03-2016, 05:11 PM
@MarkHaysHarris777 : thanks, I was fearing this reply (which is the one you made to fire219 too 
)
I will when I have a bit more time and maybe my pine64 at hand.
@fire219 : thanks for the writeup, I'm sure it will be helpful as it probably is one of the most comprehensive I've read.
I did read your post on 4.7.0-rc1 but really I want to be able to build my own kernel to decide which bit I want (well it seems not much things are working anyway
)
1. I have, that's my base, but i'm working on filesystem for now
Took it from here : https://github.com/apritzel/pine64/tree/master/images
2. I used this page
http://linux-sunxi.org/Pine64#Mainline_kernel
and picked the "stable" kernel info from here
http://linux-sunxi.org/Mainline_Kernel_H...e_releases
As it turns out it's probably a 4.7.0 kernel as the "stable" kernel git link provided is actually not pointing to stable but to RC...
Did not go to icenowy's repo.
3. yep got that one covered I think : crossbuild-essential-arm64
4. went with
make defconfig
5. ARCH=arm64 make -j2 Image dtbs modules
went fairly short
6.
The dtb files are present in the firmware, why use the ones from the compilation ?
Is it not just a file describing the devices ? (may be a silly question)
I have the compiled kernel, so I should just copy that to this image, if I understand it right ?
From my findings, either at the root or in boot/
7. Ok that's another point where I'm not clear
From https://github.com/apritzel/pine64/blob/.../README.md
It seems it's my task to decide which partition and modify the boot script (not especially on p5)
I looked it up:
So it seems i can use p2 from the existing boot script ?
Why should i do an extended p5 in p2 ?
8&9. I should be able to do (although not a believer...)
I don't have the UART serial adapter...
)I will when I have a bit more time and maybe my pine64 at hand.
@fire219 : thanks for the writeup, I'm sure it will be helpful as it probably is one of the most comprehensive I've read.
I did read your post on 4.7.0-rc1 but really I want to be able to build my own kernel to decide which bit I want (well it seems not much things are working anyway
)1. I have, that's my base, but i'm working on filesystem for now
Took it from here : https://github.com/apritzel/pine64/tree/master/images
2. I used this page
http://linux-sunxi.org/Pine64#Mainline_kernel
and picked the "stable" kernel info from here
http://linux-sunxi.org/Mainline_Kernel_H...e_releases
As it turns out it's probably a 4.7.0 kernel as the "stable" kernel git link provided is actually not pointing to stable but to RC...
Did not go to icenowy's repo.
3. yep got that one covered I think : crossbuild-essential-arm64
4. went with
make defconfig
5. ARCH=arm64 make -j2 Image dtbs modules
went fairly short
6.
Code:
$ xzcat pine64_firmware-20160601.img.xz | dd of=/AARCH/firmware/apritzel.img bs=1M
$ fdisk -lu /AARCH/firmware/apritzel.img
$ mount -o loop,offset=$((2048 * 512)) /AARCH/firmware/apritzel.img /mnt
$ cd /mnt
$ ls
boot.scr.uimg sun50i-a64-pine64.dtb sun50i-a64-pine64-plus.dtbThe dtb files are present in the firmware, why use the ones from the compilation ?
Is it not just a file describing the devices ? (may be a silly question)
I have the compiled kernel, so I should just copy that to this image, if I understand it right ?
From my findings, either at the root or in boot/
7. Ok that's another point where I'm not clear
From https://github.com/apritzel/pine64/blob/.../README.md
It seems it's my task to decide which partition and modify the boot script (not especially on p5)
I looked it up:
Code:
root@debianCross:/mnt# ls
boot.scr.uimg sun50i-a64-pine64.dtb sun50i-a64-pine64-plus.dtb
root@debianCross:/mnt# dumpimage -i boot.scr.uim boot.cmd
dumpimage: Can't open "boot.scr.uim": No such file or directory
root@debianCross:/mnt# dumpimage -i boot.scr.uimg boot.cmd
root@debianCross:/mnt# ls
boot.cmd boot.scr.uimg sun50i-a64-pine64.dtb sun50i-a64-pine64-plus.dtb
root@debianCross:/mnt# cat boot.cmd
?fatload mmc 0 $kernel_addr_r Image
fatload mmc 0 $fdt_addr_r $fdtfile
setenv bootargs "console=ttyS0,115200n8 ro root=/dev/mmcblk0p5 rootwait earlycon=uart,mmio32,0x01c28000"
booti $kernel_addr_r - $fdt_addr_r
root@debianCross:/mnt#So it seems i can use p2 from the existing boot script ?
Why should i do an extended p5 in p2 ?
8&9. I should be able to do (although not a believer...)
I don't have the UART serial adapter...
