Hi,
I wanted to test latest u-boot for beagleboard (we currently use an old linaro u-boot for beagleboard).
And I found some problems about ext2 to ext4 transition (due to u-boot update I guess).
First error is in mlo-ext2.patch in spl/Makefile:
+LIBS-$(CONFIG_SPL_FAT_SUPPORT) += fs/ext2/libext2fs.o
should be replaced with:
+LIBS-$(CONFIG_SPL_FAT_SUPPORT) += fs/ext4/libext4fs.o
otherwise, we have a build error since ext2 does not exist!
Once fixed, boot from MMC hangs early because "ext4fs_set_blk_dev" function is misused.
We are using:
err = ext4fs_set_blk_dev(&mmc->block_dev,
CONFIG_SYS_MMC_SD_FAT_BOOT_PARTITION);
But arg number 2 must be "disk_partition_t *info" and not "int" as it was the case for ext2fs_set_blk_dev!
Alex, could you have a look at it? According to the *.changes files, you are the best to fix it! ;)
Guillaume
--
To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org
Hi,
I'm using the image "openSUSE-12.2-ARM-JeOS-panda.armv7l-1.12.1-Build1.46.1.raw.xz" (uname -r -> 3.4.6-2.10-omap2plus)
for the Pandaboard ES. Is this the latest one, because the current images does not have a version number anymore? If
not, can I upgrade to the latest stable via zypper?
Actually the default software repositories are:
sudo zypper lr -u
# | Alias | Name | Enabled | Refresh | URI
--+-----------------------------+----------------------------+-----------+---------------+-----------
1 | openSUSE-12.2-ARM-Repo-OSS | openSUSE-12.2-ARM-Repo-OSS | Yes | No |
http://download.opensuse.org/ports/armv7hl/distribution/12.2/repo/oss/
2 | openSUSE-12.2-ARM-Updates | openSUSE-12.2-ARM-Updates | No | Yes |
http://download.opensuse.org/ports/armv7hl/update/12.2/
I had to disable repo 2, because it is invalid (error message while refreshing it). Is this a known error? Is there a
valid update repository?
Regards,
endym
--
To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org
Hi,
I was wondering if we want to use /lib64 and /usr/lib64 for AArch64 or use /lib and /usr/lib.
It seems Fedora uses lib64 whereas linaro uses lib.
Debian seems to use a symlink so that lib and lib64 are the same.
Some people discussed about that on cross-distro list some times ago; AArch64 triplet thread:
http://lists.linaro.org/pipermail/cross-distro/2012-November/thread.html
It seems Fedora is right using lib64 convention.
Should we use it also? It is better to decide now since aarch64 is at an early stage.
Guillaume
--
To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org
I'm curious if anyone is planning on attending Linaro Connect in March
which will be held in Hong Kong? I appreciate it's a bit of a journey
for most, but still. Unfortunately this year they have started
charging for non-member attendees, but this is something that the
Travel Support Team at openSUSE could help with.
If not, I understand, but there will be two more Connect events this
year - one in Europe and One in the US. It would be great if others
could attend. Not only to fly the openSUSE (and SUSE) flag, but
crucially to glean as much information as you can from many of the
people that are actively involved upstream.
Regards,
Andy
--
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
Hi guys,
FOSDEM is close, we want everybody to talk about openSUSE and as ARM is
super cool the idea how to do it is to do some periodical demos -
something like five or ten minutes (can be longer) at booth in
predefined time slots about what cool stuff can you do with ARM. We are
going to have there ARM based Chromebooks to demo stuff. What we are
missing is volunteers to do the demos, schedule and the demos :-D
Few ideas that comes to my mind:
* Web development on Chromebook
Ok, little lame, but we can show that if you replace ChromeOS with
openSUSE, you can do web development on it, like rails or even much
cooler tntnet[1]. I can test, prepare and do this one.
* KVM and Chromebook
If I'm not mistaken, Cromebooks do have Cortex A-15 and thus support for
virtualization, kernel 3.8 and KVM should have support for that as well,
so theoretically, we can boot some virtual machine on Chromebook, which
would be awasome even as an article/video to do some promo after the
FOSDEM. Only trouble is, that I'm not sure how much work it is and I
don't have a Chromebook. So this one would require somebody else to
prepare and test.
* WiFi sniffing/cracking
I have no experience with that so it would be again nice if somebody
else would step in and do some demo. We can connect to the public WiFi
that is going to be there and sniff around or setup some local AP and
crack it on the spot...
* Packaging
We can do pretty ordinary OBS packaging demo with one minor modification
- do everything on Chromebook and in the end submit package in OBS to
get packages even for other architectures. I can do that one as well.
These were just a few ideas and I can make happen only two of them, so I
would like to call for volunteers and for more ideas :-D We can off
course do same demo twice or trice for different audience, but if we
will get more cool stuff, it will be better. When we had these workshop
sessions on LinuxTag, I remember that people came. Although the most
packed were Hennes evening crafting sessions...
[1] http://www.tntnet.org/
--
Michal Hrusecky <Michal(a)Hrusecky.net>
--
To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org
Hi,
I have some errors with rpmbuild for aarch64.
Once compilation is done successfully, I get an error for packaging files:
error: No file attributes configured
Maybe a macro file not included?
Example of pkg-config:
********************************************************************************
Making install in check
make[1]: Entering directory `/usr/src/packages/BUILD/pkg-config-0.27.1/check'
make[2]: Entering directory `/usr/src/packages/BUILD/pkg-config-0.27.1/check'
make[2]: Nothing to be done for `install-exec-am'.
make[2]: Nothing to be done for `install-data-am'.
make[2]: Leaving directory `/usr/src/packages/BUILD/pkg-config-0.27.1/check'
make[1]: Leaving directory `/usr/src/packages/BUILD/pkg-config-0.27.1/check'
+ rm /usr/src/packages/BUILDROOT/pkg-config-0.27.1-0.aarch64/usr/share/doc/pkg-config/pkg-config-guide.html
+ /usr/lib/rpm/brp-compress
+ /usr/lib/rpm/brp-suse
Processing files: pkg-config-0.27.1-0.aarch64
Executing(%doc): /bin/sh -e /var/tmp/rpm-tmp.8ntDEJ
+ umask 022
+ cd /usr/src/packages/BUILD
+ cd pkg-config-0.27.1
+ DOCDIR=/usr/src/packages/BUILDROOT/pkg-config-0.27.1-0.aarch64/usr/share/doc/packages/pkg-config
+ export DOCDIR
+ /bin/mkdir -p /usr/src/packages/BUILDROOT/pkg-config-0.27.1-0.aarch64/usr/share/doc/packages/pkg-config
+ cp -pr AUTHORS COPYING NEWS README ChangeLog pkg-config-guide.html /usr/src/packages/BUILDROOT/pkg-config-0.27.1-0.aarch64/usr/share/doc/packages/pkg-config
+ exit 0
error: No file attributes configured
Obsoletes: pkgconfig < 0.21
Checking for unpackaged file(s): /usr/lib/rpm/check-files /usr/src/packages/BUILDROOT/pkg-config-0.27.1-0.aarch64
RPM build errors:
No file attributes configure
********************************************************************************
Guillaume
--
To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org
Hi,
Finaly, I got an image from OBS for Raspberry Pi (armv5 image) but I have the following problem.
All boot files (kernel image, etc.) are in /boot folder from ext3 partition, not in FAT32 boot partition.
Any idea why? So that we could fix it?
Guillaume
--
To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org
Hi,
I would like to make a wiki page about AArch64 (armv8) to list all things we must do for AArch64 in openSUSE.
A page name like openSUSE:AArch64 looks good to me. Any objection?
I have already some informations about AArch64 build but nothing on what is needed to get things in openSUSE (understand in OBS). I mean, what is needed to be able to start building AArch64 packages?
I guess we must have a minimal rootfs with some tools? Or maybe just cross-compile?
I already tested my own rootfs (built with the buildroot tool).
I used :
* a bootimg: http://releases.linaro.org/12.12/openembedded/aarch64/img-foundation.axf
* u-boot: http://fedorapeople.org/~ahs3/u-boot.bin
* Foundation_v8 (sort of qemu but seems to not be redistribuable)
* A custom rootfs (I built using buildroot. See: buildroot.net)
I built my own image with fdisk and files listed above and got it running:
Foundation_v8 --image img-foundation.axf --block-device ./tmp/rootfs.img --network=nat
So, what would be the next step?
Regards,
Guillaume
--
To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org
Hi guys,
What do you think about quad core cortex-A9 1GHz vs dual core cortex-A15 1.7 GHz?
I saw 2 boards :
* Freescale IMX6 SABRE-LITE : quad cortex-A9 1GHz - 1 GB DDR3
* ARMBRIX-5250-A : dual cortex A15 1.7 GHz - 2 GB DDR3
I guess dual cortex-A15 is better compared to quad cortex-A9? (For desktop use).
Any experience using this kind of boards?
Guillaume
--
To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org