[U-Boot-Users] A simple howto boot sequoia (ARCH=powerpc) using flattened device tree (FDT)

[U-Boot-Users] A simple howto boot sequoia (ARCH=powerpc) using flattened device tree (FDT)

[Niklaus Giger]

Hi

It took me a evening to put everything together. Therefore I send this mail
hoping it may help somebody else. Hopefully some of the content will find
its way into the DULG/FAQ, may as point 14.3.30. "Booting using flattened device tree (FDT)"

First one needs a recent U-boot with FDT support compiled into, e.g 
1.3.2-rc3-g772003e4-dirty (Apr 11 2008 - 15:56:0 for the sequoia board.

Secone one needs a recent Linux kernel made using "ARCH=powerpc", e.g. from 
2.6.25-00002-ga9bf9f0 from  git://www.denx.de/git/linux-2.6-denx.git.

Third one needs a recent dtc (Device Tree Compiler). The following commands
$ git clone http://www.jdl.com/software/dtc.git
$ cd dtc && make && sudo cp dtc /usr/local/bin
should do the job.

Now you are ready to compile the device tree blob. I used the commands given in
http://www.denx.de/wiki/view/DULG/LinuxFDTBlob
dtc -b 0 -V 17 -R 4 -S 0x3000 -I dts -O dtb -f arch/powerpc/boot/dts/sequoia.dts \
> /tftpboot/sequoia/sequoia.dtb

Now power up your sequoia board and execute the following commands to start a
Linux kernel on a NFS root device. The following commands did the job for me:

> Hit any key to stop autoboot:  0
> => tftp  200000 /tftpboot/sequoia/uImage
> Waiting for PHY auto negotiation to complete.. done
> ENET Speed is 100 Mbps - FULL duplex connection (EMAC0)
> Using ppc_4xx_eth0 device
> TFTP from server 172.25.1.3; our IP address is 172.25.1.88
> Filename '/tftpboot/sequoia/uImage'.
> Load address: 0x200000
> Loading: #################################################################
>          ######################
> done
> Bytes transferred = 1277067 (137c8b hex)
> => tftp 1000000 /tftpboot/sequoia/sequoia.dtb
> ENET Speed is 100 Mbps - FULL duplex connection (EMAC0)
> Using ppc_4xx_eth0 device
> TFTP from server 172.25.1.3; our IP address is 172.25.1.88
> Filename '/tftpboot/sequoia/sequoia.dtb'.
> Load address: 0x1000000
> Loading: #
> done
> Bytes transferred = 12288 (3000 hex)
> => run nfsargs addip addtty
> => printenv bootargs
> bootargs=root=/dev/nfs rw nfsroot=172.25.1.3:/opt/eldk/ppc_4xxFP
> ip=172.25.1.88:172.25.1.3:::sequoia:eth0:off panic=1 console=ttyS0,115200
> => fdt addr 1000000
> => fdt chosen
> => fdt list
<...>
> => fdt print
<...>
> => bootm 200000 - 1000000
> ## Booting image at 00200000 ...
>    Image Name:   Linux-2.6.25-00002-ga9bf9f0
>    Image Type:   PowerPC Linux Kernel Image (gzip compressed)
>    Data Size:    1277003 Bytes =  1.2 MB
>    Load Address: 00000000
>    Entry Point:  00000000
>    Verifying Checksum ... OK
>    Uncompressing Kernel Image ... OK
>    Booting using the fdt at 0x1000000
>    Loading Device Tree to 007fc000, end 007fefff ... OK
> Using Sequoia machine description
<...>

Thats it. Now you should boot into your shiny new Linux kernel. Attached is
a gzipped output of my startup (for the curious).

Once my kernel started I used the following commands to update my u-boot
environment:
> setenv ftd_get 'tftp 200000 ${bootfile};tftp 1000000 sequoia/sequoia.dtb;fdt addr 1000000;' 
> setenv net_nfs 'run ftd_get nfsargs addip addtty; fdt chosen;bootm 200000 - 1000000' 
> saveenv 

Best regards

Niklaus
-------------- next part --------------
A non-text attachment was scrubbed...
Name: sequoia.log.gz
Type: application/x-gzip
Size: 5179 bytes
Desc: not available
Url : http://lists.denx.de/pipermail/u-boot/attachments/20080514/da0b3b47/attachment.bin 

[U-Boot-Users] A simple howto boot sequoia (ARCH=powerpc) using flattened device tree (FDT)

[Larry Johnson]

Hi Niklaus, Stefan, and all,

Niklaus Giger wrote:
> Hi
> 
> It took me a evening to put everything together. Therefore I send this mail
> hoping it may help somebody else. Hopefully some of the content will find
> its way into the DULG/FAQ, may as point 14.3.30. "Booting using flattened device tree (FDT)"

Niklaus, thank you for putting together this howto.  It did help me.

I also have a couple of comments and questions.
 
> First one needs a recent U-boot with FDT support compiled into, e.g 
> 1.3.2-rc3-g772003e4-dirty (Apr 11 2008 - 15:56:0 for the sequoia board.
> 
> Secone one needs a recent Linux kernel made using "ARCH=powerpc", e.g. from 
> 2.6.25-00002-ga9bf9f0 from  git://www.denx.de/git/linux-2.6-denx.git.
> 
> Third one needs a recent dtc (Device Tree Compiler). The following commands
> $ git clone http://www.jdl.com/software/dtc.git
> $ cd dtc && make && sudo cp dtc /usr/local/bin
> should do the job.
> 
> Now you are ready to compile the device tree blob. I used the commands given in
> http://www.denx.de/wiki/view/DULG/LinuxFDTBlob
> dtc -b 0 -V 17 -R 4 -S 0x3000 -I dts -O dtb -f arch/powerpc/boot/dts/sequoia.dts \
>> /tftpboot/sequoia/sequoia.dtb

BTW, because the ">" before "/tftpboot/sequoia/sequoia.dtb" is the first
character on the line, Thunderbird displays it as a quote.

> Now power up your sequoia board and execute the following commands to start a
> Linux kernel on a NFS root device. The following commands did the job for me:
> 
>> Hit any key to stop autoboot:  0
>> => tftp  200000 /tftpboot/sequoia/uImage
>> Waiting for PHY auto negotiation to complete.. done
>> ENET Speed is 100 Mbps - FULL duplex connection (EMAC0)
>> Using ppc_4xx_eth0 device
>> TFTP from server 172.25.1.3; our IP address is 172.25.1.88
>> Filename '/tftpboot/sequoia/uImage'.
>> Load address: 0x200000
>> Loading: #################################################################
>>          ######################
>> done
>> Bytes transferred = 1277067 (137c8b hex)
>> => tftp 1000000 /tftpboot/sequoia/sequoia.dtb
>> ENET Speed is 100 Mbps - FULL duplex connection (EMAC0)
>> Using ppc_4xx_eth0 device
>> TFTP from server 172.25.1.3; our IP address is 172.25.1.88
>> Filename '/tftpboot/sequoia/sequoia.dtb'.
>> Load address: 0x1000000
>> Loading: #
>> done
>> Bytes transferred = 12288 (3000 hex)
>> => run nfsargs addip addtty
>> => printenv bootargs
>> bootargs=root=/dev/nfs rw nfsroot=172.25.1.3:/opt/eldk/ppc_4xxFP
>> ip=172.25.1.88:172.25.1.3:::sequoia:eth0:off panic=1 console=ttyS0,115200

The "sequoia.dts" file in linux-2.6-denx contains a line specifying
"bootargs", and this apparently overrides the environment variable, as
can be seen by typing "cat /proc/cmdline" under Linux.

>> => fdt addr 1000000
>> => fdt chosen
>> => fdt list
> <...>
>> => fdt print
> <...>
>> => bootm 200000 - 1000000
>> ## Booting image at 00200000 ...

When I run this using U-Boot 1.3.3, it tells me that it's booting a
"Legacy Image".  Is this correct?

>>    Image Name:   Linux-2.6.25-00002-ga9bf9f0
>>    Image Type:   PowerPC Linux Kernel Image (gzip compressed)
>>    Data Size:    1277003 Bytes =  1.2 MB
>>    Load Address: 00000000
>>    Entry Point:  00000000
>>    Verifying Checksum ... OK
>>    Uncompressing Kernel Image ... OK
>>    Booting using the fdt at 0x1000000
>>    Loading Device Tree to 007fc000, end 007fefff ... OK
>> Using Sequoia machine description
> <...>
> 
> Thats it. Now you should boot into your shiny new Linux kernel. Attached is
> a gzipped output of my startup (for the curious).
> 
> Once my kernel started I used the following commands to update my u-boot
> environment:
>> setenv ftd_get 'tftp 200000 ${bootfile};tftp 1000000 sequoia/sequoia.dtb;fdt addr 1000000;' 
>> setenv net_nfs 'run ftd_get nfsargs addip addtty; fdt chosen;bootm 200000 - 1000000' 
>> saveenv 
> 
> Best regards
> 
> Niklaus

I normally test Linux by booting Sequoia from the flash images
distributed by AMCC.  The flash partition information in "sequoia.dts"
is for an early distribution (Rev. 2, I think).  The latest distribution
I have is Rev. 6.  (Is there anything later?)  The following patch
updates the partition information for Rev 6.  It also comments out the
"bootargs" definition, so I can specify it from U-Boot.


diff --git a/arch/powerpc/boot/dts/sequoia.dts b/arch/powerpc/boot/dts/sequoia.dts
index 96dbe49..181b796 100644
--- a/arch/powerpc/boot/dts/sequoia.dts
+++ b/arch/powerpc/boot/dts/sequoia.dts
@@ -168,32 +168,36 @@
 				nor_flash at 0,0 {
 					compatible = "amd,s29gl256n", "cfi-flash";
 					bank-width = <2>;
-					reg = <0 000000 4000000>;
+					reg = <0 0000000 4000000>;
 					#address-cells = <1>;
 					#size-cells = <1>;
-					partition at 0 {
+					partition at 0000000 {
 						label = "Kernel";
-						reg = <0 180000>;
+						reg = <0000000 0200000>;
 					};
-					partition at 180000 {
+					partition at 0200000 {
+						label = "kozio";
+						reg = <0200000 0200000>;
+					};
+					partition at 0400000 {
 						label = "ramdisk";
-						reg = <180000 200000>;
+						reg = <0400000 1400000>;
 					};
-					partition at 380000 {
+					partition at 1800000 {
 						label = "file system";
-						reg = <380000 3aa0000>;
+						reg = <1800000 0400000>;
 					};
-					partition at 3e20000 {
-						label = "kozio";
-						reg = <3e20000 140000>;
+					partition at 1c00000 {
+						label = "unused";
+						reg = <1c00000 2360000>;
 					};
 					partition at 3f60000 {
 						label = "env";
-						reg = <3f60000 40000>;
+						reg = <3f60000 0040000>;
 					};
 					partition at 3fa0000 {
 						label = "u-boot";
-						reg = <3fa0000 60000>;
+						reg = <3fa0000 0060000>;
 					};
 				};
 
@@ -359,6 +363,6 @@
 
 	chosen {
 		linux,stdout-path = "/plb/opb/serial at ef600300";
-		bootargs = "console=ttyS0,115200";
+/*		bootargs = "console=ttyS0,115200"; */
 	};
 };


Best regards,
Larry

[U-Boot-Users] A simple howto boot sequoia (ARCH=powerpc) using flattened device tree (FDT)

[Stefan Roese]

Hi Larry,

On Thursday 22 May 2008, Larry Johnson wrote:
> >> => run nfsargs addip addtty
> >> => printenv bootargs
> >> bootargs=root=/dev/nfs rw nfsroot=172.25.1.3:/opt/eldk/ppc_4xxFP
> >> ip=172.25.1.88:172.25.1.3:::sequoia:eth0:off panic=1
> >> console=ttyS0,115200
>
> The "sequoia.dts" file in linux-2.6-denx contains a line specifying
> "bootargs", and this apparently overrides the environment variable, as
> can be seen by typing "cat /proc/cmdline" under Linux.

Correct. And when the "chosen" node exists, the "bootm" doesn't override the 
bootargs. There are three ways to change this behavior:

a) Delete the chosen node from the dts
b) Run "fdt chosen" in U-Boot before booting Linux
c) Change U-Boot to enable overwriting the chosen node upon Linux
   booting without needing to call "fdt chosen"

Currently I usually use a) if possible. So I won't add a chosen node when I 
create a new board port. But I would like to see c) implemented too 
for "older" arch/powerpc board ports (like Sequoia) that have a chosen node 
in their dts. Anyone care to send a patch for this? :)

