From: Shifu Xu <xusf@aps.anl.gov>
To: linux-kernel@vger.kernel.org
Subject: patch-2.6.13-rt12 problem on Powerpc board
Date: Fri, 16 Sep 2005 18:03:50 -0500 [thread overview]
Message-ID: <432B4F56.6070404@aps.anl.gov> (raw)
Hi,
I tried the patch-2.6.13-rt12 on mvme2100 board, I made the following
changes to get it pass compiling:
(no CONFIG_HIGH_RES_TIMER)
1) mv include/asm-ppc/hrtime.h include/asm-ppc/hrtimer.h
2) in arch/ppc/syslib/todc_time.c, add :
unsigned long cpu_khz;
3)in include/linux/time.h, add :
+#ifndef div_long_long_rem
+#define div_long_long_rem(dividend,divisor,remainder) \
+({ \
+ u64 result = dividend; \
+ *remainder = do_div(result,divisor); \
+ result; \
+})
+#endif
+
When booting, it stoped after displaying:
...
openpic :enter
I remove two printk statement after the output "openpic :enter" in
arch/ppc/syslib/open_pic.c.
and then boot and display the following:
....
....
Linux version 2.6.13-rt12 () (gcc version 3.4.2) #2 Thu Sep 15 16:34:48
CDT 2005
Platform: Motorola MVME2100
Real-Time Preemption Support (C) 2004-2005 Ingo Molnar
Built 1 zonelists
Kernel command line: console=ttyS0,9600 ip=dhcp
WARNING: experimental RCU implementation.
PID hash table entries: 256 (order: 8, 4096 bytes)
Registered KTimer base Monotonic
Registered KTimer base Realtime
time_init: decrementer frequency = 16.666734 MHz
Dentry cache hash table entries: 8192 (order: 3, 32768 bytes)
Inode-cache hash table entries: 4096 (order: 2, 16384 bytes)
Memory: 30316k available (1412k kernel code, 392k data, 328k init, 0k
highmem)
Mount-cache hash table entries: 512
NET: Registered protocol family 16
PCI: Probing PCI hardware
lpptest: irq 7 in use. Unload parport module!
Generic RTC Driver v1.07
Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing disabled
ttyS0 at MMIO 0x0 (irq = 29) is a 16550A
io scheduler noop registered
io scheduler anticipatory registered
io scheduler deadline registered
io scheduler cfq registered
Linux Tulip driver version 1.1.13 (May 11, 2002)
tulip0: EEPROM default media type Autosense.
tulip0: Index #0 - Media MII (#11) described by a 21142 MII PHY (3) block.
tulip0: MII transceiver #8 config 1000 status 7809 advertising 01e1.
eth0: Digital DS21143 Tulip rev 65 at febfef80, 00:01:AF:09:0D:EA, IRQ 17.
NET: Registered protocol family 2
IP route cache hash table entries: 512 (order: -1, 2048 bytes)
TCP established hash table entries: 2048 (order: 4, 81920 bytes)
TCP bind hash table entries: 2048 (order: 4, 65536 bytes)
TCP: Hash tables configured (established 2048 bind 2048)
TCP reno registered
TCP bic registered
NET: Registered protocol family 1
NET: Registered protocol family 17
Sending DHCP requests .<6>eth0: Setting half-duplex based on MII#8 link
partner capability of 0021.
..... timed out!
IP-Config: Retrying forever (NFS root)...
Sending DHCP requests .<6>eth0: Setting half-duplex based on MII#8 link
partner capability of 0021.
..... timed out!
IP-Config: Retrying forever (NFS root)...
Sending DHCP requests .<6>eth0: Setting half-duplex based on MII#8 link
partner capability of 0021.
...
What else have to be changed to make it booting? By the way, Linux2.6.13
can boot when not applying the
patch-2.6.13-rt12.
please cc any answer/comments to my email.
thanks in advance for any help.
Shifu
reply other threads:[~2005-09-16 23:03 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=432B4F56.6070404@aps.anl.gov \
--to=xusf@aps.anl.gov \
--cc=linux-kernel@vger.kernel.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