[opensuse-arm] AArch64
Hi, I would like to make a wiki page about AArch64 (armv8) to list all things we must do for AArch64 in openSUSE. A page name like openSUSE:AArch64 looks good to me. Any objection? I have already some informations about AArch64 build but nothing on what is needed to get things in openSUSE (understand in OBS). I mean, what is needed to be able to start building AArch64 packages? I guess we must have a minimal rootfs with some tools? Or maybe just cross-compile? I already tested my own rootfs (built with the buildroot tool). I used : * a bootimg: http://releases.linaro.org/12.12/openembedded/aarch64/img-foundation.axf * u-boot: http://fedorapeople.org/~ahs3/u-boot.bin * Foundation_v8 (sort of qemu but seems to not be redistribuable) * A custom rootfs (I built using buildroot. See: buildroot.net) I built my own image with fdisk and files listed above and got it running: Foundation_v8 --image img-foundation.axf --block-device ./tmp/rootfs.img --network=nat So, what would be the next step? Regards, Guillaume -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
On Mon, Jan 14, 2013 at 04:50:25PM +0100, Guillaume Gardet wrote:
Hi,
I would like to make a wiki page about AArch64 (armv8) to list all things we must do for AArch64 in openSUSE.
A page name like openSUSE:AArch64 looks good to me. Any objection?
I have already some informations about AArch64 build but nothing on what is needed to get things in openSUSE (understand in OBS). I mean, what is needed to be able to start building AArch64 packages?
I guess we must have a minimal rootfs with some tools? Or maybe just cross-compile?
I already tested my own rootfs (built with the buildroot tool).
I used : * a bootimg: http://releases.linaro.org/12.12/openembedded/aarch64/img-foundation.axf * u-boot: http://fedorapeople.org/~ahs3/u-boot.bin * Foundation_v8 (sort of qemu but seems to not be redistribuable) * A custom rootfs (I built using buildroot. See: buildroot.net)
Hi Guillaume, I'm surprised that you've used u-boot here - the normal Foundation Model and kernel from Linaro don't (currently) have any boot loaders, so you're expected to use the boot wrapper instead. Are you sure you actually used u-boot? In the longer term, AArch64 is expected to use UEFI for boot. Cheers, -- Steve McIntyre steve.mcintyre@linaro.org http://www.linaro.org/ Linaro.org | Open source software for ARM SoCs -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
Le 14/01/2013 17:06, Steve McIntyre a écrit :
On Mon, Jan 14, 2013 at 04:50:25PM +0100, Guillaume Gardet wrote:
Hi,
I would like to make a wiki page about AArch64 (armv8) to list all things we must do for AArch64 in openSUSE.
A page name like openSUSE:AArch64 looks good to me. Any objection?
I have already some informations about AArch64 build but nothing on what is needed to get things in openSUSE (understand in OBS). I mean, what is needed to be able to start building AArch64 packages?
I guess we must have a minimal rootfs with some tools? Or maybe just cross-compile?
I already tested my own rootfs (built with the buildroot tool).
I used : * a bootimg: http://releases.linaro.org/12.12/openembedded/aarch64/img-foundation.axf * u-boot: http://fedorapeople.org/~ahs3/u-boot.bin * Foundation_v8 (sort of qemu but seems to not be redistribuable) * A custom rootfs (I built using buildroot. See: buildroot.net) Hi Guillaume,
I'm surprised that you've used u-boot here - the normal Foundation Model and kernel from Linaro don't (currently) have any boot loaders, so you're expected to use the boot wrapper instead. Are you sure you actually used u-boot?
At least I copied u-boot on the first partition of my img file. But bootimg (axf file) was used "as is" (no rebuild) and it seems to have kernel and kernel cmdline inside. So, my first FAT partition seems useless. (I used some infos from fedora project and others which seems wrong or outdated.)
In the longer term, AArch64 is expected to use UEFI for boot.
Thanks for info. Guillaume
Cheers,
-- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
First usefull infos are here: https://en.opensuse.org/openSUSE:AArch64 Regards, Guillaume Le 14/01/2013 16:50, Guillaume Gardet a écrit :
Hi,
I would like to make a wiki page about AArch64 (armv8) to list all things we must do for AArch64 in openSUSE.
A page name like openSUSE:AArch64 looks good to me. Any objection?
I have already some informations about AArch64 build but nothing on what is needed to get things in openSUSE (understand in OBS). I mean, what is needed to be able to start building AArch64 packages?
I guess we must have a minimal rootfs with some tools? Or maybe just cross-compile?
I already tested my own rootfs (built with the buildroot tool).
I used : * a bootimg: http://releases.linaro.org/12.12/openembedded/aarch64/img-foundation.axf * u-boot: http://fedorapeople.org/~ahs3/u-boot.bin * Foundation_v8 (sort of qemu but seems to not be redistribuable) * A custom rootfs (I built using buildroot. See: buildroot.net)
I built my own image with fdisk and files listed above and got it running: Foundation_v8 --image img-foundation.axf --block-device ./tmp/rootfs.img --network=nat
So, what would be the next step?
Regards,
Guillaume
-- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
Hi, I think it would be great to have a devel:ARM:AArch64 project (or another name) where we could store all our patches for AArch64. What do you think about it? Regards, Guillaume Le 15/01/2013 10:46, Guillaume Gardet a écrit :
First usefull infos are here:
https://en.opensuse.org/openSUSE:AArch64
Regards,
Guillaume
Le 14/01/2013 16:50, Guillaume Gardet a écrit :
Hi,
I would like to make a wiki page about AArch64 (armv8) to list all things we must do for AArch64 in openSUSE.
A page name like openSUSE:AArch64 looks good to me. Any objection?
I have already some informations about AArch64 build but nothing on what is needed to get things in openSUSE (understand in OBS). I mean, what is needed to be able to start building AArch64 packages?
I guess we must have a minimal rootfs with some tools? Or maybe just cross-compile?
I already tested my own rootfs (built with the buildroot tool).
I used : * a bootimg: http://releases.linaro.org/12.12/openembedded/aarch64/img-foundation.axf * u-boot: http://fedorapeople.org/~ahs3/u-boot.bin * Foundation_v8 (sort of qemu but seems to not be redistribuable) * A custom rootfs (I built using buildroot. See: buildroot.net)
I built my own image with fdisk and files listed above and got it running: Foundation_v8 --image img-foundation.axf --block-device ./tmp/rootfs.img --network=nat
So, what would be the next step?
Regards,
Guillaume
-- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
2013/1/28 Guillaume Gardet
I think it would be great to have a devel:ARM:AArch64 project (or another name) where we could store all our patches for AArch64. What do you think about it?
Hi, great idea. I've created devel:ARM:AArch64:Factory and added you as maintainer there. Feel free to keep submitting stuff there. Thanks, Dirk -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
Am Montag, 28. Januar 2013, 13:52:26 schrieb Guillaume Gardet:
Hi,
I think it would be great to have a devel:ARM:AArch64 project (or another name) where we could store all our patches for AArch64. What do you think about it?
Yes, but lets not do the mistake to store them there to long. They should get submitted to standard factory as soon as possible (maybe just ensuring that they harm not other architectures :)
Regards,
Guillaume
Le 15/01/2013 10:46, Guillaume Gardet a écrit :
First usefull infos are here:
https://en.opensuse.org/openSUSE:AArch64
Regards,
Guillaume
Le 14/01/2013 16:50, Guillaume Gardet a écrit :
Hi,
I would like to make a wiki page about AArch64 (armv8) to list all things we must do for AArch64 in openSUSE.
A page name like openSUSE:AArch64 looks good to me. Any objection?
I have already some informations about AArch64 build but nothing on what is needed to get things in openSUSE (understand in OBS). I mean, what is needed to be able to start building AArch64 packages?
I guess we must have a minimal rootfs with some tools? Or maybe just cross-compile?
I already tested my own rootfs (built with the buildroot tool).
I used : * a bootimg: http://releases.linaro.org/12.12/openembedded/aarch64/img-foundation.axf * u-boot: http://fedorapeople.org/~ahs3/u-boot.bin * Foundation_v8 (sort of qemu but seems to not be redistribuable) * A custom rootfs (I built using buildroot. See: buildroot.net)
I built my own image with fdisk and files listed above and got it running: Foundation_v8 --image img-foundation.axf --block-device ./tmp/rootfs.img --network=nat
So, what would be the next step?
Regards,
Guillaume
-- Adrian Schroeter SUSE Linux Products GmbH email: adrian@suse.de -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
Le 28/01/2013 14:36, Adrian Schröter a écrit :
Am Montag, 28. Januar 2013, 13:52:26 schrieb Guillaume Gardet:
Hi,
I think it would be great to have a devel:ARM:AArch64 project (or another name) where we could store all our patches for AArch64. What do you think about it? Yes, but lets not do the mistake to store them there to long. They should get submitted to standard factory as soon as possible (maybe just ensuring that they harm not other architectures :)
Ok. What would be the policy? For example, I can build the "rpm" package without selinux support since it is not yet available. Is it ok to add patches to Factory to disable selinux for aarch64? Then, "autoreconf -fi" fails with an obscure reason. So, I workaround it with "autoreconf -fi || autoconf -fi" for aarch64. I am not sure Factory will accept this kind of workaround. Regards, Guillaume
Regards,
Guillaume
Le 15/01/2013 10:46, Guillaume Gardet a écrit :
First usefull infos are here:
https://en.opensuse.org/openSUSE:AArch64
Regards,
Guillaume
Le 14/01/2013 16:50, Guillaume Gardet a écrit :
Hi,
I would like to make a wiki page about AArch64 (armv8) to list all things we must do for AArch64 in openSUSE.
A page name like openSUSE:AArch64 looks good to me. Any objection?
I have already some informations about AArch64 build but nothing on what is needed to get things in openSUSE (understand in OBS). I mean, what is needed to be able to start building AArch64 packages?
I guess we must have a minimal rootfs with some tools? Or maybe just cross-compile?
I already tested my own rootfs (built with the buildroot tool).
I used : * a bootimg: http://releases.linaro.org/12.12/openembedded/aarch64/img-foundation.axf * u-boot: http://fedorapeople.org/~ahs3/u-boot.bin * Foundation_v8 (sort of qemu but seems to not be redistribuable) * A custom rootfs (I built using buildroot. See: buildroot.net)
I built my own image with fdisk and files listed above and got it running: Foundation_v8 --image img-foundation.axf --block-device ./tmp/rootfs.img --network=nat
So, what would be the next step?
Regards,
Guillaume
-- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
2013/1/28 Guillaume Gardet
Ok. What would be the policy?
Hi, the policy would be "try to keep changes in a mergeable state, and merge as soon as possible". I don't think there is anything wrong with having a collaborative area where we can exchange AArch64 patches. I prefer an existing Aarch64 port over a non-existing but perfectly-clean-Factory sources at any time.
with "autoreconf -fi || autoconf -fi" for aarch64. I am not sure Factory will accept this kind of workaround.
Then we'll submit it to factory once we understood the error and either fixed it more elegantly or can explain why there is no better solution. For now, there is imho nothing wrong with having the chances available. Thanks, Dirk -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
Am Montag, 28. Januar 2013, 14:42:49 schrieb Guillaume Gardet:
Le 28/01/2013 14:36, Adrian Schröter a écrit :
Am Montag, 28. Januar 2013, 13:52:26 schrieb Guillaume Gardet:
Hi,
I think it would be great to have a devel:ARM:AArch64 project (or another name) where we could store all our patches for AArch64. What do you think about it? Yes, but lets not do the mistake to store them there to long. They should get submitted to standard factory as soon as possible (maybe just ensuring that they harm not other architectures :)
Ok. What would be the policy? For example, I can build the "rpm" package without selinux support since it is not yet available. Is it ok to add patches to Factory to disable selinux for aarch64?
Yes, would be fine. However, for this specific case, disabling core features may turn into a nightmare when one has to adapt lots of packages afterwards ... But if we want to go that way, better doing it in factory and reverting it also there later. The former ARM ports failed mainly because exactly this merging work was not done.
Then, "autoreconf -fi" fails with an obscure reason. So, I workaround it with "autoreconf -fi || autoconf -fi" for aarch64. I am not sure Factory will accept this kind of workaround.
Hm, I would prefer to understand if better ... but in the end, the question is if the individual package owner does accept it or not ;) bye adrian
Regards,
Guillaume
Regards,
Guillaume
Le 15/01/2013 10:46, Guillaume Gardet a écrit :
First usefull infos are here:
https://en.opensuse.org/openSUSE:AArch64
Regards,
Guillaume
Le 14/01/2013 16:50, Guillaume Gardet a écrit :
Hi,
I would like to make a wiki page about AArch64 (armv8) to list all things we must do for AArch64 in openSUSE.
A page name like openSUSE:AArch64 looks good to me. Any objection?
I have already some informations about AArch64 build but nothing on what is needed to get things in openSUSE (understand in OBS). I mean, what is needed to be able to start building AArch64 packages?
I guess we must have a minimal rootfs with some tools? Or maybe just cross-compile?
I already tested my own rootfs (built with the buildroot tool).
I used : * a bootimg: http://releases.linaro.org/12.12/openembedded/aarch64/img-foundation.axf * u-boot: http://fedorapeople.org/~ahs3/u-boot.bin * Foundation_v8 (sort of qemu but seems to not be redistribuable) * A custom rootfs (I built using buildroot. See: buildroot.net)
I built my own image with fdisk and files listed above and got it running: Foundation_v8 --image img-foundation.axf --block-device ./tmp/rootfs.img --network=nat
So, what would be the next step?
Regards,
Guillaume
-- Adrian Schroeter SUSE Linux Products GmbH email: adrian@suse.de -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
On 01/28/2013 03:08 PM, Adrian Schröter wrote:
Am Montag, 28. Januar 2013, 14:42:49 schrieb Guillaume Gardet:
Le 28/01/2013 14:36, Adrian Schröter a écrit :
Am Montag, 28. Januar 2013, 13:52:26 schrieb Guillaume Gardet:
Hi,
I think it would be great to have a devel:ARM:AArch64 project (or another name) where we could store all our patches for AArch64. What do you think about it? Yes, but lets not do the mistake to store them there to long. They should get submitted to standard factory as soon as possible (maybe just ensuring that they harm not other architectures :) Ok. What would be the policy? For example, I can build the "rpm" package without selinux support since it is not yet available. Is it ok to add patches to Factory to disable selinux for aarch64? Yes, would be fine. However, for this specific case, disabling core features may turn into a nightmare when one has to adapt lots of packages afterwards ...
But if we want to go that way, better doing it in factory and reverting it also there later. The former ARM ports failed mainly because exactly this merging work was not done.
Then, "autoreconf -fi" fails with an obscure reason. So, I workaround it with "autoreconf -fi || autoconf -fi" for aarch64. I am not sure Factory will accept this kind of workaround. Hm, I would prefer to understand if better ... but in the end, the question is if the individual package owner does accept it or not ;)
I'd be inclined to say that I'd really start worrying about Factory merging as soon as we actually have a base system we can build with :). Alex -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
participants (5)
-
Adrian Schröter -
Alexander Graf -
Dirk Müller -
Guillaume Gardet -
Steve McIntyre