October 2011 - openSUSE ARM - openSUSE Mailing Lists

[opensuse-arm] new qemu deployment in openSUSE:Factory:ARM and Base:build:arm
by Adrian Schröter 28 Oct '11

28 Oct '11

JFYI, we do use the qemu from openSUSE:Tools project in openSUSE:Factory:ARM via some aggregate&ExportFilter trick now. That means we don't need to deploy new worker images anymore for a qemu upgrade. The qemu version in openSUSE:Tools is currently not frozen, that means changes in Virtualization or openSUSE:Factory project will have direct effects. We can change this if needed. bye adrian PS: this is still considered a hack and not a clean solution, because it still requires identical architectures via the build hosts. A cleaner solution will be implemented later when working on worker capabilities. -- Adrian Schroeter SUSE Linux Products GmbH email: adrian(a)suse.de -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

1 0

[opensuse-arm] iproute2 package exists. :)
by Joop Boonen 28 Oct '11

28 Oct '11

Hi All, I see iproute2 has been build. I'm going to checkout how far I can get with JeOS, this weekend. A small remark. There is a unresolvable issue with iproute2 now. nothing provides perl = 5.14.1 needed by sgmltool If I check this out it looks like it;s not correct. OBS issue? https://build.opensuse.org/package/show?package=iproute2&project=openSUSE%3… https://build.opensuse.org/package/show?package=perl&project=openSUSE%3AFac… https://build.opensuse.org/package/show?package=sgmltool&project=openSUSE%3… Regards, Joop. -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

2 1

Re: [opensuse-ppc] Re: [opensuse-arm] [ml-admin] Merging the architecture lists to opensuse-arch
by Joop Boonen 27 Oct '11

27 Oct '11

On Thu, October 27, 2011 2:41 pm, Karl Eichwalder wrote: > Larry Stotler <larrystotler(a)gmail.com> writes: > >>> Meantime a merged list seems to me to be the wrong way to go: keep lists >>> that are active or might reasonably be expected to become so and kill the >>> others, effectively merging into -project and -factory. >> >> Is it really that big of a deal to leave it be and see what happens? Not really sure why it's so necessary to consider something dead when it may rise up again unexpectedly. > > Agreed. These arch lists are fine. Problematic are those general purpose lists such as -factory, -marketing, -project, etc. But as long as we do not create more of them, we can stand it. (I'm subscribe to -factory only, though.) When we are at it, is it an option to add opensuse-mips? > > -- > Karl Eichwalder SUSE LINUX Products GmbH R&D / Documentation MaxfeldstraÃe 5 > 90409 NÃ¼rnberg, Germany > GF: Jeff Hawn, Jennifer Guild, Felix ImendÃ¶rffer, HRB 16746 (AG NÃ¼rnberg) > -- > To unsubscribe, e-mail: opensuse-ppc+unsubscribe(a)opensuse.org > To contact the owner, e-mail: opensuse-ppc+owner(a)opensuse.org > > Regards, Joop. -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

1 0

Re: [opensuse-ppc] Re: [opensuse-arm] [ml-admin] Merging the architecture lists to opensuse-arch
by Joop Boonen 27 Oct '11

27 Oct '11

On Thu, October 27, 2011 2:41 pm, Karl Eichwalder wrote: > Larry Stotler <larrystotler(a)gmail.com> writes: > >>> Meantime a merged list seems to me to be the wrong way to go: keep >>> lists >>> that are active or might reasonably be expected to become so and kill >>> the >>> others, effectively merging into -project and -factory. >> >> Is it really that big of a deal to leave it be and see what happens? >> Not really sure why it's so necessary to consider something dead when >> it may rise up again unexpectedly. > > Agreed. These arch lists are fine. Problematic are those general > purpose lists such as -factory, -marketing, -project, etc. But as long > as we do not create more of them, we can stand it. (I'm subscribe to > -factory only, though.) When we are at it, is it an option to add opensuse-mips? > > -- > Karl Eichwalder SUSE LINUX Products GmbH > R&D / Documentation MaxfeldstraÃe 5 > 90409 NÃ¼rnberg, Germany > GF: Jeff Hawn, Jennifer Guild, Felix ImendÃ¶rffer, HRB 16746 (AG > NÃ¼rnberg) > -- > To unsubscribe, e-mail: opensuse-ppc+unsubscribe(a)opensuse.org > To contact the owner, e-mail: opensuse-ppc+owner(a)opensuse.org > > Regards, Joop. -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

1 0

