SIG-ARM

sig-arm@lists.ipfire.org

49 discussions

build ipfire-2.x on odroid C4
by Marco Bauer 27 Apr '23

27 Apr '23

Hi, I try to build ipfire-2.x on odroid C4 OS: ubuntu 22.04 mini, odroid image, all updates done. No changes made in the sources, common workflow used, till yet. Unfortunatelly there is some trouble described here: https://community.ipfire.org/t/build-ipfire-aarch64-on-odriodc4/ Are there any hints to fix this? kind regards, Marco

2 1

Re: Understanding boot process.
by Michael Tremer 18 Dec '20

18 Dec '20

Hello Furkan, *please* copy the list. I can’t have a conversation in private only with you. This conversation should be shared with other and documented, too. > On 23 Nov 2020, at 11:42, Furkan Salman <tech(a)fkardame.com> wrote: > > Hey, > I don't understand by what you mean kernel that boots on arm? We have not ported the configuration and all the patches that we need, yet. > I will try to reuse your kernel5.9 pkg of x86 and try to build the same for arm boards as I have all the config needed. This is not a good idea, because the kernels are slightly different. > I have been compiling kernels for arm board since 5.0 and maintaining kernel support so I hope I can do the same for ipfire soon. The only thing I might miss is the additional config needed for ipfire which we will come to later once I get the kernel to boot work 5.9. Exactly, if you just need a kernel that compiles, that is not very difficult to achieve. But we have a custom configuration and we have some patches that make that kernel work better for us. Those need to be tested a lot before we can release them. > I will try to get it to boot and support you with ARM as I am aware arm is 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. That would be great. I personally do not have any ARM hardware that I use for development any more, but since there is interest in the community to support IPFire on as much hardware as possible, I would support this. > Thanks for replying. I will start looking into what I can do with my limited knowledge of ipfire source;) Please ask questions. Development is not a quick job. It requires planning, a lot of work and testing. It is not enough if a device just boots. It has to work. All of it. That includes networking, power management, LEDs, etc. And it needs to perform. There is no point to support hardware for the fun of it. If people cannot use this 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. Best, -Michael > > Will stay in touch with you here. > > Thanks. > > > > ---- On Mon, 23 Nov 2020 14:36:43 +0300 michael.tremer(a)ipfire.org wrote ---- > > Hello, > > Again, *please* copy the list. > > We currently do not have an ARM version of that kernel available. There is only a version for x86. > > As soon as we have a kernel that boots it will be announced on the development list. So, please watch this space :) > > -Michael > > > On 23 Nov 2020, at 11:34, Furkan Salman <tech(a)fkardame.com> wrote: > > > > I would love to be part of testing 5.9 as most of the boards are already supported there. > > > > NanopiR2s > > RockpiE > > RockpiE3 (RockPiE with extra Lan, total 3 lan) this is development board and not public yet. > > > > I have good understanding in Dts updates so it will be helpful for ipfire team. I don't mind supporting few devices myself. > > > > I will dedicate one of my amlogic device for building ipfire images only. > > > > Please guide me on how I can build images with kernel 5.9 as I have had build images with 4.9 only. > > > > Thanks > > > > > > > > ---- On Mon, 23 Nov 2020 14:31:06 +0300 michael.tremer(a)ipfire.org wrote ---- > > > > We currently have a version of kernel 5.9 that we are testing and we will target to move to 5.10 as soon as it comes out. > > > > I hope for a release early next year. > > > > Best, > > -Michael > > > > P.S. Please do not forget to copy the list. > > > > > On 23 Nov 2020, at 11:25, Furkan Salman <tech(a)fkardame.com> wrote: > > > > > > Hello Michael, > > > > > > Yes I see that EFI boot is already provied in aarch64 image. > > > I am flashing rockpie and using rock64 dtb or I will try it with rockpie itself this time and report back to you by tonight or tomorrow max. > > > > > > When do you plan to move to kernel 5.4 ? > > > > > > > > > > > > > > > ---- On Mon, 23 Nov 2020 14:21:43 +0300 michael.tremer(a)ipfire.org wrote ---- > > > > > > Hello Furkan, > > > > > > Thanks for signing up and posting :) > > > > > > I suppose we are talking about ARM64: > > > > > > We currently only support systems that use EFI. If there is an EFI BIOS, it will launch GRUB and hopefully return all required configuration to the kernel. > > > > > > > On 22 Nov 2020, at 15:00, Furkan Salman <tech(a)fkardame.com> wrote: > > > > > > > > Hello IPFire Team, > > > > > > > > I would like to understand how do you get the grub to work on the arm images. > > > > > > > > I have RockPiE which is not supported by your project but I am willing to add support it by myself. > > > > > > > > Afaik I should be able to get it to boot with other Rk3328 board dtb i have its mainline uboot. > > > > > > > > It seems to get stuck on grub after selecting the ipfire version it doesnt boot further. > > > > > > Do you have any output from the bootloader/kernel? > > > > > > > I suspect that the bootscripts are designed for a specific arm board as every board will have different addr for kernel load. > > > > > > No, we only support a generic way to boot, because it is simply not feasible for us to provide hundreds of different images for all ARM boards out there. > > > > > > > Where can I find the source code for the boot script package? > > > > > > https://git.ipfire.org/?p=ipfire-2.x.git;a=blob;f=lfs/grub;h=811c2f745e267e… > > > > > > This is how we install GRUB on x86 and ARM64. > > > > > > Best, > > > -Michael > > > > > > > > > > > Thank you. > > > > > > > > _______________________________________________ > > > > SIG-ARM mailing list > > > > SIG-ARM(a)lists.ipfire.org > > > > https://lists.ipfire.org/mailman/listinfo/sig-arm > > > > > > > > > > > >

