On 10/23/07, Michal Simek <[EMAIL PROTECTED]> wrote:
> Hi David,
> I remove some labels from my generator. I created fake system with some
> peripherals.
> There are 3 buses and 3 bridges.
> Can you check it and tell me what is wrong?
>
> Thanks,
> Michal Simek
>
> / {
> model = "mONStR";
You should have a board-level compatible property here
> chosen {
> bootargs = "root=/dev/xsysace/disc0/part2";
> } ;
> cpus {
> #size-cells = <0>;
> #cpus = < 0 >;
> #address-cells = <1>;
> microblaze_0,[EMAIL PROTECTED] {
Simply [EMAIL PROTECTED] will do.
> device_type = "cpu";
> reg = <0>;
> clock-frequency = <5f5e1000>;
> timebase-frequency = <1FCA055>;
> i-cache-line-size = <2000>;
> i-cache-size = <10>;
> d-cache-line-size = <2000>;
> d-cache-size = <10>;
> xilinx,pvr = <0>;
use 'xlnx,' for the prefix; this is a comment that I received on the
binding document that the stock ticker is an appropriate appreviation.
> xilinx,debug-enabled = <1>;
> xilinx,fsl-links = <0>;
> } ;
> } ;
>
You should have a parent 'plb' bus node for all these devices to be children of.
> [EMAIL PROTECTED] {
> compatible = "opb_ethernet_1.04.a","opb_ethernet";
- add manufacture prefix
- convert underscores to dashes
- drop "opb_ethernet"; there's no such thing
Just "xlnx,opb-ethernet-1.04.a" will do; or something like
"xlnx,opb-ethernet-1.04b","xlnx,opb-ethernet-1.04a" works too.
> interrupts = < 3 0 >;
> reg = < 10060000 10000 >;
> device_type = "network";
> xilinx,cam-exist = <0>;
> xilinx,dev-blk-id = <1>;
> xilinx,dev-mir-enable = <1>;
> xilinx,dma-present = <1>;
> xilinx,include-dev-pencoder = <1>;
> xilinx,ipif-rdfifo-depth = <8000>;
> xilinx,ipif-wrfifo-depth = <8000>;
> xilinx,mii-exist = <1>;
use 'xlnx,' for prefix.
> } ;
> [EMAIL PROTECTED] {
> memreg:reg = < 20000000 10000000 >;
> device_type = "memory";
> } ;
> [EMAIL PROTECTED] {
> compatible = "opb_uart16550_1.00.d","opb_uart16550";
'opb_uart16550' is bogus non-device; Always specify a version for IP
core compatible fields. There was some talk about defining a
'sparse16550' or some such value to reflect things that were almost a
16550 but had a different register layout; but in the mean time leave
it out.
- change '_' to '-', add 'xlnx,'; etc.
> reg = < 10030000 10000 >;
> device_type = "serial";
> } ;
> [EMAIL PROTECTED] {
> compatible = "opb_timer_1.00.b","opb_timer";
ditto
> interrupts = < 0 0 >;
> reg = < 10020000 10000 >;
> xilinx,count-width = <20>;
> xilinx,one-timer-only = <0>;
> } ;
> [EMAIL PROTECTED] {
- change '_' to '-'
> ranges = < 0 30000000 10000000 >;
> [EMAIL PROTECTED] {
Since you're bus uses the ranges property value to translate; the
device address should reflect the offset off the base of the bus:
[EMAIL PROTECTED]
If instead your ranges property was empty then the full address still
works. Address translation makes sense for the opb-opb-lite because
it's only got one translation range. However, the plb-opb bridge
covers multiple ranges so it's probably easier to leave out the
translation.
> compatible = "opb_gpio_3.01.b","opb_gpio";
> reg = < 30020000 10000 >;
Same comment as above; reg = <20000 10000>; These comments go for all
the nodes below.
> xilinx,gpio-width = <4>;
> xilinx,is-dual = <0>;
> } ;
> [EMAIL PROTECTED] {
> compatible = "opb_iic_1.02.a","opb_iic";
> reg = < 30030000 10000 >;
> device_type = "i2c";
> } ;
>
> [EMAIL PROTECTED] {
> compatible = "opb_gpio_3.01.b","opb_gpio";
> reg = < 30010000 10000 >;
> xilinx,gpio-width = <20>;
> xilinx,is-dual = <0>;
> } ;
> [EMAIL PROTECTED] {
> compatible =
> "opb_ethernetlite_1.01.b","opb_ethernetlite";
> reg = < 30040000 10000 >;
> device_type = "network";
> xilinx,duplex = <1>;
> xilinx,rx-ping-pong = <0>;
> xilinx,tx-ping-pong = <0>;
> } ;
> [EMAIL PROTECTED] {
> compatible = "opb_sysace_1.00.c","opb_sysace";
> reg = < 30050000 10000 >;
> xilinx,mem-width = <10>;
> } ;
> [EMAIL PROTECTED] {
> compatible =
> "opb_ps2_dual_ref_1.00.a","opb_ps2_dual_ref";
> interrupts = < 2 0 >;
> interrupts = < 1 0 >;
> reg = < 30060000 10000 >;
> } ;
> };
> [EMAIL PROTECTED] {
> compatible = "opb_intc_1.00.c","opb_intc";
> reg = < 10010000 10000 >;
> } ;
> [EMAIL PROTECTED] {
> compatible = "opb_mdm_2.00.a","opb_mdm";
> reg = < 10050000 10000 >;
> xilinx,mb-dbg-ports = <1>;
> xilinx,uart-width = <8>;
> xilinx,use-uart = <1>;
> } ;
> [EMAIL PROTECTED] {
> compatible = "opb_uartlite_1.00.b","opb_uartlite";
> interrupts = < 4 0 >;
> reg = < 10040000 10000 >;
> device_type = "serial";
> xilinx,baudrate = <2580>;
> xilinx,data-bits = <8>;
> xilinx,clk-freq = <5f5e100>;
> xilinx,odd-parity = <0>;
> xilinx,use-parity = <0>;
My patch to booting-without-of says that you should have a
'current-speed' property (instead of xlnx,baudrate) because it's a
standard property; but 'xlnx,baudrate' might be a suitable alternative
because this is a fixed speed device. Segher, David; what say you?
> } ;
> [EMAIL PROTECTED] {
> ranges = < 0 80000000 80000000 >;
> [EMAIL PROTECTED] {
> compatible = "plb_uart16550_1.00.c","plb_uart16550";
> reg = < a0020000 10000 >;
> device_type = "serial";
> } ;
> [EMAIL PROTECTED] {
> compatible = "plb_gpio_1.00.b","plb_gpio";
> reg = < a0010000 10000 >;
> xilinx,gpio-width = <20>;
> xilinx,is-dual = <0>;
> } ;
> [EMAIL PROTECTED] {
> compatible = "plb_ethernet_1.01.a","plb_ethernet";
> reg = < a0000000 10000 >;
> device_type = "network";
> } ;
> [EMAIL PROTECTED] {
> ranges = < 0 10000000 10000000 >;
> ranges = < 1 20000000 10000000 >;
> };
There are no nodes on this bus. What is the intended usage? Also,
you cannot have two properties with the same name, I think the syntax
you want is:
ranges = <0 10000000 10000000 2 20000000 10000000>;
Also, these values won't work. They state that you've got two address
range translations. The first translates from address 10000000 to
address 0 (which makes sense). The second translates from address
20000000 to address 1 (which overlaps the first region, only offset by
1 byte).
> cpus {
> #size-cells = <0>;
> #cpus = < 1 >;
> #address-cells = <1>;
> ppc405_0,[EMAIL PROTECTED] {
> device_type = "cpu";
> reg = <0>;
> clock-frequency = <5f5e1000>;
> timebase-frequency = <1FCA055>;
> } ;
> } ;
This is weird. Is this representing a design with both a ppc and a
microblaze? If so; I would generate 2 device trees. One for each
processor.
> };
> } ;
>
BTW, Thanks for all this work
g.
--
Grant Likely, B.Sc., P.Eng.
Secret Lab Technologies Ltd.
[EMAIL PROTECTED]
(403) 399-0195
_______________________________________________
Linuxppc-dev mailing list
Linuxppc-dev@ozlabs.org
https://ozlabs.org/mailman/listinfo/linuxppc-dev