> >> => fdt addr 1000000
> >> => fdt chosen
> >> => fdt list
> >
> > <...>
> >
> >> => fdt print
> >
> > <...>
> >
> >> => bootm 200000 - 1000000
> >> ## Booting image at 00200000 ...
>
> When I run this using U-Boot 1.3.3, it tells me that it's booting a
> "Legacy Image".  Is this correct?

Yes. This refers to the "old" uImage formate compared to the "new" FIT 
(Flattened Image Tree) uImage format. Please see README for more infos about 
this FIT.

> >>    Image Name:   Linux-2.6.25-00002-ga9bf9f0
> >>    Image Type:   PowerPC Linux Kernel Image (gzip compressed)
> >>    Data Size:    1277003 Bytes =  1.2 MB
> >>    Load Address: 00000000
> >>    Entry Point:  00000000
> >>    Verifying Checksum ... OK
> >>    Uncompressing Kernel Image ... OK
> >>    Booting using the fdt at 0x1000000
> >>    Loading Device Tree to 007fc000, end 007fefff ... OK
> >> Using Sequoia machine description
> >
> > <...>
> >
> > Thats it. Now you should boot into your shiny new Linux kernel. Attached
> > is a gzipped output of my startup (for the curious).
> >
> > Once my kernel started I used the following commands to update my u-boot
> >
> > environment:
> >> setenv ftd_get 'tftp 200000 ${bootfile};tftp 1000000
> >> sequoia/sequoia.dtb;fdt addr 1000000;' setenv net_nfs 'run ftd_get
> >> nfsargs addip addtty; fdt chosen;bootm 200000 - 1000000' saveenv
> >
> > Best regards
> >
> > Niklaus
>
> I normally test Linux by booting Sequoia from the flash images
> distributed by AMCC.  The flash partition information in "sequoia.dts"
> is for an early distribution (Rev. 2, I think).  The latest distribution
> I have is Rev. 6.  (Is there anything later?)