Re: [opensuse-ppc] Re: [opensuse-arm] [ml-admin] Merging the architecture lists to opensuse-arch
by Joop Boonen 27 Oct '11

27 Oct '11

On Thu, October 27, 2011 9:44 am, Richard (MQ) wrote: > On 26/10/11 19:19, Joop Boonen wrote: >> On Wed, October 26, 2011 3:25 pm, Andreas Färber wrote: >>> Hi, >>> >>> Am 26.10.2011 15:04, schrieb Henne Vogelsang: >>>> On 26.10.2011 14:58, Adrian Schröter wrote: >>>>> Am Mittwoch, 26. Oktober 2011, 14:29:57 schrieb Henne Vogelsang: >>>>>> >>>>>> we are currently trying to reduce the amount of communication >>>>>> channels >>>>>> we provide. Because of this I would like to merge the 4 architecture >>>>>> lists into one list called opensuse-arch. >>>>>> >>>>>> If nobody objects until the 15th of November 12:00 UTC I will merge >>>>>> the >>>>>> lists. You don't have to do anything except rewriting your filter if >>>>>> you >>>>>> use one. >>>>> >>>>> I would definitive unsubscribe from such a list if the majority of >>>>> mails is >>>>> not interessting for me. >>>> >>>> The ppc, amd64 and ia64 lists didn't have any traffic in 2010 and >>>> 2011. >>>> I would like to have some point for people to go for non x86 >>>> architecture specific stuff. >>> >>> There was some recent activity to revive ppc openSUSE, so if arm stays >>> ppc should probably stay as well. >>> amd64 is mainstream now, so that's different I guess. >>> >> >> I agree. >> >> I think it's best to have separate mailing lists for different >> architectures. >> >> I think traffic wise it also safes bandwidth. Only people that are >> interested in a specific mailing list will get this mail and not >> traffic >> they don't want. >> >> The ppc mailing list will be very interesting again when the AmigaOne >> X1000 and Netbook will be released. >> http://en.wikipedia.org/wiki/AmigaOne_X1000 >> http://eab.abime.net/showthread.php?p=781936 >> If this ends up in an active mailing list where also ARM resides it's >> difficult to filter, I'm subscribed to both. > > If / when the AmigaOne X1000 arrives there will certainly be a new PPC > platform, but whether we can persuade the community to re-start the PPC > version of openSuSE Linux is another matter entirely. FWIW, the argument > for dropping it a few years back was that the usage had dwindled to > insignificant numbers (ISTR around 20 downloads / month) - I couldn't > really argue with that. > > My expectation is that there won't be another official PPC version at > all, though maybe we'll have enough momentum for an unofficial one - in > which case retention of this list will be vindicated. It all depends on > whether the machine is ever launched - time will tell. > > Meantime a merged list seems to me to be the wrong way to go: keep lists > that are active or might reasonably be expected to become so and kill > the others, effectively merging into -project and -factory. Why not be the distro that also invites people who want to try other distro's? If you look at other distro's they are more inviting for people who want to try other distro's. http://lists.debian.org/ports.html https://admin.fedoraproject.org/mailman/listinfo Why not even add a opensuse-mips mailing-list for people in for instance China who would like to work on a Loongson/Godson port. I think this will pull more hardware gurus to our distro. I think our current limiting approach set us behind other distro's on supported archs. This is something we see now in the arm port. This might happen again when another important architecture would appear. I think we should get rid of the opensuse-amd86 mailing-list as it's x86. One other thing I also don't understand is. WE currently build all ppc packages as Factory. Why don't we also build a the iso's for the current version, with the extra label unstable (so 12.1-unstable-ppc). Now a newbie that is interested in openSuSE on his old Mac won't be able to install openSuSE ppc due to the lack of a DVD. And therefor will move on to another distro. > > -- > Cheers > Richard (MQ) > -- > To unsubscribe, e-mail: opensuse-ppc+unsubscribe(a)opensuse.org > To contact the owner, e-mail: opensuse-ppc+owner(a)opensuse.org > > Regards, Joop. -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

1 0

[opensuse-arm] rootfs
by Bernhard Schuster 27 Oct '11

27 Oct '11

Can anybody point me to a (alpha,beta) rootfs, howto create such or what to fix in order to move forward towards it? I already read all openSuSE and ARM related pages but I did not stumble upon anything. I am especially interested in armv7hl for a BB-xM. Regards Bernhard Schuster -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

6 12

[opensuse-arm] [ml-admin] Merging the architecture lists to opensuse-arch
by Henne Vogelsang 27 Oct '11