2 6

Re: Understanding boot process.
by Michael Tremer 23 Nov '20

23 Nov '20

Hello, Again, *please* copy the list. We currently do not have an ARM version of that kernel available. There is only a version for x86. As soon as we have a kernel that boots it will be announced on the development list. So, please watch this space :) -Michael > On 23 Nov 2020, at 11:34, Furkan Salman <tech(a)fkardame.com> wrote: > > I would love to be part of testing 5.9 as most of the boards are already supported there. > > NanopiR2s > RockpiE > RockpiE3 (RockPiE with extra Lan, total 3 lan) this is development board and not public yet. > > I have good understanding in Dts updates so it will be helpful for ipfire team. I don't mind supporting few devices myself. > > I will dedicate one of my amlogic device for building ipfire images only. > > Please guide me on how I can build images with kernel 5.9 as I have had build images with 4.9 only. > > Thanks > > > > ---- On Mon, 23 Nov 2020 14:31:06 +0300 michael.tremer(a)ipfire.org wrote ---- > > We currently have a version of kernel 5.9 that we are testing and we will target to move to 5.10 as soon as it comes out. > > I hope for a release early next year. > > Best, > -Michael > > P.S. Please do not forget to copy the list. > > > On 23 Nov 2020, at 11:25, Furkan Salman <tech(a)fkardame.com> wrote: > > > > Hello Michael, > > > > Yes I see that EFI boot is already provied in aarch64 image. > > I am flashing rockpie and using rock64 dtb or I will try it with rockpie itself this time and report back to you by tonight or tomorrow max. > > > > When do you plan to move to kernel 5.4 ? > > > > > > > > > > ---- On Mon, 23 Nov 2020 14:21:43 +0300 michael.tremer(a)ipfire.org wrote ---- > > > > Hello Furkan, > > > > Thanks for signing up and posting :) > > > > I suppose we are talking about ARM64: > > > > We currently only support systems that use EFI. If there is an EFI BIOS, it will launch GRUB and hopefully return all required configuration to the kernel. > > > > > On 22 Nov 2020, at 15:00, Furkan Salman <tech(a)fkardame.com> wrote: > > > > > > Hello IPFire Team, > > > > > > I would like to understand how do you get the grub to work on the arm images. > > > > > > I have RockPiE which is not supported by your project but I am willing to add support it by myself. > > > > > > Afaik I should be able to get it to boot with other Rk3328 board dtb i have its mainline uboot. > > > > > > It seems to get stuck on grub after selecting the ipfire version it doesnt boot further. > > > > Do you have any output from the bootloader/kernel? > > > > > I suspect that the bootscripts are designed for a specific arm board as every board will have different addr for kernel load. > > > > No, we only support a generic way to boot, because it is simply not feasible for us to provide hundreds of different images for all ARM boards out there. > > > > > Where can I find the source code for the boot script package? > > > > https://git.ipfire.org/?p=ipfire-2.x.git;a=blob;f=lfs/grub;h=811c2f745e267e… > > > > This is how we install GRUB on x86 and ARM64. > > > > Best, > > -Michael > > > > > > > > Thank you. > > > > > > _______________________________________________ > > > SIG-ARM mailing list > > > SIG-ARM(a)lists.ipfire.org > > > https://lists.ipfire.org/mailman/listinfo/sig-arm > > > > > >

