Op vrijdag 19 oktober 2018 13:32:25 CEST schreef Freek de Kruijf: > Op vrijdag 19 oktober 2018 09:52:32 CEST schreef Alexander Graf: > > Hi Freek, > > > > On 18.10.18 16:45, Freek de Kruijf wrote: > > > I noticed a number of images/support for Banana Pi systems having an > > > armv7 > > > type processor architecture. Also using names with sinovoipbpi in the > > > name > > > of the image. > > > > > > This name is also present in information about the Banana Pi M64 of > > > which > > > the processor architecture is aarch64. There is even an openSUSE > > > Tumbleweed image, dating a year back, which runs on this system. > > > > Where did you find that image? Who created it? > > There are two images on https://dev.banana-pi.org.cn/Image/BPI-M64/ > 2017-08-29-openSUSE-Tumbleweed-ARM-MATE-desktop-demo-bpi-m64-aarch64-sd- > emmc.img.zip > and > 2017-08-29-opensuse-xfce-desktop-demo-bpi-m64-aarch64-sd-emmc.img.zip > > I could not find who created these images. Asked for information in the > BananaPi forum, but got no answer. > > I used the MATE image and was able to update the system to the latest > Tumbleweed version. However a new kernel and initrd was generated but was > not put on the boot partition. So a reboot worked but showed the old > kernel. The boot partition mmcblk0p1 is not mounted only the root partition > mmcblk0p2. I compared the new initrd and Image in /boot on the root > partition with the old one on the boot partition (mmcblk0p1) and did not > try to replace these files. > > The eMMC is shown on the debian system as /dev/mmcblk1. There are other > partitions /dev/mmcblk1boot0, /dev/mmcblk1boot1, /dev/mmcblk1p0 and /dev/ > mmcblk1p1. The first two are read-only, the second two are currently a small > fat32 partition (256M and a large ext4 partition (6.7G). Although the first > two share the text mmcblk1, they do not show up in fdisk -l /dev/mmcblk1 > > In some documentation I found a type of shell script which reads a file > uEnv.txt and at the end contains a load command which first loads something > like a dtb file, second a file initrd.img and third a file Image. In the > boot partition are folder with names 1080p, 480p, 720p, lcd5 and lcd7. In > these folders are three files all with the same name in each folder. The > names are bootlogo.bmp, sun50i-a64-bpi-m64-lcd5.dtb and uEnv.txt. uEnv.txt > contains parameter definitions for console, kernel_filename, > initrd_filename and fdt_filename of which only fdt_filename receives > different values in the different folders. Both kernel_filename and > initrd_filename point to files in the parent folder of these > > I assume that this type of shell script exists somewhere on the bootX > devices.
I was wrong. This type shell script is in the boot partition (mmcblk0p1) of the openSUSE image. This partition looks quite different from the boot partition of the debian image. On the boot partition of the openSUSE image almost everything is in the top folder. There is only a dtb subfolder. On debian the real content starts in bananapi/bpi-m64/linux/ with the file Image etc. like mentioned before. The content of the shell script mentioned U-boot and also a command mkimage to generate images. On openSUSE I dont see a device /dev/mmcblk1, so the eMMC is invisible. > > The Banana Pi M64 seems to be A64 based, so I'm fairly sure from a > > kernel enablement point of view, we're in good shape. The only thing you > > might be missing would be the low level firmware bits. > > > > The idea openSUSE scenario for that would be if someone in the community > > did a "firmware installer" that really just writes U-Boot and ATF onto > > the eMMC. That U-Boot would then run distro boot and provide a workable > > DT for the platform. > > > > With that in place, you could just take the openSUSE installer iso, boot > > it, and install your system as with any other machine. No need for images. > > > > > Will there be support for the Banana Pi M64 with a more recent image? It > > > does seem very complicated to have such an image available in the ports > > > repository for aarch64. > > > > It's not very complicated to have such an image available. In fact, all > > it takes is someone who takes the pieces necessary (ATF, U-Boot), makes > > sure everything's mainline and built in our copies and then sends a > > submit request to the JeOS package to enable the port. > > > > > > Alex > > Do you want some more information on the openSUSE image? -- fr.gr. member openSUSE Freek de Kruijf -- To unsubscribe, e-mail: [email protected] To contact the owner, e-mail: [email protected]
