- openSUSE ARM

[opensuse-arm] dietlibc status
by Tim Serong 06 Oct '11

06 Oct '11

Hi All, I spent some time with dietlibc on the weekend. Here's the story: * The attached patch is necessary to fix the immediate build error (doesn't recognize armv7a as a known architecture). * If you apply this patch, later, the build fails with: gcc -D__dietlibc__ -I. -isystem include -fmessage-length=0 -march=armv7-a -mtune=cortex-a9 -mlittle-endian -mfpu=vfpv3-d16 -mfloat-abi=hard -mthumb -mabi=aapcs-linux -Os -Wall -fstack-protector -g -fno-strict-aliasing -c arm/__longjmp.S -o bin-arm/__longjmp.o arm/__longjmp.S: Assembler messages: arm/__longjmp.S:9: Error: selected processor does not support ARM mode `lfm f4,4,[ip],#48' Apparently, FPU vfpv3-d16 doesn't include the lfm opcode (nor sfm, used in setjmp). I am unfortunately grossly unqualified to have an opinion on this, or to (re)implement a correct setjmp/longjmp. * I suspected an upgrade to dietlibc 0.32 may be good/useful (see changelog at http://www.fefe.de/dietlibc/changes-0.32.txt, it mentions some ARM fixes), but AFACIT even upgrading to 0.32 does not fix the above lfm/sfm opcode issue. * Unless other packages depend on it, I'm somewhat tempted to suggest dropping dietlibc if suitable fixes can't be located. The last upstream release was in 2009, and there's mention of it having "numerous unfixed bugs" on the busybox web site (http://busybox.net/FAQ.html#libc) Regards, Tim -- Tim Serong Senior Clustering Engineer SUSE tserong(a)suse.com

3 4

Re: [opensuse-arm] Can openSUSE:Factory:ARM please be published
by Joop Boonen 04 Oct '11

04 Oct '11

On Sun, October 2, 2011 5:28 pm, Dirk Müller wrote: > On Sunday 02 October 2011, Joop Boonen wrote: > >> Can openSUSE:Factory:ARM please be published? >> If it's not allowed to publish it on download.opensuse.org can it please be published like the powerpc packages? arm.opensuse.org? > > As I don't know why it was disabled, I've enabled publishing of > openSUSE:Factory:ARM now. It looks like there is an issue publishing armv7hl packages (http://download.opensuse.org/repositories/openSUSE:/Factory:/ARM/armv7hl/) Packages are in state: "State needs recalculations, former state was: The repository state is being calculated right now" > > Greetings, > Dirk Regards, Joop. -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-arm+help(a)opensuse.org

2 1

[opensuse-arm] Cleaning up architecture mess ...
by Adrian Schröter 04 Oct '11

04 Oct '11

Hi, this my plan to cleanup the current mess with the architectures for ARM: * drop armv7hl scheduler and run only armv7el (armv7l would make more sense but to stay compatible with former OBS releases). * change target to produce armv7l.rpm's. The build flags and used hardware floating point switches will remain to be active. * adapt rpm to accept the not existing armv7hl architecture packages to stay compatible with Fedora and MeeGo. Reason behind this is that we currently mix ABI compatibilities and hardware features in the machine string. armv7l hardware should always be able to execute hard float binaries. When the ABI is not compatible this should be expressed by package dependencies. Any comments on this ? thanks adrian -- Adrian Schroeter SUSE Linux Products GmbH email: adrian(a)suse.de

3 3

[opensuse-arm] xorg-x11-driver-video request to split-up
by Joop Boonen 03 Oct '11

03 Oct '11

Hi, Currently this package doesn't build for ARM as of broken code for the xgi driver. I wonder if it would be an idea to slit the package up into different rpm packages, for each driver one rpm package. Basically the same was MeeGo does. The advantage is that it'll safe space. What is important for ARM. I think that chance that an ARM system will be connected to a XGI card is next to nothing. So this driver doesn't need to be maintained for ARM, I think. What do you think about this? Regards, Joop. -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-arm+help(a)opensuse.org

1 0

[opensuse-arm] xorg-x11-driver-video request to split-up
by Joop Boonen 03 Oct '11

03 Oct '11

Hi, Currently this package doesn't build for ARM as of broken code for the xgi driver. I wonder if it would be an idea to slit the package up into different rpm packages, for each driver one rpm package. Basically the same was MeeGo does. The advantage is that it'll safe space. What is important for ARM. I think that chance that an ARM system will be connected to a XGI card is next to nothing. So this driver doesn't need to be maintained for ARM, I think. What do you think about this? Regards, Joop. -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-arm+help(a)opensuse.org

1 0

Re: [opensuse-arm] Can openSUSE:Factory:ARM please be published
by Joop Boonen 03 Oct '11

03 Oct '11

On Sun, October 2, 2011 5:28 pm, Dirk Müller wrote: > On Sunday 02 October 2011, Joop Boonen wrote: > >> Can openSUSE:Factory:ARM please be published? >> If it's not allowed to publish it on download.opensuse.org can it please >> be published like the powerpc packages? arm.opensuse.org? > > As I don't know why it was disabled, I've enabled publishing of > openSUSE:Factory:ARM now. It looks like there is an issue publishing armv7hl packages (http://download.opensuse.org/repositories/openSUSE:/Factory:/ARM/armv7hl/) Packages are in state: "State needs recalculations, former state was: The repository state is being calculated right now" > > Greetings, > Dirk Regards, Joop. -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-arm+help(a)opensuse.org

1 0

[opensuse-arm] Can openSUSE:Factory:ARM please be published
by Joop Boonen 02 Oct '11

02 Oct '11

All, Can openSUSE:Factory:ARM please be published? If it's not allowed to publish it on download.opensuse.org can it please be published like the powerpc packages? arm.opensuse.org? Regards, Joop. -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-arm+help(a)opensuse.org

3 2

[opensuse-arm] Growing some openSUSE ARMs
by Andrew Wafaa 01 Oct '11

01 Oct '11

Sorry for the cross posting, but I thought it worth the extra noise ;-) One of the things that came out of the recent Geeko Love-In for me was a new project to immerse myself in within openSUSE. Yeah I know, we have enough existing projects already so why create a new one? Simples! Believe it or not but openSUSE is behind the curve in a specific segment, and that segment has yet to explode to its full potential. That segment is ARM. No I'm not talking about your upper body appendages, but the architecture that powers most of your little devices (and some bigger ones too). Almost all smartphones, tablets and many other consumer devices are powered by ARM from one of the numerous licensees. Didn't openSUSE do something about this a while ago? Yes we did. Unfortunately the effort seems to have bitrotted somewhat, there were numerous reasons and I don't even prophesise to know the all either. As such I'm going to try and kickstart things, and see it through and hopefully see it grow. As I mentioned, this idea came up at the conference when I was talking to numerous people (I forget how it all started, but that doesn't really matter). There was an overwhelmingly positive view on the matter, and that for me was all that counts. Now let me be crystal clear here, *THIS WILL NOT BE A ONE MAN SHOW!!* I mentioned previously that my view is that we as a community are pretty lazy at times with getting our hands dirty. As such if you think things are going slow or not going in the direction you would like, don't moan. Get your hands dirty and help make a difference. The process will not be an easy one either, so don't expect a port to magically appear over night. If we're lucky we might be able to have a working port in 6 months. Maybe longer, maybe shorter; ultimately that lies with us as a community. Stage one has begun already thanks to Adrian Schroeter, Alex Graf and Dirk Mueller. Stage one comprises of getting the boot strap process to work. At a cursory level this means getting the packages required for setting up a build chroot environment and for building these packages on the target ARM architecture. This will possibly take a fair amount of time, and no I won't give any timelines for this - how long is a piece of string? openSUSE has a couple of advantages here, 1) we have the OBS which can cross build and if need be cross compile packages for numerous architectures (ARM included) so we are going to make a start with that; 2) SUSE are going to be doing another HackWeek (I think it is next week) which means Adrian, Alex, Dirk and anyone else that has knowledge, experience or interest can join in the fun and pain almost full time for a week - let's not kid ourselves here there is a high probability for lots of pain, but also fun ;-) Thing is HackWeek is not just for SUSE staff, it is also for the community. You can join in and spend some quality time on the project with those that know a whole heap of stuff, and learn from them and maybe even teach them something too. We are going to be targeting ARMv7 nothing older I'm afraid this means CORTEX-A8 and above (looking at A9 primarily and then the new A15 when it's available), it gets too messy otherwise and it is already messy enough.If you have knowledge and experience, please help out. If you don't take part you have no justification to complain - you've got to be in it to win it ;-) So I'm basically just giving you all a heads up on this effort, and will update you as regularly as possible (I'm hoping to do something weekly maybe). In the meantime, if you're interested join #opensuse-arm on Freenode and the opensuse-arm mailing list. *DO NOT HARRASS* for updates, if there is something to say it will be said. If you've got a question, ask and *WAIT* for an answer. If you want to help out but want to know how ask and *WAIT* for an answer. I will try and get something on the wiki soon, with a todo list etc. Thanks and here's to getting our Geeko some ARMs. Regards, Andy -- Andrew Wafaa IRC: FunkyPenguin GPG: 0x3A36312F -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-arm+help(a)opensuse.org

17 26

[opensuse-arm] Target ARM Hardware
by Andrew Wafaa 30 Sep '11

30 Sep '11

This is a hot topic, and one that seems to generate the most noise. I've had a discussion with several people about target hardware, and I've also looked at what our peers are doing and saying. At the same time I've been trying to see what options we have for getting some sponsorship for hardware. There were three devices in the running, all are classed as development boards - so no case or external prettyness (beauty comes from within anyway): TI PandaBoard [0] Samsung Origen [1] ST Ericsson Snowball [2] After discussing, the preferred nominee is the PandaBoard. Several factors led to this decision, it has an integrated wired network connection; is well supported by the incumbant distros; widely used within the wider ARM open source community; and it has Pandas (OK only in name but still!) So if you want to prep and get some hardware, then go for the PandaBoard (as soon as the Cortex A15 is released, we'll be looking at them). Yes, I know it's a developer board and not an end user product. Unfortunately there aren't actually that many end user products that you can sensibly use for development at the moment. Sure, there's the TrimSlice[3] the DreamPlug[4] and a few others, but after consulting someone that is far more knowledgable and aware of the wider landscape we went with their recommendations. Oh and things are moving pretty fast folk!! \o/ 0 = http://www.pandaboard.org/ 1 = http://www.origenboard.org/ 2 = http://www.igloocommunity.org/ 3 = http://trimslice.com/ 4 = http://www.globalscaletechnologies.com/t-dreamplugdetails.aspx -- Andrew Wafaa IRC: FunkyPenguin GPG: 0x3A36312F -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-arm+help(a)opensuse.org

2 1

[opensuse-arm] Marvell Dreamplug D2 available for purchase
by Bill Merriam 29 Sep '11

29 Sep '11

Here is Marvell's description of the processor: The Marvell ARMADA 510 is a high-performance, highly integrated, low-power system-on-chip (SoC) with an ARM v6/v7-compliant superscalar processor core, hardware graphics processing unit, video decoding acceleration hardware and a broad range of peripherals. Targeted for smartbooks, thin clients, mobile internet devices (MIDs) and tablet devices, this high-performance SoC answers the need for fast processing and a rich multimedia user experience, in a low-power design that offers quick Internet browsing, software compatibility, HD video, 3D graphics and high-speed connectivity. Marvell’s ARMADA 510 (88AP510) SoC gives developers a fully integrated design that provides end users with the portability and similar battery life experience of a smartphone, along with the multimedia, software and browser performance of a PC. The D2 is not a board, is a complete system with case, power supply etc. It lists for US$250 which seems reasonable. It comes with Ubuntu 10.04 installed. Everything is open source, including graphics. Marvell maintains the kernel patches but I think they are upstream. Here are some links: http://plugcomputer.org/development-kits/d2plug.html http://www.marvell.com/application-processors/armada-500/index.jsp https://www.globalscaletechnologies.com/t-d2plugdetails.aspx Anybody have any thoughts about using this as a target platform? Bill -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-arm+help(a)opensuse.org

1 0