1 0

Re: Understanding boot process.
by Michael Tremer 23 Nov '20

23 Nov '20

We currently have a version of kernel 5.9 that we are testing and we will target to move to 5.10 as soon as it comes out. I hope for a release early next year. Best, -Michael P.S. Please do not forget to copy the list. > On 23 Nov 2020, at 11:25, Furkan Salman <tech(a)fkardame.com> wrote: > > Hello Michael, > > Yes I see that EFI boot is already provied in aarch64 image. > I am flashing rockpie and using rock64 dtb or I will try it with rockpie itself this time and report back to you by tonight or tomorrow max. > > When do you plan to move to kernel 5.4 ? > > > > > ---- On Mon, 23 Nov 2020 14:21:43 +0300 michael.tremer(a)ipfire.org wrote ---- > > Hello Furkan, > > Thanks for signing up and posting :) > > I suppose we are talking about ARM64: > > We currently only support systems that use EFI. If there is an EFI BIOS, it will launch GRUB and hopefully return all required configuration to the kernel. > > > On 22 Nov 2020, at 15:00, Furkan Salman <tech(a)fkardame.com> wrote: > > > > Hello IPFire Team, > > > > I would like to understand how do you get the grub to work on the arm images. > > > > I have RockPiE which is not supported by your project but I am willing to add support it by myself. > > > > Afaik I should be able to get it to boot with other Rk3328 board dtb i have its mainline uboot. > > > > It seems to get stuck on grub after selecting the ipfire version it doesnt boot further. > > Do you have any output from the bootloader/kernel? > > > I suspect that the bootscripts are designed for a specific arm board as every board will have different addr for kernel load. > > No, we only support a generic way to boot, because it is simply not feasible for us to provide hundreds of different images for all ARM boards out there. > > > Where can I find the source code for the boot script package? > > https://git.ipfire.org/?p=ipfire-2.x.git;a=blob;f=lfs/grub;h=811c2f745e267e… > > This is how we install GRUB on x86 and ARM64. > > Best, > -Michael > > > > > Thank you. > > > > _______________________________________________ > > SIG-ARM mailing list > > SIG-ARM(a)lists.ipfire.org > > https://lists.ipfire.org/mailman/listinfo/sig-arm > >

1 0

Understanding boot process.
by Furkan Salman 23 Nov '20

23 Nov '20

Hello IPFire Team, I would like to understand how do you get the grub to work on the arm images. I have RockPiE which is not supported by your project but I am willing to add support it by myself. Afaik I should be able to get it to boot with other Rk3328 board dtb i have its mainline uboot. It seems to get stuck on grub after selecting the ipfire version it doesnt boot further. I suspect that the bootscripts are designed for a specific arm board as every board will have different addr for kernel load. Where can I find the source code for the boot script package? Thank you.

2 1

Ipfire 3
by Sholom Young 20 Jul '19

20 Jul '19

Hello everyone I would like to compile ipfire for orange pi zero. I am not sure to use ipfire 2 or 3 since 2 is the current one but 3 is package based and I do not now if it is supported and also to setup a cluster of orange pi to compile or do it on a modern workstation (Xeon e5 dual)?

1 0

Re: SIG-ARM Digest, Vol 21, Issue 1
by Luís Mendes 15 Feb '19

15 Feb '19