Not that I am aware of. But we should probably update it (again) to add the 
dtb partition. The kernel.org canyonlands.dts should be a good example.

Best regards,
Stefan

=====================================================================
DENX Software Engineering GmbH,     MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: +49-8142-66989-0 Fax: +49-8142-66989-80  Email: office at denx.de
=====================================================================

[U-Boot-Users] A simple howto boot sequoia (ARCH=powerpc) using flattened device tree (FDT)

[Jerry Van Baren]

Stefan Roese wrote:
> Hi Larry,
> 
> On Thursday 22 May 2008, Larry Johnson wrote:
>>>> => run nfsargs addip addtty
>>>> => printenv bootargs
>>>> bootargs=root=/dev/nfs rw nfsroot=172.25.1.3:/opt/eldk/ppc_4xxFP
>>>> ip=172.25.1.88:172.25.1.3:::sequoia:eth0:off panic=1
>>>> console=ttyS0,115200
>> The "sequoia.dts" file in linux-2.6-denx contains a line specifying
>> "bootargs", and this apparently overrides the environment variable, as
>> can be seen by typing "cat /proc/cmdline" under Linux.
> 
> Correct. And when the "chosen" node exists, the "bootm" doesn't override the 
> bootargs. There are three ways to change this behavior:
> 
> a) Delete the chosen node from the dts
> b) Run "fdt chosen" in U-Boot before booting Linux
> c) Change U-Boot to enable overwriting the chosen node upon Linux
>    booting without needing to call "fdt chosen"
> 
> Currently I usually use a) if possible. So I won't add a chosen node when I 
> create a new board port. But I would like to see c) implemented too 
> for "older" arch/powerpc board ports (like Sequoia) that have a chosen node 
> in their dts. Anyone care to send a patch for this? :)

