From: "rakesh bk" <rakeshbk402@gmail.com>
To: linuxppc-embedded@ozlabs.org
Subject: porting xenomaii for power pc 750Cxe based SBC
Date: Thu, 7 Feb 2008 17:41:45 +0530 [thread overview]
Message-ID: <43455a600802070411w42b6745aqf87fa3ae88dcaf8c@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2737 bytes --]
Hello Everyone,
Iam Trying to port the xenomai-2.2.0 using the "
adeos-ipipe-2.6.14-ppc-1.3-05.patch" to linux-kernel 2.6.14( Vanilla) to
our custom based SBC, After applying patches as i get Enough printk's on my
console , I get Stucked after UNMASKING of Ethernet Irq The following are
the printk messages after i tried to boot the image. can i know what the
actual problem is ...........
These are the following printks, which i get ,
ATSLinux:eth0:none console=ttyS0,9600 ip1=off
Initializing init_irq
PID hash table entries: 1024 (order: 10, 16384 bytes)
time_init: decrementer frequency = 17.000000 MHz
Warning: real time clock seems stuck!
I-pipe 1.3-05: pipeline enabled.
Console: colour dummy device 80x25
Dentry cache hash table entries: 32768 (order: 5, 131072 bytes)
Inode-cache hash table entries: 16384 (order: 4, 65536 bytes)
Memory: 125440k available (2716k kernel code, 1200k data, 148k init, 0k
highmem)
Mount-cache hash table entries: 512
softlockup thread 0 started up.
NET: Registered protocol family 16
PCI: Probing PCI hardware
Xenomai: ALTIVEC support enabled in kernel but no hardware found.
Disable CONFIG_ALTIVEC in the kernel configuration.
Xenomai: system init failed, code -19.
Xenomai: native skin init failed, code -19.
Xenomai: starting POSIX services.
Xenomai: POSIX skin init failed, code -19.
Xenomai: RTDM skin init failed, code -19.
Installing knfsd (copyright (C) 1996 okir@monad.swb.de).
JFFS2 version 2.2. (NAND) (C) 2001-2003 Red Hat, Inc.
Initializing Cryptographic API
Generic RTC Driver v1.07
Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing disabled
ttyS0 at MMIO 0x0 (irq = 85) is a 16550A
ttyS1 at MMIO 0x0 (irq = 86) is a 16550A
io scheduler noop registered
io scheduler anticipatory registered
io scheduler deadline registered
io scheduler cfq registered
loop: loaded (max 8 devices)
eth%d: Couldn't Read Srom MAC address
Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
physmap flash device: 10000 at f6000000
Generic platform RAM MTD, (c) 2004 Simtec Electronics
mice: PS/2 mouse device common for all mice
NET: Registered protocol family 2
IP route cache hash table entries: 2048 (order: 1, 8192 bytes)
TCP established hash table entries: 8192 (order: 3, 32768 bytes)
TCP bind hash table entries: 8192 (order: 3, 32768 bytes)
TCP: Hash tables configured (established 8192 bind 8192)
TCP reno registered
TCP bic registered
NET: Registered protocol family 1
NET: Registered protocol family 17
Entering The Ethernet device : <NULL>
UNMasking of Eth interrupt ( After generating the interrupt ).
Retval of irq32 is : 0
gt64260_eth_open : Assigned IRQ 32 to gt64260_eth0
[-- Attachment #2: Type: text/html, Size: 3057 bytes --]
next reply other threads:[~2008-02-07 12:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-07 12:11 rakesh bk [this message]
2008-02-09 16:11 ` porting xenomaii for power pc 750Cxe based SBC Wolfgang Grandegger
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=43455a600802070411w42b6745aqf87fa3ae88dcaf8c@mail.gmail.com \
--to=rakeshbk402@gmail.com \
--cc=linuxppc-embedded@ozlabs.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).