Hi,
What do you think about adding couple of test cases for ARM to our
openQA? I remember two cases when our JeOSes were broken independently
of hardware. First one, when u-boot was looking for boot.scr in wrong
place, second one, when the kernel 3.14 was broken due to bug in depmod.
So, I think that we could test JeOS-vexpress and JeOS-vexpress64 for
armv7 and aarch64 using qemu emulation (I know that it is slow ;) )
Then just check that the image is booted for the first time, and for the
second time, controlling the process through serial console.
At the moment I have no idea how many efforts are needed to implement this.
--
To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org
Hello Ciaran,
Kindly please see this license:
https://github.com/NVIDIA/tegrarcm/blob/master/LICENSE
in part of src/miniloader binaries.
I'm in doubt can i package and redistribute tegrarcm on obs and with
which license
if it is possible.
--
Best Regards,
Misha Komarovskiy
zombahatgmaildotcom
--
To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org
Hi,
Anybody still using CuBox? I mean the old one:
https://en.opensuse.org/HCL:CuBox openSUSE 12.2 seems to be a bit old :(
Bye,
CzP
--
To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org
Greetings,
I had a chance to test JeOS Factory Build 207.2 (13-Sep-14) on the Pi
this weekend and found it didn't boot.
U-boot loads.
It looks for /uEnv.txt, fails to find it.
U-boot next looks for, and finds /boot.scr.
It reads and executes the scrip.
Then this happens:
-----
switch to partitions #0, OK
mmc is current device
** File not found boot/linux.vmx **
SCRIPT FAILED: continuing...
** Bad Partition specification mmc 0:0:2 **
** Bad Partition specification mmc 0:0:2 **
** Bad Partition specification mmc 0:0:2 **
U-Boot>
-----
There is a linux.vmx at the top level of the boot partition - so maybe a
script path problem?
-A
--
To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org
Hi,
I've found that we have Mesa package in initial initrd in our JeOSes. Do
we really need it? I estimated it takes about 20MB of 130MB total size
of uncompressed initrd.
Typical ARM boards don't have lots of RAM like big x86 servers.
--
To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org
Hi all,
I've just found this:
https://news.opensuse.org/2014/03/19/development-for-13-2-kicks-off/
"""The btrfs filesystem is default (and comes with btrfsprogs 3.12), as
is the wicked network management tool (replacing ifup) and the dracut
initrd replacement"""
But our JeOS images still not use btrfs. Should they? At least for 13.3
release.
--
To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org
Hi,
I think we need ARM support for http://software.opensuse.org
At least for couple best-supported boards.
--
To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org
Hi,
We have a 12.3 image for iMX53 loco, no image in 13.1 and an image with an old kernel and an old u-boot in Factory.
Should we update the kernel and u-boot or should we drop it ?
Is there anyone with such a board for testing new u-boot and new kernel (-default flavour or not upstream?).
Guillaume
--
To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org
Hi,
Same questions as iMX53 loco.
We have a 12.3 image, no image in 13.1 and no image in Factory.
Contrary to iMX53 loco, origen is upstream and we should be able to use our default kernel.
Is there anyone around who have an origen board to test a factory JeOS-origen image?
Guillaume
--
To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org