All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@domain.hid>
To: Philippe Gerum <rpm@xenomai.org>
Cc: xenomai@xenomai.org
Subject: Re: [Xenomai-help] help with xenomai-2.5.0 on pure64bit linux x86_64
Date: Sun, 31 Jan 2010 14:25:46 +0100	[thread overview]
Message-ID: <4B6584DA.2010707@domain.hid> (raw)
In-Reply-To: <1264944150.16492.72.camel@domain.hid>

[-- Attachment #1: Type: text/plain, Size: 6151 bytes --]

Philippe Gerum wrote:
> On Sun, 2010-01-31 at 13:37 +0100, Jan Kiszka wrote:
>> lux-integ wrote:
>>> Greetings
>>>
>>>  I am new to xenomai and I am attempting to   install    a RT-kernel on a pure 
>>> 64-bit  (not multilib) amd64 linux setup.  The machine has a Sempron CPU and 
>>> 2 GBytes of RAM.  The distribution is cross-lfs  compiled from sources.  This 
>>> is what I have done:-
>>>
>>> a) I   fetched fresh kernel2.6.32.2  source-code   and placed it 
>>> in /usr/src/linux like so:-
>>> `linux' -> `linux-2.6.32.2'
>>>
>>> b) ..I then  applied  the  xenomai patch as such:-
>>> $SOURCES/xenomai-2.5.0/scripts/prepare-kernel.sh --linux=/usr/src/linux  --adeos=$SOURCES/xenomai-2.5.0/ksrc/arch/x86/patches/adeos-ipipe-2.6.32.2-x86-2.5-00.patch  --arch=x86_64
>>>
>>> patching file arch/x86/Kconfig
>>> patching file arch/x86/include/asm/apic.h
>>> patching file arch/x86/include/asm/apicdef.h
>>> patching file arch/x86/include/asm/entry_arch.h
>>> patching file arch/x86/include/asm/hw_irq.h
>>> patching file arch/x86/include/asm/i387.h
>>> patching file arch/x86/include/asm/i8259.h
>>> patching file arch/x86/include/asm/ipi.h
>>> patching file arch/x86/include/asm/ipipe.h
>>> patching file arch/x86/include/asm/ipipe_32.h
>>> patching file arch/x86/include/asm/ipipe_64.h
>>> patching file arch/x86/include/asm/ipipe_base.h
>>> patching file arch/x86/include/asm/irq_vectors.h
>>> patching file arch/x86/include/asm/irqflags.h
>>> patching file arch/x86/include/asm/mmu_context.h
>>> patching file arch/x86/include/asm/nmi.h
>>> patching file arch/x86/include/asm/processor.h
>>> patching file arch/x86/include/asm/system.h
>>> patching file arch/x86/include/asm/traps.h
>>> patching file arch/x86/kernel/Makefile
>>> patching file arch/x86/kernel/apic/apic.c
>>> patching file arch/x86/kernel/apic/apic_flat_64.c
>>> patching file arch/x86/kernel/apic/io_apic.c
>>> patching file arch/x86/kernel/apic/ipi.c
>>> patching file arch/x86/kernel/apic/nmi.c
>>> patching file arch/x86/kernel/apic/x2apic_cluster.c
>>> patching file arch/x86/kernel/apic/x2apic_phys.c
>>> patching file arch/x86/kernel/cpu/mtrr/cyrix.c
>>> patching file arch/x86/kernel/cpu/mtrr/generic.c
>>> patching file arch/x86/kernel/dumpstack.c
>>> patching file arch/x86/kernel/dumpstack_32.c
>>> patching file arch/x86/kernel/dumpstack_64.c
>>> patching file arch/x86/kernel/entry_32.S
>>> patching file arch/x86/kernel/entry_64.S
>>> patching file arch/x86/kernel/i8253.c
>>> patching file arch/x86/kernel/i8259.c
>>> patching file arch/x86/kernel/ipipe.c
>>> patching file arch/x86/kernel/irq.c
>>> patching file arch/x86/kernel/irqinit.c
>>> patching file arch/x86/kernel/process.c
>>> patching file arch/x86/kernel/process_32.c
>>> patching file arch/x86/kernel/process_64.c
>>> patching file arch/x86/kernel/smp.c
>>> patching file arch/x86/kernel/smpboot.c
>>> patching file arch/x86/kernel/time.c
>>> patching file arch/x86/kernel/traps.c
>>> patching file arch/x86/kernel/vm86_32.c
>>> patching file arch/x86/lib/mmx_32.c
>>> patching file arch/x86/lib/thunk_64.S
>>> patching file arch/x86/mm/fault.c
>>> patching file arch/x86/mm/tlb.c
>>> patching file drivers/pci/htirq.c
>>> patching file drivers/serial/8250.c
>>> patching file fs/exec.c
>>> patching file include/asm-generic/atomic.h
>>> patching file include/asm-generic/bitops/atomic.h
>>> patching file include/asm-generic/cmpxchg-local.h
>>> patching file include/asm-generic/percpu.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_lock.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/preempt.h
>>> patching file include/linux/sched.h
>>> patching file include/linux/spinlock.h
>>> patching file include/linux/spinlock_api_smp.h
>>> patching file init/Kconfig
>>> patching file init/main.c
>>> patching file kernel/Makefile
>>> patching file kernel/exit.c
>>> patching file kernel/fork.c
>>> 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/lockdep.c
>>> patching file kernel/panic.c
>>> patching file kernel/power/hibernate.c
>>> patching file kernel/printk.c
>>> patching file kernel/sched.c
>>> patching file kernel/signal.c
>>> patching file kernel/spinlock.c
>>> patching file kernel/time/tick-common.c
>>> patching file kernel/time/tick-sched.c
>>> patching file kernel/timer.c
>>> patching file kernel/trace/ftrace.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 mm/memory.c
>>> patching file mm/mmu_context.c
>>> patching file mm/vmalloc.c
>>>
>>> c) I configured the kernel using make menuconfig  disabling smp support  (here 
>>> is the relevent section of my kernel configuration):-
>>> # CONFIG_X86_DS is not set
>>> CONFIG_HPET_TIMER=y
>>> CONFIG_HPET_EMULATE_RTC=y
>>> CONFIG_DMI=y
>>> CONFIG_GART_IOMMU=y
>>> CONFIG_CALGARY_IOMMU=y
>>> CONFIG_CALGARY_IOMMU_ENABLED_BY_DEFAULT=y
>>> CONFIG_AMD_IOMMU=y
>>> CONFIG_AMD_IOMMU_STATS=y
>>> CONFIG_SWIOTLB=y
>>> CONFIG_IOMMU_HELPER=y
>>> CONFIG_IOMMU_API=y
>>> CONFIG_NR_CPUS=1
>>>
>> Please provide your full .config so that we can reproduce this build error.
>>
> 
> This is likely our old friend CONFIG_SPARSE_IRQ which is at work. Just
> disable this, until we have introduced the required changes to support
> more than 1024 IRQs.

