From: Joachim Meyer <Jogi95@domain.hid>
To: xenomai@xenomai.org
Subject: [Xenomai-help] Compiling Problems for Virtex II pro Board
Date: Mon, 25 Feb 2008 21:38:47 +0100 [thread overview]
Message-ID: <608371653@domain.hid> (raw)
HI
I tried to patch my Kernel 2.6.23 with the aedos patch. But I got the error listet at the end. I was using a Kernel from the Xilinx git tree because there are all the driver included I need. Next I tried to use a the last 2.6.23 Kernel from DENX, which succeded and they also support the ml300 Board but the support for the Xilinx on-chip ethernet is missing. I need that support. So what can I do? The Xenomai patch doesn't only work with the DENX Kernels, right? But where can I look for the error?
Greetings & Thx for all help
Joachim
error:
-------------------------------------------------------------------------------------------------------------------------------------------
meyer@domain.hid> ./prepare-kernel.sh
Linux tree [default /lib/modules/2.6.13-15.18-bigsmp/source]: ~/xenomai/test/linux-2.6-xlnx.git
prepare-kernel.sh: cannot access Linux tree in ~/xenomai/test/linux-2.6-xlnx.git
Linux tree [default /usr/src]: /home/meyer/xenomai/test/linux-2.6-xlnx.git
Target architecture [default i686]: ppc
Adeos patch [default /home/meyer/xenomai/xenomai-2.4.2/ksrc/arch/powerpc/patches/adeos-ipipe-2.6.23-ppc-DENX-1.6-03.patch]:
patching file Makefile
patching file arch/powerpc/kernel/cputable.c
Hunk #1 succeeded at 1298 (offset -89 lines).
Hunk #2 succeeded at 1327 (offset -89 lines).
patching file arch/powerpc/kernel/idle.c
patching file arch/powerpc/kernel/io.c
patching file arch/powerpc/kernel/irq.c
patching file arch/powerpc/kernel/process.c
Hunk #2 succeeded at 333 with fuzz 2 (offset -11 lines).
Hunk #3 succeeded at 973 (offset -11 lines).
patching file arch/ppc/Kconfig
Hunk #1 succeeded at 980 (offset -32 lines).
patching file arch/ppc/boot/Makefile
patching file arch/ppc/kernel/Makefile
patching file arch/ppc/kernel/entry.S
Hunk #5 FAILED at 726.
1 out of 6 hunks FAILED -- saving rejects to file arch/ppc/kernel/entry.S.rej
patching file arch/ppc/kernel/head.S
patching file arch/ppc/kernel/head_44x.S
Hunk #1 succeeded at 426 (offset -1 lines).
patching file arch/ppc/kernel/head_4xx.S
patching file arch/ppc/kernel/head_8xx.S
patching file arch/ppc/kernel/head_booke.h
Hunk #1 succeeded at 187 (offset -4 lines).
Hunk #2 succeeded at 351 (offset -4 lines).
Hunk #3 succeeded at 367 (offset -4 lines).
patching file arch/ppc/kernel/head_fsl_booke.S
patching file arch/ppc/kernel/ipipe.c
patching file arch/ppc/kernel/mcount_32.S
patching file arch/ppc/kernel/setup.c
patching file arch/ppc/kernel/time.c
patching file arch/ppc/kernel/traps.c
patching file arch/ppc/mm/fault.c
patching file arch/ppc/syslib/cpm2_pic.c
patching file arch/ppc/syslib/ipic.c
patching file arch/ppc/syslib/open_pic.c
patching file arch/ppc/syslib/ppc4xx_pic.c
Hunk #3 succeeded at 292 (offset -30 lines).
patching file drivers/pci/htirq.c
patching file include/asm-powerpc/hw_irq.h
patching file include/asm-powerpc/time.h
patching file include/asm-ppc/ipipe.h
patching file include/asm-ppc/ipipe_base.h
patching file include/asm-ppc/mmu_context.h
patching file include/linux/clockchips.h
patching file include/linux/hardirq.h
patching file include/linux/ipipe.h
patching file include/linux/ipipe_base.h
patching file include/linux/ipipe_compat.h
patching file include/linux/ipipe_percpu.h
patching file include/linux/ipipe_tickdev.h
patching file include/linux/ipipe_trace.h
patching file include/linux/irq.h
patching file include/linux/kernel.h
patching file include/linux/linkage.h
patching file include/linux/mm.h
patching file include/linux/preempt.h
patching file include/linux/sched.h
Hunk #3 succeeded at 1192 (offset -5 lines).
Hunk #4 succeeded at 1345 (offset -5 lines).
patching file include/linux/spinlock.h
patching file include/linux/spinlock_types.h
patching file init/Kconfig
patching file init/main.c
Hunk #1 succeeded at 524 (offset -1 lines).
Hunk #2 succeeded at 577 (offset -4 lines).
Hunk #3 succeeded at 742 (offset -4 lines).
patching file kernel/Makefile
patching file kernel/exit.c
patching file kernel/fork.c
Hunk #1 succeeded at 392 (offset -20 lines).
Hunk #2 succeeded at 926 (offset -20 lines).
Hunk #3 succeeded at 1275 (offset -22 lines).
patching file kernel/ipipe/Kconfig
patching file kernel/ipipe/Kconfig.debug
patching file kernel/ipipe/Makefile
patching file kernel/ipipe/core.c
patching file kernel/ipipe/tracer.c
patching file kernel/irq/chip.c
patching file kernel/irq/handle.c
patching file kernel/power/swsusp.c
patching file kernel/printk.c
Hunk #1 succeeded at 504 (offset -92 lines).
Hunk #2 succeeded at 591 (offset -92 lines).
patching file kernel/sched.c
patching file kernel/signal.c
patching file kernel/spinlock.c
patching file kernel/time/clockevents.c
patching file lib/Kconfig.debug
patching file lib/bust_spinlocks.c
patching file lib/ioremap.c
patching file lib/smp_processor_id.c
patching file lib/spinlock_debug.c
patching file mm/memory.c
patching file mm/mlock.c
patching file mm/vmalloc.c
prepare-kernel.sh: Unable to patch kernel 2.6.23xlnx with adeos-ipipe-2.6.23-ppc-DENX-1.6-03.patch.
meyer@domain.hid>
-------------------------------------------------------------------------------------------------------------------------------------------
_______________________________________________________________________
Jetzt neu! Schützen Sie Ihren PC mit McAfee und WEB.DE. 30 Tage
kostenlos testen. http://www.pc-sicherheit.web.de/startseite/?mc=022220
next reply other threads:[~2008-02-25 20:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-25 20:38 Joachim Meyer [this message]
2008-02-25 22:15 ` [Xenomai-help] Compiling Problems for Virtex II pro Board Philippe Gerum
-- strict thread matches above, loose matches on Subject: below --
2008-02-26 10:33 Joachim Meyer
2008-02-26 16:51 Joachim Meyer
2008-02-26 18:05 ` Philippe Gerum
2008-02-26 22:05 Joachim Meyer
2008-08-28 14:32 Joachim Meyer
2008-08-29 7:36 ` Philippe Gerum
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=608371653@domain.hid \
--to=jogi95@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.