On Wed, November 9, 2011 2:21 pm, Adrian Schröter wrote:
Am Mittwoch, 9. November 2011, 14:01:30 schrieb Joop Boonen:
On Wed, November 9, 2011 12:26 pm, Adrian Schröter wrote:
Am Mittwoch, 9. November 2011, 10:10:35 schrieb Joop Boonen:
On Tue, November 8, 2011 3:23 pm, Alexander Graf wrote:
On 11/08/2011 02:31 PM, Peter Czanik wrote:
Hello,
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%3AFacto ry%3AA RM ). As I have an EFIKA MX and helped to get some EFIKAs for
developers,
Yes, thanks a lot for that!
my questions relate to it:
- 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...)
Yes, we're using the common ground here. However, our triplet is "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 to 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 last state I knew (just flew back in yesterday - was on the road
for
the past 3 weeks) was that Adrian was looking at getting kiwi to work with ARM. At that point we could just build images :).
Adrian, what is the status of the kiwi build?
I had no time for it so far, I need a kernel-default package first.
Ok, then I'll start working on kiwi, this coming weekend. If I get something working how can I submit the diffs, to be reviewed?
best is to the kiwi developer mailing list. Or make a git pull request on github.com
I didn't get to this was working on the kernel. Hopefully I can fix this issues with this one soon. I have an usb issue, that I need to fix. ( home:worldcitizen:armv7l kernel-omap4panda ) After that I'll start working on kiwi.
Hopefully 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.
U-boot has been build for the pandaboard. I used the meego version as a base. It still needs a bit of tuning. The package can be found here: home:worldcitizen:armv7l u-boot-omap4panda
please look for a devel project and submit to factory.
I've submitted both x-loader-omap4panda and u-boot-omap4panda to Base:System . (request id 91227 and request id 91228) I've tested both of them on my PandaBoard.
-- 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