Hi,
> Kiwi seems to have been updated by Dirk:
> https://build.opensuse.org/package/rdiff/openSUSE:13.1:Ports/kiwi?linkrev=base&rev=2
yes I just checked out the project and saw this too, that looks
good to me
> But still fails:
> https://build.opensuse.org/package/live_build_log/openSUSE:13.1:Po
Hi,
> > Anything I did wrong here ?
>
> You should provide a DTB (device tree blob) to the kernel so that the kernel
> identify which board it is running on.
> Previously Linux kernel had board descriptions built-in, so no DTB were used.
I thought kernel-exynos is still a kernel without device
Le 30/10/2013 17:23, Marcus Schäfer a écrit :
> Hi,
>
>> Seems your new patch does not help armv7 images. :(
> I did not get any feedback from Dirk that the patch is really
> active. Are you sure the change was applied somewhere in the
> buildservice space ?
>
> I have it all up and running buildi
Hi,
I buit an image for the origen board with
kernel-exynos-3.11.6-2.1.armv7hl
u-boot-origen-2013.04-3.1.7.armv7hl
on boot I get the following information:
snip--
U-Boot 2013.04 (Oct 21 2013 - 22:37:12) for ORIGEN
Le 30/10/2013 10:54, Marcus Schäfer a écrit :
> Hi,
>
>> Your kiwi patch in 13.1:Ports did not fix it (see [0]) and now armv6 also
>> fails on kernel extraction, see [1].
> I'm working on this one and will come up with a patch today
Seems your new patch does not help armv7 images. :(
Guillaume
Le 30/10/2013 17:12, Marcus Schäfer a écrit :
> Hi,
>
>>> Your kiwi patch in 13.1:Ports did not fix it (see [0]) and now armv6 also
>>> fails on kernel extraction, see [1].
>> I'm working on this one and will come up with a patch today
> I submitted a patch to kiwi and tested a build
> hope we ge
Hi,
> Seems your new patch does not help armv7 images. :(
I did not get any feedback from Dirk that the patch is really
active. Are you sure the change was applied somewhere in the
buildservice space ?
I have it all up and running building armv7l images on my
panda board, tested kernels: kernel-
Le 30/10/2013 17:19, Marcus Schäfer a écrit :
> Hi,
>
> I buit an image for the origen board with
>
> kernel-exynos-3.11.6-2.1.armv7hl
> u-boot-origen-2013.04-3.1.7.armv7hl
>
> on boot I get the following information:
>
> snip--
>
> U-Boot 2013.04 (Oct 21 2013 - 22:37:12) f
Hi,
> > Your kiwi patch in 13.1:Ports did not fix it (see [0]) and now armv6 also
> > fails on kernel extraction, see [1].
>
> I'm working on this one and will come up with a patch today
I submitted a patch to kiwi and tested a build
hope we get back on track soon
Regards,
Marcus
--
Public K
Hi,
We already faced this problem before but cannot find what was the solution.
Factory ARM images (both armv6 and armv7) are unresolvable because of this
error:
**
nothing provides ERROR_NO_BOOT_CONFIG_FILE_FOUND needed by
kiwi
Hi,
> Your kiwi patch in 13.1:Ports did not fix it (see [0]) and now armv6 also
> fails on kernel extraction, see [1].
I'm working on this one and will come up with a patch today
Regards,
Marcus
--
Public Key available
gpg --keyserver pgp.mit.edu --recv-keys 0xCCE3C6A2
-
On Tue, Oct 29, 2013 at 07:57:25PM +0100, Guillaume Gardet wrote:
>
> Le 29/10/2013 16:37, Guillaume Gardet a écrit :
> > Le 29/10/2013 16:35, Stefan Dirsch a écrit :
> >> On Tue, Oct 29, 2013 at 04:04:26PM +0100, Guillaume Gardet wrote:
> >>> Ok. This is where I am not sure how to handle it corre
Le 30/10/2013 09:30, Stefan Seyfried a écrit :
> Am 29.10.2013 15:40, schrieb Guillaume Gardet:
You can find it here and there for Factory and 13.1 :
https://build.opensuse.org/package/show/devel:ARM:Factory:Contrib:RaspberryPi/raspberrypi-firmware
https://build.opensuse.org/package
Am 29.10.2013 15:40, schrieb Guillaume Gardet:
>>> You can find it here and there for Factory and 13.1 :
>>> https://build.opensuse.org/package/show/devel:ARM:Factory:Contrib:RaspberryPi/raspberrypi-firmware
>>> https://build.opensuse.org/package/show/devel:ARM:13.1:Contrib:RaspberryPi/raspberrypi-
Le 30/10/2013 08:54, Dirk Müller a écrit :
> Hi Guillaume,
>
> That sounds all too familiar to me...
>
>
>>> when I build locally JeOS-raspberrypi image, I get a *.raw image but it
>>> seems that partitioning is a bit strange.
>>> We have the 2 partitions:
>>> * 1st: FAT32 for Pi bootloader (mand
Hi Marcus,
Le 29/10/2013 10:59, Marcus Schäfer a écrit :
> Hi,
>
>> As you can see here:
>> https://build.opensuse.org/project/monitor/openSUSE:13.1:Ports
>>
>> armv7 images are still broken with the same error message as in Factory some
>> time ago (which should have been fixed): "Couldn't find
Hi Guillaume,
> We have devel:ARM:13.1:Contrib:* projects pointing to openSUSE:13.1
> (repository="ports"). Should not we make them pointing to openSUSE:13.1:Ports
> (repository="ports"), so that we have latest fixes?
The actual plan is to not have any extra code overlays in
openSUSE:13.1:Ports
Hi Oscar,
> Please, add kernel-sun7i to the list. I'm building kernel-sun7i from the
> linux-sunxi project since the code for the A20 SoC is not fully upstream.
Where do you build the kernel? I'd like to include it in the Contrib
project for sunxi. I have built a 12.3 based image that seems to wo
Hi Guillaume,
That sounds all too familiar to me...
>> when I build locally JeOS-raspberrypi image, I get a *.raw image but it
>> seems that partitioning is a bit strange.
>> We have the 2 partitions:
>> * 1st: FAT32 for Pi bootloader (mandatory unfortunately) with bootflag
>> enabled
>> * 2nd
19 matches
Mail list logo