27 Oct '11

Hey, we are currently trying to reduce the amount of communication channels we provide. Because of this I would like to merge the 4 architecture lists into one list called opensuse-arch. If nobody objects until the 15th of November 12:00 UTC I will merge the lists. You don't have to do anything except rewriting your filter if you use one. Thanks in advance for your consideration. Henne -- Mailing List Admin http://lists.opensuse.org -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

6 7

Re: [opensuse-arm] [ml-admin] Merging the architecture lists to opensuse-arch
by Joop Boonen 26 Oct '11

26 Oct '11

On Wed, October 26, 2011 3:25 pm, Andreas Färber wrote: > Hi, > > Am 26.10.2011 15:04, schrieb Henne Vogelsang: >> On 26.10.2011 14:58, Adrian Schröter wrote: >>> Am Mittwoch, 26. Oktober 2011, 14:29:57 schrieb Henne Vogelsang: >>>> >>>> we are currently trying to reduce the amount of communication channels we provide. Because of this I would like to merge the 4 architecture lists into one list called opensuse-arch. >>>> >>>> If nobody objects until the 15th of November 12:00 UTC I will merge the >>>> lists. You don't have to do anything except rewriting your filter if you >>>> use one. >>> >>> I would definitive unsubscribe from such a list if the majority of mails is >>> not interessting for me. >> >> The ppc, amd64 and ia64 lists didn't have any traffic in 2010 and 2011. I would like to have some point for people to go for non x86 >> architecture specific stuff. > > There was some recent activity to revive ppc openSUSE, so if arm stays ppc should probably stay as well. > amd64 is mainstream now, so that's different I guess. > I agree. I think it's best to have separate mailing lists for different architectures. I think traffic wise it also safes bandwidth. Only people that are interested in a specific mailing list will get this mail and not traffic they don't want. The ppc mailing list will be very interesting again when the AmigaOne X1000 and Netbook will be released. http://en.wikipedia.org/wiki/AmigaOne_X1000 http://eab.abime.net/showthread.php?p=781936 If this ends up in an active mailing list where also ARM resides it's difficult to filter, I'm subscribed to both. > Andreas > > -- > SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 16746 AG Nürnberg -- > To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org > To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org > Regards, Joop. -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

1 0

[opensuse-arm] Re: [opensuse-ppc] [ml-admin] Merging the architecture lists to opensuse-arch
by Joop Boonen 26 Oct '11

26 Oct '11

On Wed, October 26, 2011 2:29 pm, Henne Vogelsang wrote: > Hey, > > we are currently trying to reduce the amount of communication channels we provide. Because of this I would like to merge the 4 architecture lists into one list called opensuse-arch. > > If nobody objects until the 15th of November 12:00 UTC I will merge the lists. You don't have to do anything except rewriting your filter if you use one. > Wouldn't it be best to leave the arm mailing list as is until the arm port has been completed? > Thanks in advance for your consideration. > > Henne > > -- > Mailing List Admin > http://lists.opensuse.org > -- > To unsubscribe, e-mail: opensuse-ppc+unsubscribe(a)opensuse.org > To contact the owner, e-mail: opensuse-ppc+owner(a)opensuse.org > > Regards, Joop. -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

1 0

[opensuse-arm] request/sugestion to work together to get hardfp/OSS ARM GPU drivers and/or to get documentation
by Joop Boonen 23 Oct '11

23 Oct '11

Hi all, Most of the (ARM) distros are currently working on or in the transition to hardfp, but until now most GPU's in de ARM Cortex SOCs don't have any hardfp drivers yet. To be able to have a ARM hardfp compiled X Window desktop system/notebook with 3D support we need hardfp compiled drivers. I was thinking it might be more efficient is all Linux distro's work together to get these drivers as it's equally important for all distro that wants to move to a hardfp distro. What do you all think, who wants to work together to get full hardfp support for as most as possible ARM SOC GPUs? It would be great if we can in the end even have OSS drivers. Regards, Joop. -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

2 2

[opensuse-arm] request/sugestion to work together to get hardfp/OSS ARM GPU drivers and/or to get documentation
by Joop Boonen 22 Oct '11

22 Oct '11

