From: Wolfgang Grandegger <wg@domain.hid>
To: Daniel Schnell <daniel.schnell@domain.hid>
Cc: Xenomai help <xenomai@xenomai.org>
Subject: Re: [Xenomai-help] Patching latest Denx 2.4.25-devel kernel with xenomai-2.3.0 fails
Date: Wed, 24 Jan 2007 15:44:21 +0100 [thread overview]
Message-ID: <45B770C5.6000803@domain.hid> (raw)
In-Reply-To: <DD39B5C3F4963040ADC9768BE7E430CB01903C10@domain.hid>
Hi Daniel,
Daniel Schnell wrote:
> Hi,
>
> I want to patch the latest Denx 2.4.25 kernel with Xenomai-2.3.0
>
> The prepare-kernel.sh skript fails with the following message:
>
> [root@domain.hid xenomai-2.3.0]# scripts/prepare-kernel.sh --arch=ppc
> --adeos=ksrc/arch/powerpc/patches/adeos-ipipe-2.4.25-ppc-CVS-20060707-1.
> 2-01.patch --linux=../linuxppc_2_4_devel-git-xenomai-2.3.0
> patching file arch/ppc/config.in
> Hunk #1 succeeded at 858 (offset 40 lines).
> patching file arch/ppc/kernel/Makefile
> patching file arch/ppc/kernel/entry.S
> patching file arch/ppc/kernel/head.S
> patching file arch/ppc/kernel/head_440.S
> patching file arch/ppc/kernel/head_44x.S
> patching file arch/ppc/kernel/head_4xx.S
> patching file arch/ppc/kernel/head_8xx.S
> patching file arch/ppc/kernel/head_e500.S
> patching file arch/ppc/kernel/idle.c
> patching file arch/ppc/kernel/ipipe-core.c
> patching file arch/ppc/kernel/ipipe-root.c
> patching file arch/ppc/kernel/irq.c
> patching file arch/ppc/kernel/ppc_ksyms.c
> patching file arch/ppc/kernel/traps.c
> patching file arch/ppc/mm/fault.c
> patching file include/asm-ppc/hw_irq.h
> patching file include/asm-ppc/ipipe.h
> patching file include/asm-ppc/mmu_context.h
> patching file include/asm-ppc/system.h
> patching file include/linux/ipipe.h
> patching file include/linux/sched.h
> Hunk #3 succeeded at 424 with fuzz 1.
> patching file init/main.c
> Hunk #1 succeeded at 412 (offset 3 lines).
> patching file kernel/Makefile
> patching file kernel/exit.c
> patching file kernel/fork.c
> patching file kernel/ipipe/Makefile
> patching file kernel/ipipe/core.c
> patching file kernel/ipipe/generic.c
> patching file kernel/printk.c
> patching file kernel/sched.c
> patching file kernel/signal.c
> ?
>
>
> Then the script unexpectedly exits without error (but a ?).
>
>
> Any hints appreciated.
I unable to reproduce your problem with a fresh linuxppc_2_4_devel tree
and xenomai-2.3.0. Could you please use the "--verbose" option with
prepare_kernel.sh and post the result.
Wolfgang.
next prev parent reply other threads:[~2007-01-24 14:44 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-23 20:48 [Xenomai-help] isolating unwanted mode switch Jeff Weber
2007-01-23 21:45 ` Dmitry Adamushko
2007-01-23 22:27 ` Jeff Weber
2007-01-24 10:08 ` Dmitry Adamushko
2007-01-24 11:22 ` [Xenomai-help] Patching latest Denx 2.4.25-devel kernel with xenomai-2.3.0 fails Daniel Schnell
2007-01-24 14:44 ` Wolfgang Grandegger [this message]
2007-01-24 17:04 ` Daniel Schnell
2007-01-24 21:33 ` Wolfgang Grandegger
2007-01-25 7:14 ` Wolfgang Grandegger
2007-01-25 9:03 ` Daniel Schnell
2007-01-25 9:38 ` Wolfgang Grandegger
2007-01-29 15:36 ` Philippe Gerum
2007-01-24 17:52 ` [Xenomai-help] isolating unwanted mode switch Jeff Weber
2007-01-24 18:55 ` Eric Noulard
2007-01-25 7:30 ` M. Koehrer
2007-01-25 8:24 ` Eric Noulard
2007-01-25 10:50 ` Philippe Gerum
2007-01-25 17:04 ` Jeff Weber
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=45B770C5.6000803@domain.hid \
--to=wg@domain.hid \
--cc=daniel.schnell@domain.hid \
--cc=xenomai@xenomai.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.