Hi Michael, I've just created bug report 12000 in Bugzilla, as per your request. Bug 12000 - ClearFog PCIe not working with v2.21-core126 Regards, Luís Mendes On Fri, Feb 15, 2019 at 12:00 PM <sig-arm-request(a)lists.ipfire.org> wrote: > > Send SIG-ARM mailing list submissions to > sig-arm(a)lists.ipfire.org > > To subscribe or unsubscribe via the World Wide Web, visit > https://lists.ipfire.org/mailman/listinfo/sig-arm > or, via email, send a message with subject or body 'help' to > sig-arm-request(a)lists.ipfire.org > > You can reach the person managing the list at > sig-arm-owner(a)lists.ipfire.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of SIG-ARM digest..." > > > Today's Topics: > > 1. ClearFog PCIe not working with v2.21-core126 (Lu?s Mendes) > 2. Re: ClearFog PCIe not working with v2.21-core126 (Michael Tremer) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Thu, 14 Feb 2019 19:53:46 +0000 > From: Lu?s Mendes <luis.p.mendes(a)gmail.com> > To: sig-arm(a)lists.ipfire.org > Subject: ClearFog PCIe not working with v2.21-core126 > Message-ID: > <CAEzXK1r3qLzCQKvg3Oe4mrpjbFAJH7wzvUmow+usMqvfsDgEcA(a)mail.gmail.com> > Content-Type: text/plain; charset="UTF-8" > > Hi all, > > I noticed that the ipfire kernel configuration doesn't include the > driver for I2C GPIO expander chip PCA9655 which is a required > dependency for the PCIe controller. Since the PCIe card reset and > clock request signals are provided by this expander chip, without such > driver, Linux simply ignores the entire PCIe subsystem. > > I've tested that adding the following options to the kernel > configuration fixes the issue: > CONFIG_GPIO_PCA953X=y > CONFIG_GPIO_PCA953X_IRQ=y > > Unfortunately IRQ option is only available is module is complied as > kernel built-in. IRQ is relevant, because the USB subsystem relies on > it to monitor USB port OverCurrent conditions, through the same GPIO > expander chip. > > Can these kernel configurations option be added to ipfire? It would be > relevant to allow for additional Ethernet ports. > > Regards, > Lu?s Mendes > > > ------------------------------ > > Message: 2 > Date: Fri, 15 Feb 2019 11:34:03 +0000 > From: Michael Tremer <michael.tremer(a)ipfire.org> > To: Lu?s Mendes <luis.p.mendes(a)gmail.com> > Cc: sig-arm(a)lists.ipfire.org > Subject: Re: ClearFog PCIe not working with v2.21-core126 > Message-ID: <1E2E2227-9F33-4C8A-A036-3890668673DE(a)ipfire.org> > Content-Type: text/plain; charset=utf-8 > > Hello Luis, > > Thank you for writing. > > I think there should be no problem to enable these options. > > Would you please open a ticket on our Bugzilla and I will assign it to the right person? > > Best, > -Michael > > > On 14 Feb 2019, at 19:53, Lu?s Mendes <luis.p.mendes(a)gmail.com> wrote: > > > > Hi all, > > > > I noticed that the ipfire kernel configuration doesn't include the > > driver for I2C GPIO expander chip PCA9655 which is a required > > dependency for the PCIe controller. Since the PCIe card reset and > > clock request signals are provided by this expander chip, without such > > driver, Linux simply ignores the entire PCIe subsystem. > > > > I've tested that adding the following options to the kernel > > configuration fixes the issue: > > CONFIG_GPIO_PCA953X=y > > CONFIG_GPIO_PCA953X_IRQ=y > > > > Unfortunately IRQ option is only available is module is complied as > > kernel built-in. IRQ is relevant, because the USB subsystem relies on > > it to monitor USB port OverCurrent conditions, through the same GPIO > > expander chip. > > > > Can these kernel configurations option be added to ipfire? It would be > > relevant to allow for additional Ethernet ports. > > > > Regards, > > Lu?s Mendes > > _______________________________________________ > > SIG-ARM mailing list > > SIG-ARM(a)lists.ipfire.org > > https://lists.ipfire.org/mailman/listinfo/sig-arm > > > > ------------------------------ > > Subject: Digest Footer > > _______________________________________________ > SIG-ARM mailing list > SIG-ARM(a)lists.ipfire.org > https://lists.ipfire.org/mailman/listinfo/sig-arm > > > ------------------------------ > > End of SIG-ARM Digest, Vol 21, Issue 1 > **************************************

1 0

ClearFog PCIe not working with v2.21-core126
by Luís Mendes 15 Feb '19

15 Feb '19

Hi all, I noticed that the ipfire kernel configuration doesn't include the driver for I2C GPIO expander chip PCA9655 which is a required dependency for the PCIe controller. Since the PCIe card reset and clock request signals are provided by this expander chip, without such driver, Linux simply ignores the entire PCIe subsystem. I've tested that adding the following options to the kernel configuration fixes the issue: CONFIG_GPIO_PCA953X=y CONFIG_GPIO_PCA953X_IRQ=y Unfortunately IRQ option is only available is module is complied as kernel built-in. IRQ is relevant, because the USB subsystem relies on it to monitor USB port OverCurrent conditions, through the same GPIO expander chip. Can these kernel configurations option be added to ipfire? It would be relevant to allow for additional Ethernet ports. Regards, Luís Mendes

2 1

Re: Rockchip RK3188 Radxa Rock
by Michael Tremer 22 Oct '14

22 Oct '14