Hi all, Most of the (ARM) distros are currently working on or in the transition to hardfp, but until now most GPU's in de ARM Cortex SOCs don't have any hardfp drivers yet. To be able to have a ARM hardfp compiled X Window desktop system/notebook with 3D support we need hardfp compiled drivers. I was thinking it might be more efficient is all Linux distro's work together to get these drivers as it's equally important for all distro that wants to move to a hardfp distro. What do you all think, who wants to work together to get full hardfp support for as most as possible ARM SOC GPUs? It would be great if we can in the end even have OSS drivers. And to have a good relationship with the GPU designers (for ARM SOCs) and hardware producers. If you know other distro's that are working on an ARM port or people that might want to help, an you please forward the email to them? Regards, Joop. -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

1 0

[opensuse-arm] [Fwd: RE: sgx540 linux drivers]
by Joop Boonen 19 Oct '11

19 Oct '11

Hi All, I'm investigating which GPU drivers are most compatible with GPL. Below you can see the answer I got from Imagination Technologies about the SGX540 driver, earlier on. Regards, Joop. Hi Joop, Yes, that is correct in most of the cases. There are parts that need to be customised for the platform like display drivers, memory configurations, etc. Regards Carlos. -----Original Message----- From: Joop Boonen [mailto:joop_boonen@*.*] Sent: 28 June 2011 10:16 To: Carlos Sarria Cc: IMGKL - DevTech Subject: RE: sgx540 linux drivers Hi Carlos, For my understanding. Does this mean that sgx540 drivers aren't generic drivers, that can be used for any ARM SOC that uses this GPU like the Samsung Hummingbird for instance? Regards, Joop. On Mon, June 27, 2011 5:07 pm, Carlos Sarria wrote: > Hi Joop, > > To release drivers for TI's platforms is not our responsibility and > MeeGo project on PandaBoard is completely unofficial. I doubt TI will > support it, although it will depend on the level of adoption of that > OS and whether TI sees any business opportunity on it. > > Best regards > > Carlos. > ------------------------------------------------------------------- > Carlos Sarria > Developer Technology Manager > Imagination Technologies Ltd. > Tel: +44 (0)1923 * > mail: *(a)imgtec.com > http://www.imgtec.com/ http://www.powervrinsider.com/ > > > > -----Original Message----- > From: Joop Boonen [mailto:joop_boonen@*.*] > Sent: 27 June 2011 11:37 > To: IMGKL - DevTech > Subject: sgx540 linux drivers > > Dear Madam, Sir, > > I'm using MeeGo on my Pandaboard. There aren't any sgx540/OMAP4430 > Linux drivers/source tar-ball available. > Do you know if/when they will be available? > > Thank you for your time. > > Regards, > > Joop. > -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

1 0

[opensuse-arm] [Fwd: Re: FW: Mali400 GL ES OSS drivers (502137)]
by Joop Boonen 19 Oct '11

19 Oct '11

Hi All, I'm investigating which GPU drivers are most compatible with GPL. Below you can see the answer I got from ARM about the Mali driver. As you can see the GL ES part isn't and probably won't be open sourced in the near future. Regards, Joop. [From Herve Lebreton - ARM Technical Support] Hello joop, > I'm very happy that you opened up the 2D part of the Mali drivers. The kernel driver was GPLed in order to comply with Android requirements. > I understood that the GL ES drivers for the Mali GPU are not open > source. > I've read they are in the Mali DDK. > I wonder who is allowed to use the DDK and if it's opensource? If not > are > there any plans to opensource the DDK? The DDK in user space is not open source and we have no plans to change this at the moment. Only ARM/Mali licensee have full access to the DDK source code so the normal procedure is that if you have any queries you should contact your SOC designer/ARM licensee (Depending on the request they may push it to ARM). Hope this helps. Regards, Hervé. -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

1 0

[opensuse-arm] No more armv7hl anymore in openSUSE:Factory:ARM ?
by Joop Boonen 18 Oct '11

18 Oct '11

All, I don't see the armv7hl build anymore in openSUSE:Factory:ARM. I hope it doesn't mean that we won't build armv7hl anymore? Regards, Joop. -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

4 5

Re: [opensuse-arm] injecting arm packages
by Ulrich Hecht 17 Oct '11

17 Oct '11

On Monday 17 October 2011, Andreas Färber wrote: > I had spotted one source of errors last week: qemu-arm was being built > without libattr.a, so some xattr-related features were disabled, > resulting in lots of unsupported syscall messages. > > A new libattr-devel-static package is now in Factory and we need the > qemu package to depend on it. Don't know on what condition to choose > between libattr-devel and libattr-devel-static build dependency now. > Any help appreciated. AFAIK the QEMU system emulators don't use libattr, so it should be sufficient to have a build dependency on libattr-devel-static. CU Uli -- SUSE LINUX Products GmbH, Maxfeldstraße 5, 90409 Nürnberg, Germany GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 16746 (AG Nürnberg) -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

