Is there anyone having sample pci circuit for outputting data and display it in the form of leds.<br><br>thank you and regards<br>babu<br><br><div><span class="gmail_quote">On 9/13/07, <b class="gmail_sendername"><a href="mailto:linuxppc-dev-request@ozlabs.org">
linuxppc-dev-request@ozlabs.org</a></b> <<a href="mailto:linuxppc-dev-request@ozlabs.org">linuxppc-dev-request@ozlabs.org</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Send Linuxppc-dev mailing list submissions to<br> <a href="mailto:linuxppc-dev@ozlabs.org">linuxppc-dev@ozlabs.org</a><br><br>To subscribe or unsubscribe via the World Wide Web, visit<br> <a href="https://ozlabs.org/mailman/listinfo/linuxppc-dev">
https://ozlabs.org/mailman/listinfo/linuxppc-dev</a><br>or, via email, send a message with subject or body 'help' to<br> <a href="mailto:linuxppc-dev-request@ozlabs.org">linuxppc-dev-request@ozlabs.org</a><br>
<br>You can reach the person managing the list at<br> <a href="mailto:linuxppc-dev-owner@ozlabs.org">linuxppc-dev-owner@ozlabs.org</a><br><br>When replying, please edit your Subject line so it is more specific<br>than "Re: Contents of Linuxppc-dev digest..."
<br><br><br>Today's Topics:<br><br> 1. Re: Linuxppc-dev Digest, Vol 37, Issue 84 (lakshminarayana babu)<br> 2. Re: 2.6.23-rc3 boot hang on MPC8641D (sivaji)<br> 3. Re: 2.6.23-rc3 boot hang on MPC8641D (David Gibson)
<br> 4. RE: 2.6.23-rc3 boot hang on MPC8641D (sivaji)<br> 5. Re: Linuxppc-dev Digest, Vol 37, Issue 84 (Kumar Gala)<br> 6. Re: 2.6.23-rc3 boot hang on MPC8641D (Michael Ellerman)<br> 7. Make mpc82xx use generic_calibrate_decr() (David Gibson)
<br> 8. Re: [PATCH 10/10] mpc82xx: Add pq2fads board support. (Kumar Gala)<br><br><br>----------------------------------------------------------------------<br><br>Message: 1<br>Date: Thu, 13 Sep 2007 10:53:57 +0530<br>
From: "lakshminarayana babu" <<a href="mailto:babu.pci81@gmail.com">babu.pci81@gmail.com</a>><br>Subject: Re: Linuxppc-dev Digest, Vol 37, Issue 84<br>To: "Olof Johansson" <<a href="mailto:olof@lixom.net">
olof@lixom.net</a>><br>Cc: <a href="mailto:linuxppc-dev@ozlabs.org">linuxppc-dev@ozlabs.org</a><br>Message-ID:<br> <<a href="mailto:a38e30640709122223m60913ad5xf3c95e636e3b3350@mail.gmail.com">a38e30640709122223m60913ad5xf3c95e636e3b3350@mail.gmail.com
</a>><br>Content-Type: text/plain; charset="iso-8859-1"<br><br>sir,<br> can you plese suggest any book for pci driver writing...At present i am<br>studying linux device drivers by alexandrorubini<br><br>On 9/13/07, Olof Johansson <
<a href="mailto:olof@lixom.net">olof@lixom.net</a>> wrote:<br>><br>> On Thu, Sep 13, 2007 at 10:01:36AM +0530, lakshminarayana babu wrote:<br>> > i am new to the linux.....can you tell me how to access the pci
<br>> > configuration space using ioremap function...but it is implicit<br>> function<br>> > declaration...<br>><br>> That is architecture and platform dependent. Some platforms don't even<br>> have a memory-mappable interface to configuration space.
<br>><br>> Instead, please use the abstracted config access functions that the<br>> kernel provides. (pci_read_config_word and friends).<br>><br>><br>> -Olof<br>><br>-------------- next part --------------
<br>An HTML attachment was scrubbed...<br>URL: <a href="http://ozlabs.org/pipermail/linuxppc-dev/attachments/20070913/2aa5ccff/attachment-0001.htm">http://ozlabs.org/pipermail/linuxppc-dev/attachments/20070913/2aa5ccff/attachment-0001.htm
</a><br><br>------------------------------<br><br>Message: 2<br>Date: Wed, 12 Sep 2007 22:24:22 -0700 (PDT)<br>From: sivaji <<a href="mailto:rameshmrm@gmail.com">rameshmrm@gmail.com</a>><br>Subject: Re: 2.6.23-rc3 boot hang on MPC8641D
<br>To: <a href="mailto:linuxppc-dev@ozlabs.org">linuxppc-dev@ozlabs.org</a><br>Message-ID: <<a href="mailto:12648913.post@talk.nabble.com">12648913.post@talk.nabble.com</a>><br>Content-Type: text/plain; charset=us-ascii
<br><br><br><br>Hi,<br> I am not willing to upgrade the uboot. Becuase it takes some time to<br>port the new uboot for my custom boad.<br>whether the current problem is related to uboot ? One more point, previously
<br>i tried 2.6.21 with the same uboot(1.1.6) we got linux prompt but we face<br>some issue in the pci express in that version. so we plan to upgrade the<br>kernel version.<br>by<br>Sivaji<br><br>Kumar Gala-3 wrote:<br>>
<br>><br>> On Sep 12, 2007, at 11:52 PM, sivaji wrote:<br>><br>>><br>>><br>>> Hi,<br>>> I tired to move the dtb to 0x2000000, but the result was<br>>> same.<br>>> uboot version is
1.1.6<br>><br>> seems like a pretty old u-boot. Willing to try a 1.3.0-rc1?<br>><br>> - k<br>> _______________________________________________<br>> Linuxppc-dev mailing list<br>> <a href="mailto:Linuxppc-dev@ozlabs.org">
Linuxppc-dev@ozlabs.org</a><br>> <a href="https://ozlabs.org/mailman/listinfo/linuxppc-dev">https://ozlabs.org/mailman/listinfo/linuxppc-dev</a><br>><br>><br><br>--<br>View this message in context: <a href="http://www.nabble.com/2.6.23-rc3-boot-hang-on-MPC8641D-tf4433508.html#a12648913">
http://www.nabble.com/2.6.23-rc3-boot-hang-on-MPC8641D-tf4433508.html#a12648913</a><br>Sent from the linuxppc-dev mailing list archive at <a href="http://Nabble.com">Nabble.com</a>.<br><br><br><br>------------------------------
<br><br>Message: 3<br>Date: Thu, 13 Sep 2007 15:29:32 +1000<br>From: David Gibson <<a href="mailto:david@gibson.dropbear.id.au">david@gibson.dropbear.id.au</a>><br>Subject: Re: 2.6.23-rc3 boot hang on MPC8641D<br>To: sivaji <
<a href="mailto:rameshmrm@gmail.com">rameshmrm@gmail.com</a>><br>Cc: <a href="mailto:linuxppc-dev@ozlabs.org">linuxppc-dev@ozlabs.org</a><br>Message-ID: <<a href="mailto:20070913052932.GF14905@localhost.localdomain">
20070913052932.GF14905@localhost.localdomain</a>><br>Content-Type: text/plain; charset=us-ascii<br><br>On Wed, Sep 12, 2007 at 10:24:22PM -0700, sivaji wrote:<br>><br>><br>> Hi,<br>> I am not willing to upgrade the uboot. Becuase it takes some time to
<br>> port the new uboot for my custom boad.<br>> whether the current problem is related to uboot ? One more point, previously<br>> i tried 2.6.21 with the same uboot(1.1.6) we got linux prompt but we face<br>> some issue in the pci express in that version. so we plan to upgrade the
<br>> kernel version.<br><br>I thought u-boot < 1.3 didn't understand the flat tree at all. In<br>which case you'll need a cuboot zImage.<br><br>--<br>David Gibson | I'll have my music baroque, and my code
<br>david AT <a href="http://gibson.dropbear.id.au">gibson.dropbear.id.au</a> | minimalist, thank you. NOT _the_ _other_<br> | _way_ _around_!<br><a href="http://www.ozlabs.org/~dgibson">http://www.ozlabs.org/~dgibson
</a><br><br><br>------------------------------<br><br>Message: 4<br>Date: Wed, 12 Sep 2007 22:32:24 -0700 (PDT)<br>From: sivaji <<a href="mailto:rameshmrm@gmail.com">rameshmrm@gmail.com</a>><br>Subject: RE: 2.6.23-rc3
boot hang on MPC8641D<br>To: <a href="mailto:linuxppc-dev@ozlabs.org">linuxppc-dev@ozlabs.org</a><br>Message-ID: <<a href="mailto:12648963.post@talk.nabble.com">12648963.post@talk.nabble.com</a>><br>Content-Type: text/plain; charset=us-ascii
<br><br><br>Hi,<br> Sorry i specify the wrong version, we r using 1.2.0. This uboot<br>was taken from the BSP which was released by Freescale. Previously we tested<br>linux 2.6.21 kernel, we got linux prompt. For this we are using the same
<br>uboot(1.2.0).<br>In that version we face some issues in the pci express, at that time kumar<br>suggest to upgrade the kernel verison 2.6.23-rc3.<br>Zhang did u suspect the problem is related to uboot?.<br>by<br>sivaji
<br><br><br>Zhang Wei-r63237 wrote:<br>><br>> Yes, It's too old. Maybe not fully supports FDT. You can try the version<br>> of Kumar said or in the BSP of Freescale released.<br>><br>> - zw<br>><br>>> -----Original Message-----
<br>>> From: linuxppc-dev-bounces+wei.zhang=<a href="mailto:freescale.com@ozlabs.org">freescale.com@ozlabs.org</a><br>>> [mailto:<a href="mailto:linuxppc-dev-bounces+wei.zhang=freescale.com@ozlabs.or">linuxppc-dev-bounces+wei.zhang=freescale.com@ozlabs.or
</a><br>>> g] On Behalf Of Kumar Gala<br>>> Sent: Thursday, September 13, 2007 1:11 PM<br>>> To: sivaji<br>>> Cc: <a href="mailto:linuxppc-dev@ozlabs.org">linuxppc-dev@ozlabs.org</a><br>>> Subject: Re:
2.6.23-rc3 boot hang on MPC8641D<br>>><br>>><br>>> On Sep 12, 2007, at 11:52 PM, sivaji wrote:<br>>><br>>> ><br>>> ><br>>> > Hi,<br>>> > I tired to move the dtb to 0x2000000, but the result was
<br>>> > same.<br>>> > uboot version is 1.1.6<br>>><br>>> seems like a pretty old u-boot. Willing to try a 1.3.0-rc1?<br>>><br>>> - k<br>>> _______________________________________________
<br>>> Linuxppc-dev mailing list<br>>> <a href="mailto:Linuxppc-dev@ozlabs.org">Linuxppc-dev@ozlabs.org</a><br>>> <a href="https://ozlabs.org/mailman/listinfo/linuxppc-dev">https://ozlabs.org/mailman/listinfo/linuxppc-dev
</a><br>>><br>> _______________________________________________<br>> Linuxppc-dev mailing list<br>> <a href="mailto:Linuxppc-dev@ozlabs.org">Linuxppc-dev@ozlabs.org</a><br>> <a href="https://ozlabs.org/mailman/listinfo/linuxppc-dev">
https://ozlabs.org/mailman/listinfo/linuxppc-dev</a><br>><br>><br><br>--<br>View this message in context: <a href="http://www.nabble.com/2.6.23-rc3-boot-hang-on-MPC8641D-tf4433508.html#a12648963">http://www.nabble.com/2.6.23-rc3-boot-hang-on-MPC8641D-tf4433508.html#a12648963
</a><br>Sent from the linuxppc-dev mailing list archive at <a href="http://Nabble.com">Nabble.com</a>.<br><br><br><br>------------------------------<br><br>Message: 5<br>Date: Thu, 13 Sep 2007 00:58:18 -0500<br>From: Kumar Gala <
<a href="mailto:galak@kernel.crashing.org">galak@kernel.crashing.org</a>><br>Subject: Re: Linuxppc-dev Digest, Vol 37, Issue 84<br>To: "lakshminarayana babu" <<a href="mailto:babu.pci81@gmail.com">babu.pci81@gmail.com
</a>><br>Cc: Olof Johansson <<a href="mailto:olof@lixom.net">olof@lixom.net</a>>, <a href="mailto:linuxppc-dev@ozlabs.org">linuxppc-dev@ozlabs.org</a><br>Message-ID: <<a href="mailto:93B3AC37-A4E7-46BD-8484-F074911A9A44@kernel.crashing.org">
93B3AC37-A4E7-46BD-8484-F074911A9A44@kernel.crashing.org</a>><br>Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed<br><br><br>On Sep 13, 2007, at 12:23 AM, lakshminarayana babu wrote:<br><br>> sir,
<br>> can you plese suggest any book for pci driver writing...At<br>> present i am studying linux device drivers by alexandrorubini<br><br>That's about as good as it gets. It covers writing a pci driver in<br>
there.<br><br>- k<br><br><br>------------------------------<br><br>Message: 6<br>Date: Thu, 13 Sep 2007 15:59:32 +1000<br>From: Michael Ellerman <<a href="mailto:michael@ellerman.id.au">michael@ellerman.id.au</a>><br>
Subject: Re: 2.6.23-rc3 boot hang on MPC8641D<br>To: Kumar Gala <<a href="mailto:galak@kernel.crashing.org">galak@kernel.crashing.org</a>><br>Cc: <a href="mailto:linuxppc-dev@ozlabs.org">linuxppc-dev@ozlabs.org</a>, sivaji <
<a href="mailto:rameshmrm@gmail.com">rameshmrm@gmail.com</a>><br>Message-ID: <<a href="mailto:1189663172.20396.1.camel@concordia.ozlabs.ibm.com">1189663172.20396.1.camel@concordia.ozlabs.ibm.com</a>><br>Content-Type: text/plain; charset="us-ascii"
<br><br>On Thu, 2007-09-13 at 00:13 -0500, Kumar Gala wrote:<br>> On Sep 12, 2007, at 11:47 PM, sivaji wrote:<br>><br>> ><br>> ><br>> > Hi,<br>> > I have JTAG Debugger connected to the board. I was given the
<br>> > following commands in the root path of the kernel source<br>><br>> If you can dump memory w/o connecting GDB, I suggest the following.<br>><br>> Look in your kernel build for System.map and grep for log_buf you
<br>> should get something like:<br>><br>> c040b04c d log_buf<br>> c043b1a4 b __log_buf<br>><br>> then dump the memory @ these addresses. I can't remember which one<br>> is the correct one. You'll want to subtract c000_0000 from the
<br>> address to get a physical address that you can dump. This should<br>> help provide some possible insight into what's going on.<br><br>__log_buf is the actual buffer, log_buf points to the current insertion
<br>point IIRC. It should be pretty obvious that you're looking at a dmesg<br>buffer though, unless there's nothing in there for some reason.<br><br>cheers<br><br>--<br>Michael Ellerman<br>OzLabs, IBM Australia Development Lab
<br><br>wwweb: <a href="http://michael.ellerman.id.au">http://michael.ellerman.id.au</a><br>phone: +61 2 6212 1183 (tie line 70 21183)<br><br>We do not inherit the earth from our ancestors,<br>we borrow it from our children. -
S.M.A.R.T Person<br>-------------- next part --------------<br>A non-text attachment was scrubbed...<br>Name: not available<br>Type: application/pgp-signature<br>Size: 189 bytes<br>Desc: This is a digitally signed message part
<br>Url : <a href="http://ozlabs.org/pipermail/linuxppc-dev/attachments/20070913/30f05247/attachment-0001.pgp">http://ozlabs.org/pipermail/linuxppc-dev/attachments/20070913/30f05247/attachment-0001.pgp</a><br><br>------------------------------
<br><br>Message: 7<br>Date: Thu, 13 Sep 2007 16:22:01 +1000<br>From: David Gibson <<a href="mailto:david@gibson.dropbear.id.au">david@gibson.dropbear.id.au</a>><br>Subject: Make mpc82xx use generic_calibrate_decr()<br>
To: Kumar Gala <<a href="mailto:galak@kernel.crashing.org">galak@kernel.crashing.org</a>>, Tony Breeds<br> <<a href="mailto:tony@bakeyournoodle.com">tony@bakeyournoodle.com</a>>, <a href="mailto:linuxppc-dev@ozlabs.org">
linuxppc-dev@ozlabs.org</a><br>Message-ID: <<a href="mailto:20070913062201.GA24281@localhost.localdomain">20070913062201.GA24281@localhost.localdomain</a>><br>Content-Type: text/plain; charset=us-ascii<br><br>The only difference between m82xx_calibrate_decr() and
<br>generic_calibrate_decr() is that the former computes the timebase<br>frequency from the cpu node's bus-frequency property, instead of<br>directly from the timebase-frequency property.<br><br>But there's no reason the timebase-frequency shouldn't be correct on
<br>82xx like everything else. Certainly the 82xx bootwrapper in<br>arch/powerpc/boot/cuboot-pq2.c should get it right.<br><br>Therefore, this patch removes mpc82xx_calibrate_decr(), using<br>generic_calibrate_decr() instead.
<br><br>Signed-off-by: David Gibson <<a href="mailto:david@gibson.dropbear.id.au">david@gibson.dropbear.id.au</a>><br>---<br><br>I've compiled this, but no booted it, since I don't have any 82xx<br>hardware. I'm hoping for an ack from someone who can test boot it.
<br><br>Index: working-2.6/arch/powerpc/platforms/82xx/mpc82xx_ads.c<br>===================================================================<br>--- working-2.6.orig/arch/powerpc/platforms/82xx/mpc82xx_ads.c 2007-09-13 16:14:
18.000000000 +1000<br>+++ working-2.6/arch/powerpc/platforms/82xx/mpc82xx_ads.c 2007-09-13 16:14:38.000000000 +1000<br>@@ -635,6 +635,6 @@ define_machine(mpc82xx_ads)<br> .init_IRQ = mpc82xx_ads_pic_init,<br>
.show_cpuinfo = mpc82xx_ads_show_cpuinfo,<br> .get_irq = cpm2_get_irq,<br>- .calibrate_decr = m82xx_calibrate_decr,<br>+ .calibrate_decr = generic_calibrate_decr,<br> .restart = m82xx_restart,.halt = m82xx_halt,
<br> };<br>Index: working-2.6/arch/powerpc/platforms/82xx/mpc82xx.c<br>===================================================================<br>--- working-2.6.orig/arch/powerpc/platforms/82xx/mpc82xx.c 2007-09-13 16:13:
48.000000000 +1000<br>+++ working-2.6/arch/powerpc/platforms/82xx/mpc82xx.c 2007-09-13 16:15:13.000000000 +1000<br>@@ -51,42 +51,6 @@<br><br> #include "pq2ads.h"<br><br>-static int __init get_freq(char *name, unsigned long *val)
<br>-{<br>- struct device_node *cpu;<br>- const unsigned int *fp;<br>- int found = 0;<br>-<br>- /* The cpu node should have timebase and clock frequency properties */<br>- cpu = of_find_node_by_type(NULL, "cpu");
<br>-<br>- if (cpu) {<br>- fp = of_get_property(cpu, name, NULL);<br>- if (fp) {<br>- found = 1;<br>- *val = *fp;<br>- }<br>-<br>
- of_node_put(cpu);<br>- }<br>-<br>- return found;<br>-}<br>-<br>-void __init m82xx_calibrate_decr(void)<br>-{<br>- ppc_tb_freq = 125000000;<br>- if (!get_freq("bus-frequency", &ppc_tb_freq)) {
<br>- printk(KERN_ERR "WARNING: Estimating decrementer frequency "<br>- "(not found)\n");<br>- }<br>- ppc_tb_freq /= 4;<br>- ppc_proc_freq = 1000000000;
<br>- if (!get_freq("clock-frequency", &ppc_proc_freq))<br>- printk(KERN_ERR "WARNING: Estimating processor frequency"<br>- "(not found)\n");
<br>-}<br>-<br> void mpc82xx_ads_show_cpuinfo(struct seq_file *m)<br> {<br> uint pvid, svid, phid1;<br><br>--<br>David Gibson | I'll have my music baroque, and my code<br>david AT <a href="http://gibson.dropbear.id.au">
gibson.dropbear.id.au</a> | minimalist, thank you. NOT _the_ _other_<br> | _way_ _around_!<br><a href="http://www.ozlabs.org/~dgibson">http://www.ozlabs.org/~dgibson</a><br><br><br>------------------------------
<br><br>Message: 8<br>Date: Thu, 13 Sep 2007 01:39:58 -0500<br>From: Kumar Gala <<a href="mailto:galak@kernel.crashing.org">galak@kernel.crashing.org</a>><br>Subject: Re: [PATCH 10/10] mpc82xx: Add pq2fads board support.
<br>To: Scott Wood <<a href="mailto:scottwood@freescale.com">scottwood@freescale.com</a>><br>Cc: <a href="mailto:linuxppc-dev@ozlabs.org">linuxppc-dev@ozlabs.org</a><br>Message-ID: <<a href="mailto:9BC5B02A-4E9D-42DD-90C3-F8C3382F2A96@kernel.crashing.org">
9BC5B02A-4E9D-42DD-90C3-F8C3382F2A96@kernel.crashing.org</a>><br>Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed<br><br>> diff --git a/arch/powerpc/boot/dts/pq2fads.dts b/arch/powerpc/boot/<br>> dts/pq2fads.dts
<br>> new file mode 100644<br>> index 0000000..ad736f8<br>> --- /dev/null<br>> +++ b/arch/powerpc/boot/dts/pq2fads.dts<br>> @@ -0,0 +1,236 @@<br>> +/*<br>> + * Device Tree for the PQ2FADS-ZU board with an MPC8280 chip.
<br>> + *<br>> + * Copyright 2007 Freescale Semiconductor Inc.<br>> + *<br>> + * This program is free software; you can redistribute it and/or<br>> modify it<br>> + * under the terms of the GNU General Public License as
<br>> published by the<br>> + * Free Software Foundation; either version 2 of the License, or<br>> (at your<br>> + * option) any later version.<br>> + */<br>> +<br>> +/ {<br>> + model = "pq2fads";
<br>> + compatible = "fsl,pq2fads";<br>> + #address-cells = <1>;<br>> + #size-cells = <1>;<br>> +<br>> + cpus {<br>> + #address-cells = <1>;<br>> + #size-cells = <0>;
<br>> +<br>> + cpu@0 {<br>> + device_type = "cpu";<br>> + reg = <0>;<br>> + d-cache-line-size = <d#32>;<br>> + i-cache-line-size = <d#32>;
<br>> + d-cache-size = <d#16384>;<br>> + i-cache-size = <d#16384>;<br>> + timebase-frequency = <0>;<br>> + clock-frequency = <0>;
<br>> + };<br>> + };<br>> +<br>> + CS: chipselect {<br><br>We need to document this in booting-without-of.<br><br>> + compatible = "fsl,pq2fads-chipselect",<br>> + "fsl,mpc8280-chipselect",
<br>> + "fsl,pq2-chipselect";<br>> + #address-cells = <2>;<br>> + #size-cells = <1>;<br>> + fsl,ctrl = <&CSCTRL>;<br>
> +<br>> + ranges = <0 0 fe000000 00800000<br>> + 1 0 f4500000 00008000<br>> + 8 0 f8200000 00008000>;<br>> +<br>> + flash@0,0 {<br>
> + device_type = "rom";<br>> + compatible = "direct-mapped";<br>> + reg = <0 0 800000>;<br>> + probe-type = "JEDEC";
<br>> + bank-width = <4>;<br>> + };<br>> +<br>> + bcsr@1,0 {<br>> + reg = <1 0 20>;<br>> + compatible = "fsl,pq2fads-bcsr";
<br>> + };<br>> +<br>> + PCI_PIC: pic@8,0 {<br>> + #interrupt-cells = <1>;<br>> + interrupt-controller;<br>> + reg = <8 0 8>;
<br>> + compatible = "fsl,pq2ads-pci-pic";<br>> + interrupt-parent = <&PIC>;<br>> + interrupts = <18 8>;<br>> + };
<br>> + };<br>> +<br>> + memory {<br>> + device_type = "memory";<br>> + reg = <0 0>;<br>> + };<br>> +<br>> + soc@f0000000 {<br>> + #address-cells = <1>;
<br>> + #size-cells = <1>;<br>> + device_type = "soc";<br>> + compatible = "fsl,mpc8280", "fsl,pq2-soc";<br>> + ranges = <00000000 f0000000 00053000
<br>> + 80000000 80000000 40000000<br>> + f6000000 f6000000 02000000>;<br>> +<br>> + CSCTRL: chipselect {<br>> + compatible = "fsl,mpc8280-chipselect-ctrl",
<br>> + "fsl,pq2-chipselect-ctrl";<br>> + reg = <10100 60>;<br>> + fsl,bus = <&CS>;<br>> + };<br>> +
<br>> + cpm@119c0 {<br>> + #address-cells = <1>;<br>> + #size-cells = <1>;<br>> + #interrupt-cells = <2>;<br>> + compatible = "fsl,mpc8280-cpm", "fsl,cpm2";
<br>> + reg = <119c0 30 0 2000>;<br>> + ranges;<br>> +<br>> + brg@119f0 {<br>> + compatible = "fsl,mpc8280-brg",
<br>> + "fsl,cpm2-brg",<br>> + "fsl,cpm-brg";<br>> + reg = <119f0 10 115f0 10>;
<br>> + };<br>> +<br>> + serial@11a00 {<br>> + device_type = "serial";<br>> + compatible = "fsl,mpc8280-scc-uart",
<br>> + "fsl,cpm2-scc-uart";<br>> + reg = <11a00 20 8000 100>;<br>> + interrupts = <28 8>;<br>
> + interrupt-parent = <&PIC>;<br>> + fsl,cpm-brg = <1>;<br>> + fsl,cpm-command = <00800000>;<br>> + };
<br>> +<br>> + serial@11a20 {<br>> + device_type = "serial";<br>> + compatible = "fsl,mpc8280-scc-uart",<br>> + "fsl,cpm2-scc-uart";
<br>> + reg = <11a20 20 8100 100>;<br>> + interrupts = <29 8>;<br>> + interrupt-parent = <&PIC>;<br>> + fsl,cpm-brg = <2>;
<br>> + fsl,cpm-command = <04a00000>;<br>> + };<br>> +<br>> + ethernet@11320 {<br>> + device_type = "network";
<br>> + compatible = "fsl,mpc8280-fcc-enet",<br>> + "fsl,cpm2-fcc-enet";<br>> + reg = <11320 20 8500 100 113b0 1>;
<br>> + interrupts = <21 8>;<br>> + interrupt-parent = <&PIC>;<br>> + phy-handle = <&PHY0>;<br>> + linux,network-index = <0>;
<br>> + fsl,cpm-command = <16200300>;<br>> + };<br>> +<br>> + ethernet@11340 {<br>> + device_type = "network";
<br>> + compatible = "fsl,mpc8280-fcc-enet",<br>> + "fsl,cpm2-fcc-enet";<br>> + reg = <11340 20 8600 100 113d0 1>;
<br>> + interrupts = <22 8>;<br>> + interrupt-parent = <&PIC>;<br>> + phy-handle = <&PHY1>;<br>> + linux,network-index = <1>;
<br>> + fsl,cpm-command = <1a400300>;<br>> + local-mac-address = [00 e0 0c 00 79 01];<br>> + };<br>> +<br>> +
mdio@10d40 {<br>> + device_type = "mdio";<br>> + compatible = "fsl,pq2fads-mdio-bitbang",<br>> + "fsl,mpc8280-mdio-bitbang",
<br>> + "fsl,cpm2-mdio-bitbang";<br>> + #address-cells = <1>;<br>> + #size-cells = <0>;<br>> + reg = <10d40 14>;
<br>> + fsl,mdio-pin = <9>;<br>> + fsl,mdc-pin = <a>;<br>> +<br>> + PHY0: ethernet-phy@0 {<br>> + interrupt-parent = <&PIC>;
<br>> + interrupts = <19 2>;<br>> + reg = <0>;<br>> + device_type = "ethernet-phy";
<br>> + };<br>> +<br>> + PHY1: ethernet-phy@1 {<br>> + interrupt-parent = <&PIC>;<br>> + interrupts = <19 2>;
<br>> + reg = <3>;<br>> + device_type = "ethernet-phy";<br>> + };<br>> + };
<br>> +<br>> + usb@11b60 {<br>> + #address-cells = <1>;<br>> + #size-cells = <0>;<br>> + compatible = "fsl,mpc8280-usb",
<br>> + "fsl,cpm2-usb";<br>> + reg = <11b60 18 8b00 100>;<br>> + interrupt-parent = <&PIC>;
<br>> + interrupts = <b 8>;<br>> + fsl,cpm-command = <2e600000>;<br>> + };<br>> + };<br>> +<br>> + PIC:
interrupt-controller@10c00 {<br>> + #interrupt-cells = <2>;<br>> + interrupt-controller;<br>> + reg = <10c00 80>;<br>> + compatible = "fsl,mpc8280-pic", "fsl,pq2-pic";
<br><br>this should also have a "fsl,cpm2-pic" or something of that form.<br>(exact same pic exists on 8560, 85xx+CPM)<br><br>> + };<br>> +<br>> + pci@10800 {<br>> + device_type = "pci";
<br>> + reg = <10800 10c 101ac 8 101c4 8>;<br>> + compatible = "fsl,mpc8280-pci", "fsl,pq2-pci";<br>> + #interrupt-cells = <1>;
<br>> + #size-cells = <2>;<br>> + #address-cells = <3>;<br>> + clock-frequency = <d#66000000>;<br>> + interrupt-map-mask = <f800 0 0 7>;
<br>> + interrupt-map = <<br>> + /* IDSEL 0x16 */<br>> + b000 0 0 1 &PCI_PIC 0<br>> + b000 0 0 2 &PCI_PIC 1
<br>> + b000 0 0 3 &PCI_PIC 2<br>> + b000 0 0 4 &PCI_PIC 3<br>> +<br>> + /* IDSEL 0x17 */<br>
> + b800 0 0 1 &PCI_PIC 4<br>> + b800 0 0 2 &PCI_PIC 5<br>> + b800 0 0 3 &PCI_PIC 6<br>> + b800 0 0 4 &PCI_PIC 7
<br>> +<br>> + /* IDSEL 0x18 */<br>> + c000 0 0 1 &PCI_PIC 8<br>> + c000 0 0 2 &PCI_PIC 9<br>
> + c000 0 0 3 &PCI_PIC a<br>> + c000 0 0 4 &PCI_PIC b>;<br>> +<br>> + interrupt-parent = <&PIC>;
<br>> + interrupts = <12 8>;<br>> + ranges = <42000000 0 80000000 80000000 0 20000000<br>> + 02000000 0 a0000000 a0000000 0 20000000<br>
> + 01000000 0 00000000 f6000000 0 02000000>;<br>> + };<br>> + };<br>> +<br>> + chosen {<br>> + linux,stdout-path = "/soc/cpm/serial@11a00";
<br>> + };<br>> +};<br><br>- k<br><br><br><br><br>------------------------------<br><br>_______________________________________________<br>Linuxppc-dev mailing list<br><a href="mailto:Linuxppc-dev@ozlabs.org">Linuxppc-dev@ozlabs.org
</a><br><a href="https://ozlabs.org/mailman/listinfo/linuxppc-dev">https://ozlabs.org/mailman/listinfo/linuxppc-dev</a><br><br>End of Linuxppc-dev Digest, Vol 37, Issue 87<br>********************************************<br>
</blockquote></div><br>