If that is true, then please include a simple "depends on !CONFIG_IPIPE"
in the x86 patch for the meantime.

Jan


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 257 bytes --]

  reply	other threads:[~2010-01-31 13:25 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-29 21:04 [Xenomai-help] help with xenomai-2.5.0 on pure64bit linux x86_64 lux-integ
2010-01-31 10:25 ` Gilles Chanteperdrix
2010-01-31 12:37 ` Jan Kiszka
2010-01-31 13:22   ` Philippe Gerum
2010-01-31 13:25     ` Jan Kiszka [this message]
2010-01-31 13:35       ` Philippe Gerum
2010-01-31 13:42         ` Jan Kiszka
2010-01-31 14:01           ` Philippe Gerum
2010-02-04 10:46           ` Philippe Gerum
2010-02-11 17:15             ` Wolfgang Mauerer
2010-02-11 22:55               ` Philippe Gerum
2010-02-12  8:50                 ` Wolfgang Mauerer
2010-02-12  9:48               ` Jan Kiszka
2010-02-17 11:40               ` lux-integ
2010-02-17 13:19                 ` Philippe Gerum
2010-01-31 14:26     ` lux-integ

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=4B6584DA.2010707@domain.hid \
    --to=jan.kiszka@domain.hid \
    --cc=rpm@xenomai.org \
    --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.