2 1

Re: [opensuse-arm] injecting arm packages
by Adrian Schröter 17 Oct '11

17 Oct '11

Am Sonntag, 16. Oktober 2011, 20:29:38 schrieb Andrew Wafaa: > Michal has also been able to build gtk2 on native hardware too. I injected gtk2 a while ago. I am currently injecting a texlive build from Alexander. > Could we add > these to the list of packages to inject? When building with Qemu gtk2 > repeatedly causes a segfault and fails to build. At some point we need to fix the build or we can not ever make an ARM distribution release. No matter what the reason of this failure is. bye adrian > Regards, > > Andy > > -- > Sorry for top posting > > Andrew Wafaa > IRC: FunkyPenguin > GPG: 0x3A36312F > > On 16 Oct 2011 19:49, "Alexander Graf" <agraf(a)suse.de> wrote: > > Hi Adrian, > > > > We have a couple of pretty core packages that I can build just fine with > > native hardware, but did not manage to build with QEMU yet (namely, > > texlive-bin and yast2-core). However, since I can build them just fine > > on > > hardware, I can easily produce working rpms. > > > > Can we inject those rpms into the repository and with that at least > > continue building something we can then later on base a worker image on > > so we can then build everything natively? > > > > > > Alex > > > > -- > > To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org > > To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org -- Adrian Schroeter SUSE Linux Products GmbH email: adrian(a)suse.de

3 3

[opensuse-arm] injecting arm packages
by Alexander Graf 16 Oct '11

16 Oct '11

Hi Adrian, We have a couple of pretty core packages that I can build just fine with native hardware, but did not manage to build with QEMU yet (namely, texlive-bin and yast2-core). However, since I can build them just fine on hardware, I can easily produce working rpms. Can we inject those rpms into the repository and with that at least continue building something we can then later on base a worker image on so we can then build everything natively? Alex -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

1 0

[opensuse-arm] iproute2 build without pdf documentation for once, as texlive-latex is broken?
by Joop Boonen 14 Oct '11

14 Oct '11

I have a request. iproute2 is a crucial package to install sysconfig. iproute is not build because of an issue with texlive-latex. This package is needed to generate the pdf files. (make pdf) I don't know if it's allowed for once to build this package just once without documentation in openSUSE:Factory:ARM, so openSuSE ARM can be tested with sysconfig? Can the "patch" please be applied once, in openSUSE:Factory:ARM, and rolled back after the package has been build and published? <diff> osc diff Index: iproute2.spec =================================================================== --- iproute2.spec (revision 86ae9170e809de093551e2286d24a5ba) +++ iproute2.spec (working copy) @@ -41,7 +41,8 @@ BuildRequires: libpng-devel libtiff-devel pkgconfig >= 0.19 BuildRequires: xorg-x11-devel xz %if 0%{?suse_version} -BuildRequires: ghostscript-x11 sgmltool texlive-latex +BuildRequires: ghostscript-x11 sgmltool +#BuildRequires: ghostscript-x11 sgmltool texlive-latex %endif %if 0%{?fedora} || 0%{?rhel} BuildRequires: ghostscript linuxdoc-tools sgml-common tetex-dvips tetex-latex @@ -94,7 +95,7 @@ xtlibdir="$(pkg-config xtables --variable=xtlibdir)"; make %{?_smp_mflags} LIBDIR=%_libdir CCOPTS="-D_GNU_SOURCE %optflags -Wstrict-prototypes -fPIC -DXT_LIB_DIR=\\\"$xtlibdir\\\"" cd doc -make pdf +#make pdf %install install -d %buildroot/{etc/,sbin/,usr/{sbin,share/man/man{3,8}}} @@ -125,8 +126,8 @@ %files doc %defattr(-,root,root) -%doc doc/api-ip6-flowlabels.pdf doc/arpd.pdf doc/ip-cref.pdf -%doc doc/ip-tunnels.pdf doc/nstat.pdf doc/rtstat.pdf doc/ss.pdf +#%doc doc/api-ip6-flowlabels.pdf doc/arpd.pdf doc/ip-cref.pdf +#%doc doc/ip-tunnels.pdf doc/nstat.pdf doc/rtstat.pdf doc/ss.pdf %doc ChangeLog examples/ ip/ifcfg ip/routef ip/routel %files -n libnetlink-devel </diff> Regards, Joop. -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