Note: the difference between b) and c) is that "bootm" doesn't set the 
"force" flag but "fdt chosen" does, so "fdt chosen" overrides all 
/chosen property settings (that u-boot knows about).

It would be relatively easy to do c) by creating Yet Another Config 
Variable that bootm used for the "force" flag rather than hardcoding it. 
  I'm not wild about creating YACV.  Adding Yet Another Parameter to 
bootm is probably as bad or worse.  Hmmmm.

On a related note, the population of the chosen node (when not forced) 
is fine grained now: if /chosen exists, but a /chosen/property does 
exist it is created.  If the /chosen/property already exists, it is not 
modified.

For the most part, deleting the /chosen node in the source .dts is a 
good thing.  The fine grained population of /chosen is nice because you 
can put stuff in the .dts /chosen node that u-boot doesn't know about 
and thus doesn't populate, but that linux (or whatever) needs.  Another 
scenario would be if you want to override the u-boot value.  Obviously, 
this is a tradeoff - most times enhancing u-boot is a better option than 
overriding/extending it in the .dts.

>>>> => fdt addr 1000000
>>>> => fdt chosen
>>>> => fdt list
>>> <...>
>>>
>>>> => fdt print
>>> <...>
>>>
>>>> => bootm 200000 - 1000000
>>>> ## Booting image at 00200000 ...
>> When I run this using U-Boot 1.3.3, it tells me that it's booting a
>> "Legacy Image".  Is this correct?
> 
> Yes. This refers to the "old" uImage formate compared to the "new" FIT 
> (Flattened Image Tree) uImage format. Please see README for more infos about 
> this FIT.
> 
>>>>    Image Name:   Linux-2.6.25-00002-ga9bf9f0
>>>>    Image Type:   PowerPC Linux Kernel Image (gzip compressed)
>>>>    Data Size:    1277003 Bytes =  1.2 MB
>>>>    Load Address: 00000000
>>>>    Entry Point:  00000000
>>>>    Verifying Checksum ... OK
>>>>    Uncompressing Kernel Image ... OK
>>>>    Booting using the fdt at 0x1000000
>>>>    Loading Device Tree to 007fc000, end 007fefff ... OK
>>>> Using Sequoia machine description
>>> <...>
>>>
>>> Thats it. Now you should boot into your shiny new Linux kernel. Attached
>>> is a gzipped output of my startup (for the curious).
>>>
>>> Once my kernel started I used the following commands to update my u-boot
>>>
>>> environment:
>>>> setenv ftd_get 'tftp 200000 ${bootfile};tftp 1000000
>>>> sequoia/sequoia.dtb;fdt addr 1000000;' setenv net_nfs 'run ftd_get
>>>> nfsargs addip addtty; fdt chosen;bootm 200000 - 1000000' saveenv
>>> Best regards
>>>
>>> Niklaus
>> I normally test Linux by booting Sequoia from the flash images
>> distributed by AMCC.  The flash partition information in "sequoia.dts"
>> is for an early distribution (Rev. 2, I think).  The latest distribution
>> I have is Rev. 6.  (Is there anything later?)
> 
> Not that I am aware of. But we should probably update it (again) to add the 
> dtb partition. The kernel.org canyonlands.dts should be a good example.
> 
> Best regards,
> Stefan