Hey, looking forward to hearing from you when this is finished. Just wanted to remind you to keep your replies on list if a discussion started there... -Michael On Sun, 2014-10-05 at 01:01 +0200, Jochen Kauz wrote: > Hi Michael, > 1. as I written in another post, sharing is caring.. we have the > kernel sources and we build them from sources that we publish at our > github repo or our own gitlab, and we respect in every way the GPL and > the idea of FLOSS. > 2. I have looked at your kernel sources, and it is not a good idea to > have them merged, cause Rockchip is much too different in the specific > kernel sources we have. We have dtb at 3.10.37, but the source is far > away from your specific multiarch of IMX. > 3. thanks for the first hints to build it, but I think more of a fork > to implement the Rockchip kernel into IPFire at this point. So we > could have our own uboot and kernel, that's much easier in first step. > 4. another possibility.... what about mainline kernel? Could you merge > into mainline? > 5. Only as an information.. I have put my Crewmember Astralix into CC > cause we both are working on this item together. > > > Cheers > JochenKauz > > 2014-10-04 12:15 GMT+02:00 Michael Tremer <michael.tremer(a)ipfire.org>: > Hi Mario, > > On Thu, 2014-10-02 at 00:35 +0200, Jochen Kauz wrote: > > Hi list, > > I'm a member of CrewRKTablets and we make development of > custom > > kernels and roms for rockchip based devices, mostly tablets. > > But we have one toy that we find interesting to try a port > to, the > > Radxa Rock of Tom Cubie, a rk3188 based development board. > > It has a quadcore Cortex-A9 1.6GHz, 1-2GB RAM, WLAN, > ethernet, 2 Host > > USB 2.0, 1 USB OTG, serial and much more. > > We are running at this point Ubuntu 14.04 with 3.0.36 kernel > on it. > > > > > > Now Astralix and me want to get IPFire on it running. > > We have kernel sources for 3.0.36, 3.10.37 and uboot. > > It is always very much trouble to support new ARM SBCs. Best > of luck > with that! > > We require to build our kernels from source. Primarily because > this is > an Open Source project and secondly because we modify the > kernel a lot > with patches that harden it or add some features. > > > I have read a little bit in the history of this list.. and I > know we > > need grsecurity.. okay found patch sets for 3.0 and 3.10. > But I think > > there are more things, could you please give me some more > information > > what additional should be added to the kernel? > > As there is not much support from Rockchip in the kernel, I > assume that > your patchset will be quite huge. Hopefully it supports the > multiplatform approach and brings DTB files, etc. If so, you > can add > your patches to the kernel build instructions: > > http://cgit.ipfire.org/ipfire-2.x.git/tree/lfs/linux > > Update the configuration: > > http://cgit.ipfire.org/ipfire-2.x.git/tree/config/kernel/kernel.config.armv… > > And you are ready to go. > > The same rules as above apply for u-boot as well. You will > find that in > lfs/u-boot > > http://cgit.ipfire.org/ipfire-2.x.git/tree/lfs/u-boot > > If the patches are clean and do not break support for any of > the other > platforms, we will merge that and of course we will assist you > here if > you need us to. But I won't make any promises up front that we > can add > support for that hardware, because there are always many > things that > cause us trouble and requires a lot of work to maintain > support for that > hardware. > > Best, > -Michael > > > Best regards > > JochenKauz > > _______________________________________________ > > SIG-ARM mailing list > > SIG-ARM(a)lists.ipfire.org > > http://lists.ipfire.org/mailman/listinfo/sig-arm > >

2 4

Rockchip RK3188 Radxa Rock
by Jochen Kauz 04 Oct '14

04 Oct '14

Hi list, I'm a member of CrewRKTablets and we make development of custom kernels and roms for rockchip based devices, mostly tablets. But we have one toy that we find interesting to try a port to, the Radxa Rock of Tom Cubie, a rk3188 based development board. It has a quadcore Cortex-A9 1.6GHz, 1-2GB RAM, WLAN, ethernet, 2 Host USB 2.0, 1 USB OTG, serial and much more. We are running at this point Ubuntu 14.04 with 3.0.36 kernel on it. Now Astralix and me want to get IPFire on it running. We have kernel sources for 3.0.36, 3.10.37 and uboot. I have read a little bit in the history of this list.. and I know we need grsecurity.. okay found patch sets for 3.0 and 3.10. But I think there are more things, could you please give me some more information what additional should be added to the kernel? Best regards JochenKauz

2 1

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

SIG-ARM