From: Philippe De Muyter <phdm@macqel.be>
To: linuxppc-dev@ozlabs.org
Subject: ARCH=ppc -> ARCH=powerpc : help needed for dts file
Date: Mon, 3 Mar 2008 15:47:27 +0100 [thread overview]
Message-ID: <20080303144727.GA27949@ingate.macqel> (raw)
Hi all,
I have a currently almost working ARCH=ppc linux-2.6.24 configuration for a
new mpc8540 board (except for a RTC chip connected to an i2c bus).
Knowing that ARCH=ppc will be removed, I try to make the ARCH=powerpc version
work, but that's not easy.
I have copied the mpc8540ads.dts file to a new dts file, and added the
following :
i2c@3000 {
+ #address-cells = <1>;
+ #size-cells = <0>;
device_type = "i2c";
compatible = "fsl-i2c";
reg = <3000 100>;
interrupts = <2b 2>;
interrupt-parent = <&mpic>;
dfsrr;
+
+ rtc@68 {
+ compatible = "stm,m41t81";
+ reg = <68>;
+ };
};
and I see in the boot log that my RTC chip is now working.
My root device is on a compact-flash connected to a PCI yenta chip from TI,
and this one is not working, altough it seems to be discovered :
Yenta: CardBus bridge found at 0000:00:12.0 [0000:0000]
Yenta: Using CSCINT to route CSC interrupts to PCI
Yenta: Routing CardBus interrupts to PCI
Yenta TI: socket 0000:00:12.0, mfunc 0x00001b22, devctl 0x64
irq 18: nobody cared (try booting with the "irqpoll" option)
Call Trace:
[cf813af0] [c00066c8] show_stack+0x3c/0x1bc (unreliable)
[cf813b30] [c003c1ac] __report_bad_irq+0x38/0xcc
[cf813b50] [c003c4c8] note_interrupt+0x288/0x2cc
[cf813b80] [c003cc34] handle_fasteoi_irq+0x94/0xf8
but my boot finally fails with :
VFS: Cannot open root device "hda1" or unknown-block(0,0)
Please append a correct "root=" boot option; here are the
available partitions:
1f00 8192 mtdblock0 (driver?)
Kernel panic - not syncing: VFS: Unable to mount root fs
on unknown-block(0,0)
Is there an easy way to use values found in /proc or even in the sources
in my working ppc setup to put them in the dts file to make my new powerpc
configuration work ?
Thanks for listening
Philippe
next reply other threads:[~2008-03-03 14:47 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-03 14:47 Philippe De Muyter [this message]
2008-03-03 14:54 ` ARCH=ppc -> ARCH=powerpc : help needed for dts file Grant Likely
2008-03-03 17:07 ` Scott Wood
2008-03-03 21:05 ` Philippe De Muyter
2008-03-03 21:11 ` Scott Wood
2008-03-03 21:26 ` Philippe De Muyter
2008-03-03 21:41 ` Benjamin Herrenschmidt
2008-03-04 8:19 ` Philippe De Muyter
2008-03-03 21:55 ` Scott Wood
2008-03-04 8:08 ` Philippe De Muyter
2008-03-04 8:22 ` Benjamin Herrenschmidt
2008-03-04 9:10 ` Philippe De Muyter
2008-03-05 4:52 ` David Gibson
2008-03-05 5:01 ` Benjamin Herrenschmidt
2008-03-05 16:15 ` Philippe De Muyter
2008-03-05 20:14 ` Benjamin Herrenschmidt
2008-03-05 23:34 ` Philippe De Muyter
2008-03-05 16:32 ` Scott Wood
2008-03-05 23:46 ` Benjamin Herrenschmidt
2008-03-07 0:10 ` Philippe De Muyter
2008-03-07 0:19 ` Benjamin Herrenschmidt
2008-03-09 22:31 ` Philippe De Muyter
2008-03-09 22:36 ` Benjamin Herrenschmidt
2008-03-11 0:32 ` David Gibson
2008-03-11 11:46 ` Philippe De Muyter
2008-03-11 22:42 ` David Gibson
2008-05-06 22:54 ` Andy Fleming
2008-05-07 7:50 ` Philippe De Muyter
2008-05-07 7:54 ` Stephen Rothwell
2008-03-03 21:26 ` Benjamin Herrenschmidt
2008-03-04 8:34 ` Philippe De Muyter
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=20080303144727.GA27949@ingate.macqel \
--to=phdm@macqel.be \
--cc=linuxppc-dev@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).