[U-Boot-Users] A simple howto boot sequoia (ARCH=powerpc) using flattened device tree (FDT)

[Stefan Roese]

On Friday 23 May 2008, Jerry Van Baren wrote:
> > Correct. And when the "chosen" node exists, the "bootm" doesn't override
> > the bootargs. There are three ways to change this behavior:
> >
> > a) Delete the chosen node from the dts
> > b) Run "fdt chosen" in U-Boot before booting Linux
> > c) Change U-Boot to enable overwriting the chosen node upon Linux
> >    booting without needing to call "fdt chosen"
> >
> > Currently I usually use a) if possible. So I won't add a chosen node when
> > I create a new board port. But I would like to see c) implemented too for
> > "older" arch/powerpc board ports (like Sequoia) that have a chosen node
> > in their dts. Anyone care to send a patch for this? :)
>
> Note: the difference between b) and c) is that "bootm" doesn't set the
> "force" flag but "fdt chosen" does, so "fdt chosen" overrides all
> /chosen property settings (that u-boot knows about).

Yes, I noticed this some time ago.

> It would be relatively easy to do c) by creating Yet Another Config
> Variable that bootm used for the "force" flag rather than hardcoding it.
>   I'm not wild about creating YACV.  Adding Yet Another Parameter to
> bootm is probably as bad or worse.  Hmmmm.

