From mboxrd@z Thu Jan 1 00:00:00 1970 From: Michael Tremer <michael.tremer@ipfire.org> To: sig-arm@lists.ipfire.org Subject: Re: Understanding boot process. Date: Tue, 24 Nov 2020 10:59:27 +0000 Message-ID: <D9378066-2FC7-4635-838F-57066A224781@ipfire.org> In-Reply-To: <175f6be62c6.b92ec548182277.4850897972109008957@fkardame.com> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============6416451524368796194==" List-Id: <sig-arm.lists.ipfire.org> --===============6416451524368796194== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Hello Furkan, You can find all build instructions in the lfs/ directory. For the kernel there is lfs/linux and there is lfs/u-boot. Configuration files for the kernel are in config/kernel. Best, -Michael > On 23 Nov 2020, at 20:14, Furkan Salman <tech(a)fkardame.com> wrote: >=20 > Hey, >=20 > Sorry I didn't release its only replying to you.=20 >=20 > I will be putting arm build to compile tonight and then see how long it wil= l take for my board while also looking into the kernel and uboot pkg.=20 >=20 > Can you just help me with the directories where pkg source are stored for k= ernel and uboot. >=20 > Thank you.=20 >=20 >=20 >=20 > ---- On Mon, 23 Nov 2020 18:02:29 +0300 michael.tremer(a)ipfire.org wrote -= --- >=20 > Hello Furkan,=20 >=20 > *please* copy the list. I can=E2=80=99t have a conversation in private only= with you. This conversation should be shared with other and documented, too.= =20 >=20 > > On 23 Nov 2020, at 11:42, Furkan Salman <tech(a)fkardame.com> wrote:=20 > >=20 > > Hey,=20 > > I don't understand by what you mean kernel that boots on arm?=20 >=20 > We have not ported the configuration and all the patches that we need, yet.= =20 >=20 > > I will try to reuse your kernel5.9 pkg of x86 and try to build the same f= or arm boards as I have all the config needed.=20 >=20 > This is not a good idea, because the kernels are slightly different.=20 >=20 > > I have been compiling kernels for arm board since 5.0 and maintaining ker= nel support so I hope I can do the same for ipfire soon. The only thing I mig= ht miss is the additional config needed for ipfire which we will come to late= r once I get the kernel to boot work 5.9.=20 >=20 > Exactly, if you just need a kernel that compiles, that is not very difficul= t to achieve. But we have a custom configuration and we have some patches tha= t make that kernel work better for us. Those need to be tested a lot before w= e can release them.=20 >=20 > > I will try to get it to boot and support you with ARM as I am aware arm i= s now in your priority list and its not easy to maintain but trust me it will= be easily once we have a working image for decent and powerful boards.=20 >=20 > That would be great. I personally do not have any ARM hardware that I use f= or development any more, but since there is interest in the community to supp= ort IPFire on as much hardware as possible, I would support this.=20 >=20 > > Thanks for replying. I will start looking into what I can do with my limi= ted knowledge of ipfire source;)=20 >=20 > Please ask questions. Development is not a quick job. It requires planning,= a lot of work and testing.=20 >=20 > It is not enough if a device just boots. It has to work. All of it. That in= cludes networking, power management, LEDs, etc. And it needs to perform. Ther= e is no point to support hardware for the fun of it. If people cannot use thi= s in production and they cannot rely on things working after the next update = it is worthless to spend time on getting it to work in the first place.=20 >=20 > Best,=20 > -Michael=20 >=20 > >=20 > > Will stay in touch with you here.=20 > >=20 > > Thanks.=20 > >=20 > >=20 > >=20 > > ---- On Mon, 23 Nov 2020 14:36:43 +0300 michael.tremer(a)ipfire.org wrote= ----=20 > >=20 > > Hello,=20 > >=20 > > Again, *please* copy the list.=20 > >=20 > > We currently do not have an ARM version of that kernel available. There i= s only a version for x86.=20 > >=20 > > As soon as we have a kernel that boots it will be announced on the develo= pment list. So, please watch this space :)=20 > >=20 > > -Michael=20 > >=20 > > > On 23 Nov 2020, at 11:34, Furkan Salman <tech(a)fkardame.com> wrote:=20 > > >=20 > > > I would love to be part of testing 5.9 as most of the boards are alread= y supported there.=20 > > >=20 > > > NanopiR2s=20 > > > RockpiE=20 > > > RockpiE3 (RockPiE with extra Lan, total 3 lan) this is development boar= d and not public yet.=20 > > >=20 > > > I have good understanding in Dts updates so it will be helpful for ipfi= re team. I don't mind supporting few devices myself.=20 > > >=20 > > > I will dedicate one of my amlogic device for building ipfire images onl= y.=20 > > >=20 > > > Please guide me on how I can build images with kernel 5.9 as I have had= build images with 4.9 only.=20 > > >=20 > > > Thanks=20 > > >=20 > > >=20 > > >=20 > > > ---- On Mon, 23 Nov 2020 14:31:06 +0300 michael.tremer(a)ipfire.org wro= te ----=20 > > >=20 > > > We currently have a version of kernel 5.9 that we are testing and we wi= ll target to move to 5.10 as soon as it comes out.=20 > > >=20 > > > I hope for a release early next year.=20 > > >=20 > > > Best,=20 > > > -Michael=20 > > >=20 > > > P.S. Please do not forget to copy the list.=20 > > >=20 > > > > On 23 Nov 2020, at 11:25, Furkan Salman <tech(a)fkardame.com> wrote: = > > > >=20 > > > > Hello Michael,=20 > > > >=20 > > > > Yes I see that EFI boot is already provied in aarch64 image.=20 > > > > I am flashing rockpie and using rock64 dtb or I will try it with rock= pie itself this time and report back to you by tonight or tomorrow max.=20 > > > >=20 > > > > When do you plan to move to kernel 5.4 ?=20 > > > >=20 > > > >=20 > > > >=20 > > > >=20 > > > > ---- On Mon, 23 Nov 2020 14:21:43 +0300 michael.tremer(a)ipfire.org w= rote ----=20 > > > >=20 > > > > Hello Furkan,=20 > > > >=20 > > > > Thanks for signing up and posting :)=20 > > > >=20 > > > > I suppose we are talking about ARM64:=20 > > > >=20 > > > > We currently only support systems that use EFI. If there is an EFI BI= OS, it will launch GRUB and hopefully return all required configuration to th= e kernel.=20 > > > >=20 > > > > > On 22 Nov 2020, at 15:00, Furkan Salman <tech(a)fkardame.com> wrote= :=20 > > > > >=20 > > > > > Hello IPFire Team,=20 > > > > >=20 > > > > > I would like to understand how do you get the grub to work on the a= rm images.=20 > > > > >=20 > > > > > I have RockPiE which is not supported by your project but I am will= ing to add support it by myself.=20 > > > > >=20 > > > > > Afaik I should be able to get it to boot with other Rk3328 board dt= b i have its mainline uboot.=20 > > > > >=20 > > > > > It seems to get stuck on grub after selecting the ipfire version it= doesnt boot further.=20 > > > >=20 > > > > Do you have any output from the bootloader/kernel?=20 > > > >=20 > > > > > I suspect that the bootscripts are designed for a specific arm boar= d as every board will have different addr for kernel load.=20 > > > >=20 > > > > No, we only support a generic way to boot, because it is simply not f= easible for us to provide hundreds of different images for all ARM boards out= there.=20 > > > >=20 > > > > > Where can I find the source code for the boot script package?=20 > > > >=20 > > > > https://git.ipfire.org/?p=3Dipfire-2.x.git;a=3Dblob;f=3Dlfs/grub;h=3D= 811c2f745e267e5ff6c246b66bc5f2196e12b780;hb=3DHEAD=20 > > > >=20 > > > > This is how we install GRUB on x86 and ARM64.=20 > > > >=20 > > > > Best,=20 > > > > -Michael=20 > > > >=20 > > > > >=20 > > > > > Thank you.=20 > > > > >=20 > > > > > _______________________________________________=20 > > > > > SIG-ARM mailing list=20 > > > > > SIG-ARM(a)lists.ipfire.org=20 > > > > > https://lists.ipfire.org/mailman/listinfo/sig-arm=20 > > > >=20 > > > >=20 > > >=20 > > >=20 > >=20 > >=20 >=20 >=20 --===============6416451524368796194==--