Mailinglist Archive: opensuse-arm (69 mails)
| < Previous | Next > |
Re: [opensuse-arm] efika questions
- From: Alexander Graf <agraf@xxxxxxx>
- Date: Wed, 09 Nov 2011 12:48:29 +0100
- Message-id: <4EBA688D.7050506@suse.de>
On 11/09/2011 12:26 PM, Adrian Schröter wrote:
We could also build an image that has to be "magically booted by someone else". That way we could leave out all the bootloader config and leave that up to the system's u-boot to do.
Then it should be fairly simple to create an image using kiwi. Don't hold your hopes up to see this working with qemu-linux-user though :).
Alex
--
To unsubscribe, e-mail: opensuse-arm+unsubscribe@xxxxxxxxxxxx
To contact the owner, e-mail: opensuse-arm+owner@xxxxxxxxxxxx
Am Mittwoch, 9. November 2011, 10:10:35 schrieb Joop Boonen:
On Tue, November 8, 2011 3:23 pm, Alexander Graf wrote:I had no time for it so far, I need a kernel-default package first. Hopefully
On 11/08/2011 02:31 PM, Peter Czanik wrote:Adrian, what is the status of the kiwi build?
Hello,Yes, thanks a lot for that!
I did not have Internet access for more than a week, and lost a bit
track, what is going on with the openSUSE ARM port. What I see is very
good news: over 3000 packages build already (
https://build.opensuse.org/project/show?project=openSUSE%3AFactory%3AA
RM
). As I have an EFIKA MX and helped to get some EFIKAs for developers,
my questions relate to it:Yes, we're using the common ground here. However, our triplet is
- what triplet is used to compile hardfloat binaries? In the archives
I
found:
"Currently we're building with -march=armv7-a -mfloat-abi=hard
-mfpu=vfp3-d16 -mthumb." Is it still the case? (I was asked by Debian
ARM HF project lead last week...)
"gnueabi" instead of "gnueabihf" at the last position because a lot of
parts in our toolchain break with gnueabihf and we haven't found a good
reason to not use it.
- how are the EFIKAs used?Currently the two smarttop ones are building the same repo internally
using chroot (we can't use chroot in publicly available nodes :(
security prevails) to basically give us a good overview on which
packages are broken because of qemu and which ones are actual package
bugs.
As far as the smarbooks go, one of them accompanied me to LinuxCon / ELC
in Prague and got demoed to quite a bunch of people showing openSUSE
running on ARM :).
- I have openSUSE running in a chroot on my smartbook, thanks toThe last state I knew (just flew back in yesterday - was on the road for
http://michal.hrusecky.net/2011/10/opensuse-arm-chroot-less-then-alpha
/
Is there already an image which could be booted directly? Or
instructions how to install it natively on the EFIKA?
the past 3 weeks) was that Adrian was looking at getting kiwi to work
with ARM. At that point we could just build images :).
the current build will succeed.
If someone wants to help, could someone package u-boot (the arm boot loader) ?
I suppose it will be a pre-requirement for the kiwi support.
We could also build an image that has to be "magically booted by someone else". That way we could leave out all the bootloader config and leave that up to the system's u-boot to do.
Then it should be fairly simple to create an image using kiwi. Don't hold your hopes up to see this working with qemu-linux-user though :).
Alex
--
To unsubscribe, e-mail: opensuse-arm+unsubscribe@xxxxxxxxxxxx
To contact the owner, e-mail: opensuse-arm+owner@xxxxxxxxxxxx
| < Previous | Next > |