I'm wondering who really wants to *not* override the chosen bootargs property? 
I'm probably missing something here, but for me it just makes no sense to not 
override the bootargs property with the U-Boot bootargs env variable.

Best regards,
Stefan

=====================================================================
DENX Software Engineering GmbH,     MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: +49-8142-66989-0 Fax: +49-8142-66989-80  Email: office at denx.de
=====================================================================

[U-Boot-Users] A simple howto boot sequoia (ARCH=powerpc) using flattened device tree (FDT)

[Jerry Van Baren]

Stefan Roese wrote:
> On Friday 23 May 2008, Jerry Van Baren wrote:

[snip]

>> It would be relatively easy to do c) by creating Yet Another Config
>> Variable that bootm used for the "force" flag rather than hardcoding it.
>>   I'm not wild about creating YACV.  Adding Yet Another Parameter to
>> bootm is probably as bad or worse.  Hmmmm.
> 
> I'm wondering who really wants to *not* override the chosen bootargs property? 
> I'm probably missing something here, but for me it just makes no sense to not 
> override the bootargs property with the U-Boot bootargs env variable.
> 
> Best regards,
> Stefan

Like most decisions, we kinda backed into it in an effort to mimic 
previous behavior at the start, and then tweaking our decision and code 
repeatedly over time.

The original fdt support (CONFIG_OF_FLAT_TREE) did not touch the /chosen 
node *at all* if it existed.  I carried this behavior forward with the 
libfdt version under the banner of compatibility.  Subsequently, Scott 
Wood suggested and one of us implemented a fine-grained behavior where 
we would create /chosen properties if they didn't exist but not override 
existing /chosen properties.

It may be time to reevaluate our assumptions and decisions.

Observations:
* Removing the "force" option would simplify the code.
* I've been threatening to remove the deprecated CONFIG_OF_FLAT_TREE
     for a while now.  Maybe it is time, maybe I /make/ time, to do it
     this window.

Best regards,
gvb

[U-Boot-Users] A simple howto boot sequoia (ARCH=powerpc) using flattened device tree (FDT)

[Stefan Roese]

On Friday 23 May 2008, Jerry Van Baren wrote:
> > I'm wondering who really wants to *not* override the chosen bootargs
> > property? I'm probably missing something here, but for me it just makes
> > no sense to not override the bootargs property with the U-Boot bootargs
> > env variable.
> >
> > Best regards,
> > Stefan
>
> Like most decisions, we kinda backed into it in an effort to mimic
> previous behavior at the start, and then tweaking our decision and code
> repeatedly over time.
>
> The original fdt support (CONFIG_OF_FLAT_TREE) did not touch the /chosen
> node *at all* if it existed.  I carried this behavior forward with the
> libfdt version under the banner of compatibility.  Subsequently, Scott
> Wood suggested and one of us implemented a fine-grained behavior where
> we would create /chosen properties if they didn't exist but not override
> existing /chosen properties.

Understood.

> It may be time to reevaluate our assumptions and decisions.

Yes, please :)

> Observations:
> * Removing the "force" option would simplify the code.
> * I've been threatening to remove the deprecated CONFIG_OF_FLAT_TREE
>      for a while now.  Maybe it is time, maybe I /make/ time, to do it
>      this window.

Would be very welcome. Thanks.

Best regards,
Stefan

=====================================================================
DENX Software Engineering GmbH,     MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: +49-8142-66989-0 Fax: +49-8142-66989-80  Email: office at denx.de
=====================================================================

[U-Boot-Users] A simple howto boot sequoia (ARCH=powerpc) using flattened device tree (FDT)

[Wolfgang Denk]

In message <4836BF4F.7060002@ge.com> you wrote:
>
> * Removing the "force" option would simplify the code.
> * I've been threatening to remove the deprecated CONFIG_OF_FLAT_TREE
>      for a while now.  Maybe it is time, maybe I /make/ time, to do it
>      this window.

ACK - you have my "go" for it!

Best regards,

Wolfgang Denk

-- 
DENX Software Engineering GmbH,     MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de
It is not best to swap horses while crossing the river.
- Abraham Lincoln