Op vrijdag 19 oktober 2018 09:52:32 CET 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?
> 
> 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.

Hi Alex,

continued my research and found 
https://github.com/BPI-SINOVOIP/BPI-Mainline-kernel . I did a git clone to get 
the content in folder BPI-Mainline-kernel. I 
installed the required packages mentioned in ./linux-4.19/Documentation/
process/changes.rst. However "oprofiled --version" is mentioned to check the 
version of the packet oprofile, but that did not work. The command should be 
"opreport --version".
After that I ran "./build_kernel_64.sh" in folder BPI-Mainline-kernel, which 
succeeded. I got a lot of generated files in ./linux-4.19/output/bpi-64/ among 
other a vmlinux, which seems to be the new kernel. Also a lot of drivers and 
modules have been generated.
I also downloaded the source of kernel 4.19.4 as a tar.xz, unpacked it in 
folder linux-4.19-4 in BPI-Mainline-kernel and adapted build_kernel_64.sh to 
enter linux-4.19.4. I also needed to copy a few file from linux-4.19 to 
linux-4.19.4, build_64.sh and linux-4.19/arch/arm64/bpi_64_defconfig.
After that I succeeded in building the kernel 4.19.4.

So far what I did. Now the experiment to make the kernel run. If you have any 
suggestions, please let me know.

-- 
fr.gr.

member openSUSE
Freek de Kruijf



-- 
To unsubscribe, e-mail: [email protected]
To contact the owner, e-mail: [email protected]

Reply via email to