4 3

[opensuse-arm] openSUSE got hardware!
by Dirk Müller 14 Oct '11

14 Oct '11

Hi, What a nice surprise, we got a set of genesi Efika MX today: http://www.suse.de/~dmueller/efikamx/efikamx2.jpeg These are two standalone computer, and two smartbook/netbook like laptops. We've already set them up and just started package building on it. They're not yet connected to the external build service, this will come over the next weeks when Adrian is back. Thanks a lot! Greetings, Dirk -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

1 0

[opensuse-arm] Getting the correct kernel
by Andrew Wafaa 13 Oct '11

13 Oct '11

I know one of the reasons we chose a single target for hardware was to make the job of getting the right kernel and associated modules somewhat easier. Now (un)fortunately, we have some kind sponsors of hardware Genesi with the Efika MX and Pandaboard.org with the PandaBoard. How difficult would it be to have a single kernel that supports both these devices? I've had a sniff on the web and have found a kernel repo for EfikaMX[0] and PandaBoard[1], there is also the Linaro kernel[2] which I believe supports them; nice to have would be the BeagleBoard too. I believe they should all be supported in upstream but I can't say for certain, saying that though I believe the EfikaMX needs the siihdmi driver pushing upstream for the 3.x kernel. I have a contact to push about this and will chase him up later today. Regards, Andy 0=http://gitorious.org/efikamx/linux-kernel 1=http://gitorious.org/pandaboard/kernel-mainline 2=http://git.linaro.org/gitweb?p=kernel/linux-linaro-3.1.git;a=summary -- Andrew Wafaa IRC: FunkyPenguin GPG: 0x3A36312F -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

3 4

[opensuse-arm] debian for native builds
by Peter Czanik 13 Oct '11

13 Oct '11

Hello, How can I use Debian for native builds? I have the Debian ARM HF running on my EFIKA smartbook. It also has "osc" installed, but when I try to build something, it complains, that build is not available. Bye, CzP -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

2 1

[opensuse-arm] hwinfo of the PandaBoard booted with openSuSE ARM
by Joop Boonen 12 Oct '11

12 Oct '11

Hi all, For who are interested. This is the hwinfo , /proc/cpuinfo and /proc/meminfo output of the PandaBoard booted with openSuSE ARM. Regards, Joop.

1 0

[opensuse-arm] Just got the openSuSE ARM port running on the Pandaboard
by Joop Boonen 12 Oct '11

12 Oct '11

Hi All, I just got a basic openSuSE ARM port, OBS build armv7hl packages openSuSE packages, running on the Pandaboard. I used mic2, the script that is used for MeeGo. I had to patch 2 things one for the password and one as not all packages are available yet. Otherwise the mic2 build would stop because of a raise. I used these MeeGO panda instructions: http://wiki.meego.com/ARM/OMAP4_Panda I used a adapted Panda.ks.in and Panda.sh file, I've attached these files. MLO & u-boot was build according to: http://elinux.org/Panda_How_to_MLO_%26_u-boot I've attached all files. Regards, Joop. I've also posted 2 videos on you-tube: http://www.youtube.com/watch?v=bf5zKT2gWKs http://www.youtube.com/watch?v=FMziSoonpTU

1 0

[opensuse-arm] All JeOS packages according kiwi (suse-11.4-JeOS)
by Joop Boonen 10 Oct '11

10 Oct '11

Hi all, This are all packages that have been installed for kiwi image template suse-11.4-JeOS . These packages except grub and pciutils will also be needed for a basic arm install. It might be best to focus on fixing these packages first? So we can get a running machine faster and start testing on the Pandaboard. What do you all think? Regards, Joop.

5 7

[opensuse-arm] ipfire port to ARM
by Bill Merriam 08 Oct '11

08 Oct '11

It looks like you guys are doing very well with the port and probably don't need help but I decided to tell you about this distro that just did an ARM port. ipfire is based on Linux From Scratch, do they don't use RPM. Their announcement is here. http://www.ipfire.org/news/ipfire-2.11-available-on-arm The mailing list where they talk about the port is here. http://lists.ipfire.org/pipermail/sig-arm/ Their GIT repository with the ARM patches is here. I suppose we could shamelessly look at how they did it. http://git.ipfire.org/?p=people/ms/ipfire-2.x.git;a=shortlog;h=refs/heads/a… Since they started with a different software base I don't think the patches would be directly usable but if somebody is having trouble with a particular package you could look to see how they did it. I think we would thank them if we did that. Bill -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

1 0