|

|
|
|
|
|
|
|
i.MX515 Project
 |
openSUSE support
in category Linux Distributions proposed by Peter Czanik on 2nd February 2009 (accepted on 1st June 2009)
|
|
|
|
|
|
|
|
|
|
|
|
|
Project Summary
openSUSE is one of the most popular Linux distributions. Right now it is available for x86, PPC and an unofficial port to Itanium. Recently ARM support was added to the openSUSE Build Service , which is used to build the distribution. Some people are already working to port openSUSE to ARM in QEMU.
My plan is to use my experiences from previous openSUSE board bringup works ( EFIKA , MPC8610 and MPC5121e and enable i.MX515 support for the next release.
|
|
|
|
|
Project Blog Entries
|
|
|
|
|
|
|
openSUSE 11.2
posted by Peter Czanik on 12th February 2010
openSUSE 11.2 is now being ported to ARM. The base compile system is finally ready (there were some troubles due to incompatible Build Service changes), just as the third of the rest of the packages. Right now I'm reviewing failed packages, as these block the building of many others. My first fix was just accepted, and suddenly the compile farm started to work on many new 11.2 ARM packages again :-)
|
|
|
|
|
|
|
|
|
|
|
|
and without a chroot
posted by Peter Czanik on 19th August 2009
This time I was able to boot the system without a chroot. It is still just the base system, but with some tricks, it is also possible to boot it directly, without the need of the chroot.
The next step is to install a lot more packages, including YaST and most major desktops and applications.
|
|
|
|
|
|
|
|
|
|
|
|
openSUSE ARM in chroot
posted by Peter Czanik on 24th July 2009
Today another important milestone: openSUSE ARM binaries run in chroot. This is the base system, just enough for bootstrapping and compiling packages. It can't even boot on its own, as some packages are missing, like udev & Co.
The chroot environment is actually a byproduct of osc, the command line client for the openSUSE Build Service. It is also able to do local builds, and for that it creates a chroot environment.
And a mandatory copy&paste:
root@ubuntu:~# chroot suse suse:/> gcc -v Using built-in specs. Target: armv7l-suse-linux-gnueabi Configured with: ../configure --prefix=/usr --infodir=/usr/share/info --mandir=/usr/share/man --libdir=/usr/lib --libexecdir=/usr/lib --enable-languages=c,c++,objc,fortran,obj-c++ --enable-checking=release --with-gxx-include-dir=/usr/include/c++/4.4 --enable-ssp --disable-libssp --with-bugurl=http://bugs.opensuse.org/ --with-pkgversion='SUSE Linux' --disable-libgcj --disable-libmudflap --with-slibdir=/lib --with-system-zlib --enable-__cxa_atexit --enable-libstdcxx-allocator=new --disable-libstdcxx-pch --enable-version-specific-runtime-libs --program-suffix=-4.4 --enable-linux-futex --without-system-libunwind --build=armv7l-suse-linux-gnueabi Thread model: posix gcc version 4.4.0 [gcc-4_4-branch revision 147703] (SUSE Linux)
|
|
|
|
|
|
|
|
|
|
|
|
openSUSE support
posted by Peter Czanik on 24th June 2009
I got my board a while ago, and it did not rest much ever since. Even when I did not have time for testing, it was in use, as it has fantastic audio quality :-)
As the openSUSE ARM port is not there yet, that one could install it, I spent my time getting better known with the hardware, firmware and software available.
The board came pre installed with Ubuntu, so I first experimented with that.
Then I tried Debian. I had some troubles configuring Xorg, and other minor glitches, but for the rest it was a pleasant experience, and felt slightly faster and more responsive on the same hardware than Ubuntu.
I tested the Fedore ARM port, but gave up after half a day not being able to go ahead with it.
The Movial demo was really impressive on the board, HD movie playback, and other features of the board demoed. Of course, this is not a Linux designed for hacking, but rather a nice interface for a PMP, so I quickly switched back to Debian.
Today I reached an important milestone: the first self compiled kernel is running. As a first step, I added support for an USB Ethernet converter, as I prefer to use Ethernet instead of WiFi. This is also an important step towards openSUSE support, as to install and boot openSUSE on the board, I need a custom configured kernel to the distributions need.
|
|
|
|
|
|