[U-Boot-Users] u-boot kernel parameters

[U-Boot-Users] u-boot kernel parameters

[Bizzu]

Hi all,
I have an ocotea board, the denx latest 2.6 and 2.4 kernel and u-boot 1.1.4.
I downloaded everything from Wolfgang's ftp site and followed the instructions by the letter. I tftp into memory (at 100000) and bootm my kernels.
I successfully boot linux 2.6 (2.6.14-rc3) on this board but kernel 2.4 (2.4.25) wont take off.
This is what 2.4 gives me: 
(I added early serial messages for clarity)

## Booting image at 00100000 ...
   Image Name:   Linux-2.4.25
   Created:      2006-02-07   2:25:05 UTC
   Image Type:   PowerPC Linux Kernel Image (gzip compressed)
   Data Size:    628718 Bytes = 614 kB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK
   Uncompressing Kernel Image ... OK
id mach(): done
MMU:enter
MMU:hw init
MMU:mapin
MMU:mapin_ram done
MMU:setio
MMU:exit
setup_arch: enter
setup_arch: bootmem
arch: exit
arch: exit 2

Anyone has an idea what could be wrong?


--
View this message in context: http://www.nabble.com/u-boot-kernel-parameters-t1077794.html#a2806589
Sent from the Uboot - Users forum at Nabble.com.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.denx.de/pipermail/u-boot/attachments/20060207/c192f717/attachment.htm 

[U-Boot-Users] u-boot kernel parameters

[S. Egbert]

You've entered the dark nether region of console-less portion of the
bootup code WAY before the Linux console driver is installed... and it
stop somewhere OR merrily went on its way to Linux bootup WITHOUT a console.

Once it switched from old (usually flat) memory model to virtual memory
(MMU), all bets are off.  Couple of ways to shine a light where the
cockroaches are, are to try the following:

1.  Pass a boot command line 'console=/dev/ttyS0' from your bootloader
or have it compiled in via 'make menuconfig'  Check your custom serial
driver for the exact TTY device template name (i.e., /dev/ttl0,
/dev/ttyAS0).

2. Another way to see what is going on is to flip on the
CONFIG_TEXT_CONSOLE_DEBUG and insert MANY ppc_md.progress() calls AFTER
the debug console is initialized in arch/ppc/kernel/ppc4xx_setup.c

3. Put a Linux boot command line of 'kgdb' with CONFIG_KGDB to evoke a
hardware break and then use hardware debuggerto step through the Linux
bootup sequence.

4.  Make heavy use of on-board LED indicators by calling ioremap() and
poking your virtualized hardware register location to flip on the LED
indicators.


Anyway you cut, slice or dice it, this effort will require LOTS of
recompile, relink, reload and re-run will be required to 'normalize' a
new board bring-up.

Good Luck

S. Egbert


Bizzu (sent by Nabble.com) wrote:
> Hi all,
> I have an ocotea board, the denx latest 2.6 and 2.4 kernel and u-boot 1.1.4.
> I downloaded everything from Wolfgang's ftp site and followed the instructions by the letter. I tftp into memory (at 100000) and bootm my kernels.
> I successfully boot linux 2.6 (2.6.14-rc3) on this board but kernel 2.4 (2.4.25) wont take off.
> This is what 2.4 gives me: 
> (I added early serial messages for clarity)
> 
> ## Booting image at 00100000 ...
>    Image Name:   Linux-2.4.25
>    Created:      2006-02-07   2:25:05 UTC
>    Image Type:   PowerPC Linux Kernel Image (gzip compressed)
>    Data Size:    628718 Bytes = 614 kB
>    Load Address: 00000000
>    Entry Point:  00000000
>    Verifying Checksum ... OK
>    Uncompressing Kernel Image ... OK
> id mach(): done
> MMU:enter
> MMU:hw init
> MMU:mapin
> MMU:mapin_ram done
> MMU:setio
> MMU:exit
> setup_arch: enter
> setup_arch: bootmem
> arch: exit
> arch: exit 2
> 
> Anyone has an idea what could be wrong?
> 

[U-Boot-Users] u-boot kernel parameters

[Tattone Tattone]

Argh! Somber, isn't it?

I think most of my issues are in the kernel parameters area.
The bootargs, maybe...
I went back to PIBS, just for the heck of it, and same thing happened, the
2.6 boots, the 2.4 doesn't... The later will fail the same exact way on the
same exact spot...
Unless there is something wrong with the default Wolfgang's Ocotea config in
2.4...
Thanks for the answer anyway.

Bizzu


On 2/7/06, S. Egbert <s.egbert@sbcglobal.net> wrote:
>
> You've entered the dark nether region of console-less portion of the
> bootup code WAY before the Linux console driver is installed... and it
> stop somewhere OR merrily went on its way to Linux bootup WITHOUT a
> console.
>
> Once it switched from old (usually flat) memory model to virtual memory
> (MMU), all bets are off.  Couple of ways to shine a light where the
> cockroaches are, are to try the following:
>
> 1.  Pass a boot command line 'console=/dev/ttyS0' from your bootloader
> or have it compiled in via 'make menuconfig'  Check your custom serial
> driver for the exact TTY device template name (i.e., /dev/ttl0,
> /dev/ttyAS0).
>
> 2. Another way to see what is going on is to flip on the
> CONFIG_TEXT_CONSOLE_DEBUG and insert MANY ppc_md.progress() calls AFTER
> the debug console is initialized in arch/ppc/kernel/ppc4xx_setup.c
>
> 3. Put a Linux boot command line of 'kgdb' with CONFIG_KGDB to evoke a
> hardware break and then use hardware debuggerto step through the Linux
> bootup sequence.
>
> 4.  Make heavy use of on-board LED indicators by calling ioremap() and
> poking your virtualized hardware register location to flip on the LED
> indicators.
>
>
> Anyway you cut, slice or dice it, this effort will require LOTS of
> recompile, relink, reload and re-run will be required to 'normalize' a
> new board bring-up.
>
> Good Luck
>
> S. Egbert
>
>
> Bizzu (sent by Nabble.com) wrote:
> > Hi all,
> > I have an ocotea board, the denx latest 2.6 and 2.4 kernel and u-boot
> 1.1.4.
> > I downloaded everything from Wolfgang's ftp site and followed the
> instructions by the letter. I tftp into memory (at 100000) and bootm my
> kernels.
> > I successfully boot linux 2.6 (2.6.14-rc3) on this board but kernel 2.4(
> 2.4.25) wont take off.
> > This is what 2.4 gives me:
> > (I added early serial messages for clarity)
> >
> > ## Booting image at 00100000 ...
> >    Image Name:   Linux-2.4.25
> >    Created:      2006-02-07   2:25:05 UTC
> >    Image Type:   PowerPC Linux Kernel Image (gzip compressed)
> >    Data Size:    628718 Bytes = 614 kB
> >    Load Address: 00000000
> >    Entry Point:  00000000
> >    Verifying Checksum ... OK
> >    Uncompressing Kernel Image ... OK
> > id mach(): done
> > MMU:enter
> > MMU:hw init
> > MMU:mapin
> > MMU:mapin_ram done
> > MMU:setio
> > MMU:exit
> > setup_arch: enter
> > setup_arch: bootmem
> > arch: exit
> > arch: exit 2
> >
> > Anyone has an idea what could be wrong?
> >
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.denx.de/pipermail/u-boot/attachments/20060207/5df642df/attachment.htm 

[U-Boot-Users] u-boot kernel parameters

[Wolfgang Denk]

In message <2806589.post@talk.nabble.com> you wrote:
> 
> I have an ocotea board, the denx latest 2.6 and 2.4 kernel and u-boot 1.1.4.
> I downloaded everything from Wolfgang's ftp site and followed the instructions by the letter. I tftp into memory (at 100000) and bootm my kernels.
> I successfully boot linux 2.6 (2.6.14-rc3) on this board but kernel 2.4 (2.4.25) wont take off.
> This is what 2.4 gives me: 

The documentation is based on the 2.6 kernel, and this is all what we support.
> 
> ------=_Part_11010_24584557.1139336071121
> Content-Type: text/html; charset=us-ascii
> Content-Transfer-Encoding: 7bit

Please never post HTML to this list!!

Best regards,

Wolfgang Denk

-- 
Software Engineering:  Embedded and Realtime Systems,  Embedded Linux
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de
Cigarette, n.: A fire at one end, a fool at the other, and a  bit  of
tobacco in between.

[U-Boot-Users] u-boot kernel parameters

[Wolfgang Denk]

In message <43E8ED18.2050208@sbcglobal.net> you wrote:
>
> 1.  Pass a boot command line 'console=/dev/ttyS0' from your bootloader
> or have it compiled in via 'make menuconfig'  Check your custom serial
> driver for the exact TTY device template name (i.e., /dev/ttl0,
> /dev/ttyAS0).

Alternatively, try using a post mortem dump of the lug buffer to  see
what  might  have  been prited to the console buffer. See the FAQ for
details.

> 4.  Make heavy use of on-board LED indicators by calling ioremap() and
> poking your virtualized hardware register location to flip on the LED
> indicators.

I strongly recommend *against* doing this, at least unless  you  know
*exactly*  what  you  are doing (and then you don't need this because
you will use a BDI2000 anyway). I've seen to many reports  of  "Linux
crashes  when  enabling  the  MMU"  that  were  cause by exactly such
attempts.


Best regards,

Wolfgang Denk

-- 
Software Engineering:  Embedded and Realtime Systems,  Embedded Linux
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de
Another war ... must it always be so?  How many comrades have we lost
in this way? ...  Obedience.  Duty.  Death, and more death ...
	-- Romulan Commander, "Balance of Terror", stardate 1709.2

[U-Boot-Users] u-boot kernel parameters

[Wolfgang Denk]

In message <45bf404a0602071105h4fed8fe5yd32dccc1017e1f00@mail.gmail.com> you wrote:
>
> Unless there is something wrong with the default Wolfgang's Ocotea config in
> 2.4...

There's nothing wrong with it. It just doesn't support U-Boot. Nobody
ever claimed it would.

Best regards,

Wolfgang Denk

-- 
Software Engineering:  Embedded and Realtime Systems,  Embedded Linux
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de
Of all the things I've lost, I miss my mind the most.

[U-Boot-Users] u-boot kernel parameters

[Tattone Tattone]

I understood the contrary when I read the denx.com news page:
"DENX will continue to support our Linux 2.4 kernel, too. "
My mistake then...
What should work then?

On 2/7/06, Wolfgang Denk <wd@denx.de> wrote:
> In message <45bf404a0602071105h4fed8fe5yd32dccc1017e1f00@mail.gmail.com> you wrote:
> >
> > Unless there is something wrong with the default Wolfgang's Ocotea config in
> > 2.4...
>
> There's nothing wrong with it. It just doesn't support U-Boot. Nobody
> ever claimed it would.
>
> Best regards,
>
> Wolfgang Denk
>
> --
> Software Engineering:  Embedded and Realtime Systems,  Embedded Linux
> Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de
> Of all the things I've lost, I miss my mind the most.
>

[U-Boot-Users] u-boot kernel parameters

[Stefan Roese]

On Tuesday 07 February 2006 21:55, Wolfgang Denk wrote:
> In message <45bf404a0602071105h4fed8fe5yd32dccc1017e1f00@mail.gmail.com> you 
wrote:
> > Unless there is something wrong with the default Wolfgang's Ocotea config
> > in 2.4...
>
> There's nothing wrong with it. It just doesn't support U-Boot. Nobody
> ever claimed it would.

Hmmm, I am pretty sure Ocotea linuxppc_2_4_devel worked a few month's ago 
(with U-Boot of course). I will give it a try tomorrow and let you know.

Best regards,
Stefan

[U-Boot-Users] u-boot kernel parameters

[Bizzu]

Now that's helpful!
Very, very much appreciated
Thanks Stephan
--
View this message in context: http://www.nabble.com/u-boot-kernel-parameters-t1077794.html#a2811306
Sent from the Uboot - Users forum at Nabble.com.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.denx.de/pipermail/u-boot/attachments/20060207/affe88f1/attachment.htm 

[U-Boot-Users] u-boot kernel parameters

[Bizzu]

Wolfgang,

thanks for reminding of the buffer.
This is its contents:

00151894 : 3c343e4c 696e7578 20766572 73696f6e  <4>Linux version
001518a4 : 20322e34 2e323520 28767864 6576656c   2.4.25 (vxdevel
001518b4 : 40767864 6576656c 29202867 63632076  @vxdevel) (gcc v
001518c4 : 65727369 6f6e2033 2e342e31 29202332  ersion 3.4.1) #2
001518d4 : 30205475 65204665 62203720 31343a35  0 Tue Feb 7 14:5
001518e4 : 303a3535 20505354 20323030 360a3c34  0:55 PST 2006.<4
001518f4 : 3e6b6764 6220696e 69740a3c 343e4942  >kgdb init.<4>IB
00151904 : 4d204f63 6f746561 20706f72 7420284d  M Ocotea port (M
00151914 : 6f6e7461 56697374 6120536f 66747761  ontaVista Softwa
00151924 : 72652c20 496e632e 203c736f 75726365  re, Inc. ).<4
00151944 : 3e4f6e20 6e6f6465 20302074 6f74616c  >On node 0 total
00151954 : 70616765 733a2036 35353336 0a3c343e  pages: 65536.<4>
00151964 : 7a6f6e65 2830293a 20363535 33362070  zone(0): 65536 p
00151974 : 61676573 2e0a0000 00000000 00000000  ages............
00151984 : 00000000 00000000 00000000 00000000  ................
440GX>md
00151994 : 00000000 00000000 00000000 00000000  ................
001519a4 : 00000000 00000000 00000000 00000000  ................
001519b4 : 00000000 00000000 00000000 00000000  ................
001519c4 : 00000000 00000000 00000000 00000000  ................
001519d4 : 00000000 00000000 00000000 00000000  ................
001519e4 : 00000000 00000000 00000000 00000000  ................
001519f4 : 00000000 00000000 00000000 00000000  ................
00151a04 : 00000000 00000000 00000000 00000000  ................
00151a14 : 00000000 00000000 00000000 00000000  ................
00151a24 : 00000000 00000000 00000000 00000000  ................
00151a34 : 00000000 00000000 00000000 00000000  ................
00151a44 : 00000000 00000000 00000000 00000000  ................
00151a54 : 00000000 00000000 00000000 00000000  ................
00151a64 : 00000000 00000000 00000000 00000000  ................
00151a74 : 00000000 00000000 00000000 00000000  ................
00151a84 : 00000000 00000000 00000000 00000000  ................

Not much I could do with this I am affraid...

--
View this message in context: http://www.nabble.com/u-boot-kernel-parameters-t1077794.html#a2812135
Sent from the Uboot - Users forum at Nabble.com.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.denx.de/pipermail/u-boot/attachments/20060207/d5bf6c77/attachment.htm 

[U-Boot-Users] u-boot kernel parameters

[Wolfgang Denk]

In message <45bf404a0602071323n6320991p4be1c020afa2f3d0@mail.gmail.com> you wrote:
> I understood the contrary when I read the denx.com news page:
> "DENX will continue to support our Linux 2.4 kernel, too. "

We continue to support it for the boards we support. Ocotea is not  a
board  which  we  claim to support in 2.4. We provide support for all
AMCC PowerPC boards in U-Boot and in Linux 2.6.

> My mistake then...
> What should work then?

Our 2.6 kernel tree. Please RTFM for details.

Best regards,

Wolfgang Denk

-- 
Software Engineering:  Embedded and Realtime Systems,  Embedded Linux
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de
"When the only  tool  you  have  is  a  hammer,  you  tend  to  treat
everything as if it were a nail."                    - Abraham Maslow

[U-Boot-Users] u-boot kernel parameters

[Wolfgang Denk]

In message <2812135.post@talk.nabble.com> you wrote:
>
> thanks for reminding of the buffer.

:-)

> This is its contents:
> 
> 00151894 : 3c343e4c 696e7578 20766572 73696f6e  <4>Linux version
> 001518a4 : 20322e34 2e323520 28767864 6576656c   2.4.25 (vxdevel
> 001518b4 : 40767864 6576656c 29202867 63632076  @vxdevel) (gcc v
> 001518c4 : 65727369 6f6e2033 2e342e31 29202332  ersion 3.4.1) #2

gcc 3.4.1?

Ummm... try building with another toolchain (like ELDK :-)  Not  sure
that it will help, but it might.

Best regards,

Wolfgang Denk

-- 
Software Engineering:  Embedded and Realtime Systems,  Embedded Linux
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de
Here is an Appalachian version of management's answer  to  those  who
are  concerned  with  the fate of the project: "Don't worry about the
mule. Just load the wagon."         - Mike Dennison's hillbilly uncle

[U-Boot-Users] u-boot kernel parameters

[S. Egbert]

> 
>> 4.  Make heavy use of on-board LED indicators by calling ioremap() and
>> poking your virtualized hardware register location to flip on the LED
>> indicators.
> 
> I strongly recommend *against* doing this, at least unless  you  know
> *exactly*  what  you  are doing (and then you don't need this because
> you will use a BDI2000 anyway). I've seen to many reports  of  "Linux
> crashes  when  enabling  the  MMU"  that  were  cause by exactly such
> attempts.
> 

Oh yeah... I totally agreed on your recommendation.  But when one is
located FAR FAR AWAY from the cushy software laboratory and without a
hardware debugger, I have find this technique extremely useful in very
DARK, DARK circumstances.

Another time, I had to bring-up a custom board that is totally devoid of
inputs/output interface (as those interfaces were still under HW
development), this LED method saved my bacon as I SLOWLY and PAINFULLY
integrate Xilinx UARTLITE driver (if one is extremely careful about
setting aside a TLB region JUST for that purpose.

Alright, alright.... Let us call this LED indicators, a 'poor man's'
debugger.  Desperate acts calls for desperate measure.

[U-Boot-Users] u-boot kernel parameters

[Stefan Roese]

On Tuesday 07 February 2006 22:56, Stefan Roese wrote:
> Hmmm, I am pretty sure Ocotea linuxppc_2_4_devel worked a few month's ago
> (with U-Boot of course). I will give it a try tomorrow and let you know.

As it seems the current version doesn't compile for ocotea:

make[4]: Entering directory 
`/chroot/server/home/stefan/git/linuxppc_2_4_devel/drivers/net/ibm_emac'
ppc_4xx-gcc -D__KERNEL__ 
-I/chroot/server/home/stefan/git/linuxppc_2_4_devel/include -Wall 
-Wstrict-prototypes -Wno-trigraphs -O2 -fno-strict-aliasing -fno-common 
-fomit-frame-pointer 
-I/chroot/server/home/stefan/git/linuxppc_2_4_devel/arch/ppc -fsigned-char 
-msoft-float -pipe -ffixed-r2 -Wno-uninitialized -mmultiple -mstring 
-Wa,-m405   -nostdinc 
-I /opt/eldk-3.1.1/usr/lib/gcc-lib/ppc-linux/3.3.3/include 
-DKBUILD_BASENAME=ibm_ocp_enet  -c -o ibm_ocp_enet.o ibm_ocp_enet.c
ibm_ocp_enet.c:158: error: parse error before "__res"
ibm_ocp_enet.c:158: warning: type defaults to `int' in declaration of `__res'
ibm_ocp_enet.c:158: warning: data definition has no type or storage class
ibm_ocp_enet.c: In function `emac_init':
ibm_ocp_enet.c:1981: error: `bd_t' undeclared (first use in this function)
ibm_ocp_enet.c:1981: error: (Each undeclared identifier is reported only once
ibm_ocp_enet.c:1981: error: for each function it appears in.)
ibm_ocp_enet.c:1981: error: `bd' undeclared (first use in this function)
make[4]: *** [ibm_ocp_enet.o] Error 1

If you don't get this error, your linuxppc_2_4_devel version is outdated. With 
this small patch below this is fixed and the ocotea boots again:

71a72
> #include "asm/ppcboot.h" /* test-only: ocotea build */

## Booting image at 00200000 ...
   Image Name:   Linux-2.4.25
   Created:      2006-02-08   5:44:06 UTC
   Image Type:   PowerPC Linux Kernel Image (gzip compressed)
   Data Size:    649445 Bytes = 634.2 kB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK
   Uncompressing Kernel Image ... OK
Linux version 2.4.25 (stefan at ubuntu) (gcc version 3.3.3 (DENX ELDK 3.1.1 
3.3.3-9)) #1 Wed Feb 8 06:41:37 CET 2006
IBM Ocotea port (MontaVista Software, Inc. <source@mvista.com>)
On node 0 totalpages: 65536
zone(0): 65536 pages.
zone(1): 0 pages.
zone(2): 0 pages.
Kernel command line: root=/dev/nfs rw nfsroot=192.168.1.1:/opt/eldk/ppc_4xx 
ip=192.168.80.2:192.168.1.1::255.255.0.0:ocotea:eth0:off panic=1 
console=ttyS0,115200
Calibrating delay loop... 799.53 BogoMIPS
Memory: 257000k available (976k kernel code, 320k data, 232k init, 0k highmem)
Dentry cache hash table entries: 32768 (order: 6, 262144 bytes)
Inode cache hash table entries: 16384 (order: 5, 131072 bytes)
Mount cache hash table entries: 512 (order: 0, 4096 bytes)
Buffer cache hash table entries: 16384 (order: 4, 65536 bytes)
Page-cache hash table entries: 65536 (order: 6, 262144 bytes)
POSIX conformance testing by UNIFIX
PCI: Probing PCI hardware
Linux NET4.0 for Linux 2.4
Based upon Swansea University Computer Society NET3.039
Initializing RT netlink socket
Starting kswapd
pty: 256 Unix98 ptys configured
Serial driver version 5.05c (2001-07-08) with MANY_PORTS SHARE_IRQ SERIAL_PCI 
enabled
ttyS00 at 0xfdfea200 (irq = 0) is a 16550A
ttyS01 at 0xfdfe9300 (irq = 1) is a 16550A
Generic RTC Driver v1.07
emac: IBM OCP EMAC Ethernet driver, version 2.1
Maintained by Benjamin Herrenschmidt <benh@kernel.crashing.org>
mal0: Initialized, 8 tx channels, 4 rx channels
zmii0: input 0 in SMII mode
eth0: IBM emac, MAC 00:01:73:01:dd:ac
eth0: Found Generic MII PHY (0x01)
zmii0: input 1 in SMII mode
eth1: IBM emac, MAC 00:01:73:01:dd:ad
eth1: Found Generic MII PHY (0x02)
zmii0: input 2 in SMII mode
rgmii0: input 0 in RGMII mode
eth2: IBM emac, MAC 00:01:73:01:dd:ae
eth2: Found CIS8201 Gigabit Ethernet PHY (0x10)
zmii0: input 3 in SMII mode
rgmii0: input 1 in RGMII mode
eth3: IBM emac, MAC 00:01:73:01:dd:af
eth3: Found CIS8201 Gigabit Ethernet PHY (0x18)
NET4: Linux TCP/IP 1.0 for NET4.0
IP Protocols: ICMP, UDP, TCP
IP: routing cache hash table of 2048 buckets, 16Kbytes
TCP: Hash tables configured (established 16384 bind 32768)
IP-Config: Complete:
      device=eth0, addr=192.168.80.2, mask=255.255.0.0, gw=255.255.255.255,
     host=ocotea, domain=, nis-domain=(none),
     bootserver=192.168.1.1, rootserver=192.168.1.1, rootpath=
NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.
Looking up port of RPC 100003/2 on 192.168.1.1
eth0: Link is Up
eth0: Speed: 100, Full duplex.
Looking up port of RPC 100005/1 on 192.168.1.1
VFS: Mounted root (nfs filesystem).
Freeing unused kernel memory: 232k init
modprobe: modprobe: Can't open dependencies 
file /lib/modules/2.4.25/modules.dep (No such file or directory)
INIT: version 2.84 booting
                Welcome to DENX Embedded Linux Environment
                Press 'I' to enter interactive startup.
Building the cache [  OK  ]
Mounting proc filesystem:  [  OK  ]
Configuring kernel parameters:  [  OK  ]
Setting clock : Wed Feb  8 08:38:58 MET 2006 [  OK  ]
Setting hostname ocotea:  [  OK  ]
modprobe: Can't open dependencies file /lib/modules/2.4.25/modules.dep (No 
such file or directory)
Activating swap partitions:  [  OK  ]
Finding module dependencies:  depmod: Can't 
open /lib/modules/2.4.25/modules.dep for writing
[FAILED]
Checking filesystems
[  OK  ]
Mounting local filesystems:  [  OK  ]
Enabling swap space:  [  OK  ]
modprobe: Can't open dependencies file /lib/modules/2.4.25/modules.dep (No 
such file or directory)
INIT: Entering runlevel: 3
Entering non-interactive startup
Setting network parameters:  [  OK  ]
Bringing up loopback interface:  [  OK  ]
Starting system logger: [  OK  ]
Starting kernel logger: [  OK  ]
Initializing random number generator:  [  OK  ]
Starting portmapper: [  OK  ]
Mounting NFS filesystems:  [  OK  ]
Mounting other filesystems:  [  OK  ]
Starting xinetd: [  OK  ]

ocotea login: 


Best regards,
Stefan

[U-Boot-Users] u-boot kernel parameters

[Andreas Schweigstill]

Dear Bizzu!

Bizzu (sent by Nabble.com) wrote:
 > [another message in HTML]

PLEASE DO *NOT* SEND MESSAGES IN HTML FORMAT TO THIS
MAILING LIST!

I have no problems reading them but there are other people
who can't read them. And I don't like it if someone else
forces me to read messages with certain font settings.

Regards
Andreas Schweigstill

-- 
Dipl.-Phys. Andreas Schweigstill
Schweigstill IT | Embedded Systems
Schauenburgerstra?e 116, D-24118 Kiel, Germany
Phone: (+49) 431 5606-435, Fax: (+49) 431 5606-436
Mobile: (+49) 171 6921973, Web: http://www.schweigstill.de/

[U-Boot-Users] u-boot kernel parameters

[Tattone Tattone]

Andreas,

Sorry about the format.
I thought I set it to text only.
If this current one is not then I will have to use another email machine.
Please let me know if this is better,

Apologize,

Bizzu

On 2/8/06, Andreas Schweigstill <andreas@schweigstill.de> wrote:
> Dear Bizzu!
>
> Bizzu (sent by Nabble.com) wrote:
>  > [another message in HTML]
>
> PLEASE DO *NOT* SEND MESSAGES IN HTML FORMAT TO THIS
> MAILING LIST!
>
> I have no problems reading them but there are other people
> who can't read them. And I don't like it if someone else
> forces me to read messages with certain font settings.
>
> Regards
> Andreas Schweigstill
>
> --
> Dipl.-Phys. Andreas Schweigstill
> Schweigstill IT | Embedded Systems
> Schauenburgerstra?e 116, D-24118 Kiel, Germany
> Phone: (+49) 431 5606-435, Fax: (+49) 431 5606-436
> Mobile: (+49) 171 6921973, Web: http://www.schweigstill.de/
>

[U-Boot-Users] u-boot kernel parameters

[Tattone Tattone]

Thanks Stefan,

I will check it out as soon as I get to work.
These are terrific news.

Thanks again.
Bizzu

On 2/7/06, Stefan Roese <sr@denx.de> wrote:
> On Tuesday 07 February 2006 22:56, Stefan Roese wrote:
> > Hmmm, I am pretty sure Ocotea linuxppc_2_4_devel worked a few month's ago
> > (with U-Boot of course). I will give it a try tomorrow and let you know.
>
> As it seems the current version doesn't compile for ocotea:
>
> make[4]: Entering directory
> `/chroot/server/home/stefan/git/linuxppc_2_4_devel/drivers/net/ibm_emac'
> ppc_4xx-gcc -D__KERNEL__
> -I/chroot/server/home/stefan/git/linuxppc_2_4_devel/include -Wall
> -Wstrict-prototypes -Wno-trigraphs -O2 -fno-strict-aliasing -fno-common
> -fomit-frame-pointer
> -I/chroot/server/home/stefan/git/linuxppc_2_4_devel/arch/ppc -fsigned-char
> -msoft-float -pipe -ffixed-r2 -Wno-uninitialized -mmultiple -mstring
> -Wa,-m405   -nostdinc
> -I /opt/eldk-3.1.1/usr/lib/gcc-lib/ppc-linux/3.3.3/include
> -DKBUILD_BASENAME=ibm_ocp_enet  -c -o ibm_ocp_enet.o ibm_ocp_enet.c
> ibm_ocp_enet.c:158: error: parse error before "__res"
> ibm_ocp_enet.c:158: warning: type defaults to `int' in declaration of `__res'
> ibm_ocp_enet.c:158: warning: data definition has no type or storage class
> ibm_ocp_enet.c: In function `emac_init':
> ibm_ocp_enet.c:1981: error: `bd_t' undeclared (first use in this function)
> ibm_ocp_enet.c:1981: error: (Each undeclared identifier is reported only once
> ibm_ocp_enet.c:1981: error: for each function it appears in.)
> ibm_ocp_enet.c:1981: error: `bd' undeclared (first use in this function)
> make[4]: *** [ibm_ocp_enet.o] Error 1
>
> If you don't get this error, your linuxppc_2_4_devel version is outdated. With
> this small patch below this is fixed and the ocotea boots again:
>
> 71a72
> > #include "asm/ppcboot.h" /* test-only: ocotea build */
>
> ## Booting image at 00200000 ...
>    Image Name:   Linux-2.4.25
>    Created:      2006-02-08   5:44:06 UTC
>    Image Type:   PowerPC Linux Kernel Image (gzip compressed)
>    Data Size:    649445 Bytes = 634.2 kB
>    Load Address: 00000000
>    Entry Point:  00000000
>    Verifying Checksum ... OK
>    Uncompressing Kernel Image ... OK
> Linux version 2.4.25 (stefan at ubuntu) (gcc version 3.3.3 (DENX ELDK 3.1.1
> 3.3.3-9)) #1 Wed Feb 8 06:41:37 CET 2006
> IBM Ocotea port (MontaVista Software, Inc. <source@mvista.com>)
> On node 0 totalpages: 65536
> zone(0): 65536 pages.
> zone(1): 0 pages.
> zone(2): 0 pages.
> Kernel command line: root=/dev/nfs rw nfsroot=192.168.1.1:/opt/eldk/ppc_4xx
> ip=192.168.80.2:192.168.1.1::255.255.0.0:ocotea:eth0:off panic=1
> console=ttyS0,115200
> Calibrating delay loop... 799.53 BogoMIPS
> Memory: 257000k available (976k kernel code, 320k data, 232k init, 0k highmem)
> Dentry cache hash table entries: 32768 (order: 6, 262144 bytes)
> Inode cache hash table entries: 16384 (order: 5, 131072 bytes)
> Mount cache hash table entries: 512 (order: 0, 4096 bytes)
> Buffer cache hash table entries: 16384 (order: 4, 65536 bytes)
> Page-cache hash table entries: 65536 (order: 6, 262144 bytes)
> POSIX conformance testing by UNIFIX
> PCI: Probing PCI hardware
> Linux NET4.0 for Linux 2.4
> Based upon Swansea University Computer Society NET3.039
> Initializing RT netlink socket
> Starting kswapd
> pty: 256 Unix98 ptys configured
> Serial driver version 5.05c (2001-07-08) with MANY_PORTS SHARE_IRQ SERIAL_PCI
> enabled
> ttyS00 at 0xfdfea200 (irq = 0) is a 16550A
> ttyS01 at 0xfdfe9300 (irq = 1) is a 16550A
> Generic RTC Driver v1.07
> emac: IBM OCP EMAC Ethernet driver, version 2.1
> Maintained by Benjamin Herrenschmidt <benh@kernel.crashing.org>
> mal0: Initialized, 8 tx channels, 4 rx channels
> zmii0: input 0 in SMII mode
> eth0: IBM emac, MAC 00:01:73:01:dd:ac
> eth0: Found Generic MII PHY (0x01)
> zmii0: input 1 in SMII mode
> eth1: IBM emac, MAC 00:01:73:01:dd:ad
> eth1: Found Generic MII PHY (0x02)
> zmii0: input 2 in SMII mode
> rgmii0: input 0 in RGMII mode
> eth2: IBM emac, MAC 00:01:73:01:dd:ae
> eth2: Found CIS8201 Gigabit Ethernet PHY (0x10)
> zmii0: input 3 in SMII mode
> rgmii0: input 1 in RGMII mode
> eth3: IBM emac, MAC 00:01:73:01:dd:af
> eth3: Found CIS8201 Gigabit Ethernet PHY (0x18)
> NET4: Linux TCP/IP 1.0 for NET4.0
> IP Protocols: ICMP, UDP, TCP
> IP: routing cache hash table of 2048 buckets, 16Kbytes
> TCP: Hash tables configured (established 16384 bind 32768)
> IP-Config: Complete:
>       device=eth0, addr=192.168.80.2, mask=255.255.0.0, gw=255.255.255.255,
>      host=ocotea, domain=, nis-domain=(none),
>      bootserver=192.168.1.1, rootserver=192.168.1.1, rootpath=
> NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.
> Looking up port of RPC 100003/2 on 192.168.1.1
> eth0: Link is Up
> eth0: Speed: 100, Full duplex.
> Looking up port of RPC 100005/1 on 192.168.1.1
> VFS: Mounted root (nfs filesystem).
> Freeing unused kernel memory: 232k init
> modprobe: modprobe: Can't open dependencies
> file /lib/modules/2.4.25/modules.dep (No such file or directory)
> INIT: version 2.84 booting
>                 Welcome to DENX Embedded Linux Environment
>                 Press 'I' to enter interactive startup.
> Building the cache [  OK  ]
> Mounting proc filesystem:  [  OK  ]
> Configuring kernel parameters:  [  OK  ]
> Setting clock : Wed Feb  8 08:38:58 MET 2006 [  OK  ]
> Setting hostname ocotea:  [  OK  ]
> modprobe: Can't open dependencies file /lib/modules/2.4.25/modules.dep (No
> such file or directory)
> Activating swap partitions:  [  OK  ]
> Finding module dependencies:  depmod: Can't
> open /lib/modules/2.4.25/modules.dep for writing
> [FAILED]
> Checking filesystems
> [  OK  ]
> Mounting local filesystems:  [  OK  ]
> Enabling swap space:  [  OK  ]
> modprobe: Can't open dependencies file /lib/modules/2.4.25/modules.dep (No
> such file or directory)
> INIT: Entering runlevel: 3
> Entering non-interactive startup
> Setting network parameters:  [  OK  ]
> Bringing up loopback interface:  [  OK  ]
> Starting system logger: [  OK  ]
> Starting kernel logger: [  OK  ]
> Initializing random number generator:  [  OK  ]
> Starting portmapper: [  OK  ]
> Mounting NFS filesystems:  [  OK  ]
> Mounting other filesystems:  [  OK  ]
> Starting xinetd: [  OK  ]
>
> ocotea login:
>
>
> Best regards,
> Stefan
>

[U-Boot-Users] u-boot kernel parameters

[Bizzu]

Stefan Roese wrote: 
> 
> On Tuesday 07 February 2006 22:56, Stefan Roese wrote:
>> Hmmm, I am pretty sure Ocotea linuxppc_2_4_devel worked a few month's ago
>> (with U-Boot of course). I will give it a try tomorrow and let you know.
> 
> As it seems the current version doesn't compile for ocotea:
> 
> make[4]: Entering directory 
> `/chroot/server/home/stefan/git/linuxppc_2_4_devel/drivers/net/ibm_emac'
> ppc_4xx-gcc -D__KERNEL__ 
> -I/chroot/server/home/stefan/git/linuxppc_2_4_devel/include -Wall 
> -Wstrict-prototypes -Wno-trigraphs -O2 -fno-strict-aliasing -fno-common 
> -fomit-frame-pointer 
> -I/chroot/server/home/stefan/git/linuxppc_2_4_devel/arch/ppc -fsigned-char 
> -msoft-float -pipe -ffixed-r2 -Wno-uninitialized -mmultiple -mstring 
> -Wa,-m405   -nostdinc 
> -I /opt/eldk-3.1.1/usr/lib/gcc-lib/ppc-linux/3.3.3/include 
> -DKBUILD_BASENAME=ibm_ocp_enet  -c -o ibm_ocp_enet.o ibm_ocp_enet.c
> ibm_ocp_enet.c:158: error: parse error before "__res"
> ibm_ocp_enet.c:158: warning: type defaults to `int' in declaration of
> `__res'
> ibm_ocp_enet.c:158: warning: data definition has no type or storage class
> ibm_ocp_enet.c: In function `emac_init':
> ibm_ocp_enet.c:1981: error: `bd_t' undeclared (first use in this function)
> ibm_ocp_enet.c:1981: error: (Each undeclared identifier is reported only
> once
> ibm_ocp_enet.c:1981: error: for each function it appears in.)
> ibm_ocp_enet.c:1981: error: `bd' undeclared (first use in this function)
> make[4]: *** [ibm_ocp_enet.o] Error 1
> 
> If you don't get this error, your linuxppc_2_4_devel version is outdated.
> With 
> this small patch below this is fixed and the ocotea boots again:
> 
> 71a72
>> #include "asm/ppcboot.h" /* test-only: ocotea build */
> 
> ## Booting image at 00200000 ...
>    Image Name:   Linux-2.4.25
>    Created:      2006-02-08   5:44:06 UTC
>    Image Type:   PowerPC Linux Kernel Image (gzip compressed)
>    Data Size:    649445 Bytes = 634.2 kB
>    Load Address: 00000000
>    Entry Point:  00000000
>    Verifying Checksum ... OK
>    Uncompressing Kernel Image ... OK
> Linux version 2.4.25 (stefan at ubuntu) (gcc version 3.3.3 (DENX ELDK 3.1.1 
> 3.3.3-9)) #1 Wed Feb 8 06:41:37 CET 2006
> IBM Ocotea port (MontaVista Software, Inc. < source@mvista.com>)
> On node 0 totalpages: 65536
> zone(0): 65536 pages.
> zone(1): 0 pages.
> zone(2): 0 pages.
> Kernel command line: root=/dev/nfs rw
> nfsroot=192.168.1.1:/opt/eldk/ppc_4xx 
> ip=192.168.80.2:192.168.1.1::255.255.0.0:ocotea:eth0:off panic=1 
> console=ttyS0,115200
> Calibrating delay loop... 799.53 BogoMIPS
> Memory: 257000k available (976k kernel code, 320k data, 232k init, 0k
> highmem)
> Dentry cache hash table entries: 32768 (order: 6, 262144 bytes)
> Inode cache hash table entries: 16384 (order: 5, 131072 bytes)
> Mount cache hash table entries: 512 (order: 0, 4096 bytes)
> Buffer cache hash table entries: 16384 (order: 4, 65536 bytes)
> Page-cache hash table entries: 65536 (order: 6, 262144 bytes)
> POSIX conformance testing by UNIFIX
> PCI: Probing PCI hardware
> Linux NET4.0 for Linux 2.4
> Based upon Swansea University Computer Society NET3.039
> Initializing RT netlink socket
> Starting kswapd
> pty: 256 Unix98 ptys configured
> Serial driver version 5.05c (2001-07-08) with MANY_PORTS SHARE_IRQ
> SERIAL_PCI 
> enabled
> ttyS00 at 0xfdfea200 (irq = 0) is a 16550A
> ttyS01 at 0xfdfe9300 (irq = 1) is a 16550A
> Generic RTC Driver v1.07
> emac: IBM OCP EMAC Ethernet driver, version 2.1
> Maintained by Benjamin Herrenschmidt < benh@kernel.crashing.org>
> mal0: Initialized, 8 tx channels, 4 rx channels
> zmii0: input 0 in SMII mode
> eth0: IBM emac, MAC 00:01:73:01:dd:ac
> eth0: Found Generic MII PHY (0x01)
> zmii0: input 1 in SMII mode
> eth1: IBM emac, MAC 00:01:73:01:dd:ad
> eth1: Found Generic MII PHY (0x02)
> zmii0: input 2 in SMII mode
> rgmii0: input 0 in RGMII mode
> eth2: IBM emac, MAC 00:01:73:01:dd:ae
> eth2: Found CIS8201 Gigabit Ethernet PHY (0x10)
> zmii0: input 3 in SMII mode
> rgmii0: input 1 in RGMII mode
> eth3: IBM emac, MAC 00:01:73:01:dd:af
> eth3: Found CIS8201 Gigabit Ethernet PHY (0x18)
> NET4: Linux TCP/IP 1.0 for NET4.0
> IP Protocols: ICMP, UDP, TCP
> IP: routing cache hash table of 2048 buckets, 16Kbytes
> TCP: Hash tables configured (established 16384 bind 32768)
> IP-Config: Complete:
>       device=eth0, addr=192.168.80.2, mask=255.255.0.0,
> gw=255.255.255.255,
>      host=ocotea, domain=, nis-domain=(none),
>      bootserver=192.168.1.1, rootserver=192.168.1.1, rootpath=
> NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.
> Looking up port of RPC 100003/2 on 192.168.1.1
> eth0: Link is Up
> eth0: Speed: 100, Full duplex.
> Looking up port of RPC 100005/1 on 192.168.1.1
> VFS: Mounted root (nfs filesystem).
> Freeing unused kernel memory: 232k init
> modprobe: modprobe: Can't open dependencies 
> file /lib/modules/2.4.25/modules.dep (No such file or directory)
> INIT: version 2.84 booting
>                 Welcome to DENX Embedded Linux Environment
>                 Press 'I' to enter interactive startup.
> Building the cache [  OK  ]
> Mounting proc filesystem:  [  OK  ]
> Configuring kernel parameters:  [  OK  ]
> Setting clock : Wed Feb  8 08:38:58 MET 2006 [  OK  ]
> Setting hostname ocotea:  [  OK  ]
> modprobe: Can't open dependencies file /lib/modules/2.4.25/modules.dep (No 
> such file or directory)
> Activating swap partitions:  [  OK  ]
> Finding module dependencies:  depmod: Can't 
> open /lib/modules/2.4.25/modules.dep for writing
> [FAILED]
> Checking filesystems
> [  OK  ]
> Mounting local filesystems:  [  OK  ]
> Enabling swap space:  [  OK  ]
> modprobe: Can't open dependencies file /lib/modules/2.4.25/modules.dep (No 
> such file or directory)
> INIT: Entering runlevel: 3
> Entering non-interactive startup
> Setting network parameters:  [  OK  ]
> Bringing up loopback interface:  [  OK  ]
> Starting system logger: [  OK  ]
> Starting kernel logger: [  OK  ]
> Initializing random number generator:  [  OK  ]
> Starting portmapper: [  OK  ]
> Mounting NFS filesystems:  [  OK  ]
> Mounting other filesystems:  [  OK  ]
> Starting xinetd: [  OK  ]
> 
> ocotea login: 
> 
> 
> Best regards,
> Stefan
> 
> 
> -------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc. Do you grep through log
> files
> for problems?  Stop!  Download the new AJAX search engine that makes
> searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
> http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
> _______________________________________________
> U-Boot-Users mailing list
> U-Boot-Users at lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/u-boot-users
> 
> 
Stephan,
I followed your tracks and got it to boot as you did.
This is just fantastic!
Danke sch?n!
Bizzu
--
View this message in context: http://www.nabble.com/u-boot-kernel-parameters-t1077794.html#a2823509
Sent from the Uboot - Users forum at Nabble.com.

[U-Boot-Users] u-boot kernel parameters

[Simon Yang]

Dear All,

Now I am working on CIS8201 PHY for RGMII mode, I have modified Reg
23(0x17h) from 0000 to 1300, but CIS8201 doesn't work under RGMII mode, are
there other registers I need to set? Please give me your comment. Thanks a
lot!


2006/2/8, Tattone Tattone <tattone@gmail.com>:
>
> Thanks Stefan,
>
> I will check it out as soon as I get to work.
> These are terrific news.
>
> Thanks again.
> Bizzu
>
> On 2/7/06, Stefan Roese <sr@denx.de> wrote:
> > On Tuesday 07 February 2006 22:56, Stefan Roese wrote:
> > > Hmmm, I am pretty sure Ocotea linuxppc_2_4_devel worked a few month's
> ago
> > > (with U-Boot of course). I will give it a try tomorrow and let you
> know.
> >
> > As it seems the current version doesn't compile for ocotea:
> >
> > make[4]: Entering directory
> > `/chroot/server/home/stefan/git/linuxppc_2_4_devel/drivers/net/ibm_emac'
> > ppc_4xx-gcc -D__KERNEL__
> > -I/chroot/server/home/stefan/git/linuxppc_2_4_devel/include -Wall
> > -Wstrict-prototypes -Wno-trigraphs -O2 -fno-strict-aliasing -fno-common
> > -fomit-frame-pointer
> > -I/chroot/server/home/stefan/git/linuxppc_2_4_devel/arch/ppc
> -fsigned-char
> > -msoft-float -pipe -ffixed-r2 -Wno-uninitialized -mmultiple -mstring
> > -Wa,-m405   -nostdinc
> > -I /opt/eldk-3.1.1/usr/lib/gcc-lib/ppc-linux/3.3.3/include
> > -DKBUILD_BASENAME=ibm_ocp_enet  -c -o ibm_ocp_enet.o ibm_ocp_enet.c
> > ibm_ocp_enet.c:158: error: parse error before "__res"
> > ibm_ocp_enet.c:158: warning: type defaults to `int' in declaration of
> `__res'
> > ibm_ocp_enet.c:158: warning: data definition has no type or storage
> class
> > ibm_ocp_enet.c: In function `emac_init':
> > ibm_ocp_enet.c:1981: error: `bd_t' undeclared (first use in this
> function)
> > ibm_ocp_enet.c:1981: error: (Each undeclared identifier is reported only
> once
> > ibm_ocp_enet.c:1981: error: for each function it appears in.)
> > ibm_ocp_enet.c:1981: error: `bd' undeclared (first use in this function)
> > make[4]: *** [ibm_ocp_enet.o] Error 1
> >
> > If you don't get this error, your linuxppc_2_4_devel version is
> outdated. With
> > this small patch below this is fixed and the ocotea boots again:
> >
> > 71a72
> > > #include "asm/ppcboot.h" /* test-only: ocotea build */
> >
> > ## Booting image at 00200000 ...
> >    Image Name:   Linux-2.4.25
> >    Created:      2006-02-08   5:44:06 UTC
> >    Image Type:   PowerPC Linux Kernel Image (gzip compressed)
> >    Data Size:    649445 Bytes = 634.2 kB
> >    Load Address: 00000000
> >    Entry Point:  00000000
> >    Verifying Checksum ... OK
> >    Uncompressing Kernel Image ... OK
> > Linux version 2.4.25 (stefan at ubuntu) (gcc version 3.3.3 (DENX ELDK 3.1.1
> > 3.3.3-9)) #1 Wed Feb 8 06:41:37 CET 2006
> > IBM Ocotea port (MontaVista Software, Inc. <source@mvista.com>)
> > On node 0 totalpages: 65536
> > zone(0): 65536 pages.
> > zone(1): 0 pages.
> > zone(2): 0 pages.
> > Kernel command line: root=/dev/nfs rw nfsroot=
> 192.168.1.1:/opt/eldk/ppc_4xx
> > ip=192.168.80.2:192.168.1.1::255.255.0.0:ocotea:eth0:off panic=1
> > console=ttyS0,115200
> > Calibrating delay loop... 799.53 BogoMIPS
> > Memory: 257000k available (976k kernel code, 320k data, 232k init, 0k
> highmem)
> > Dentry cache hash table entries: 32768 (order: 6, 262144 bytes)
> > Inode cache hash table entries: 16384 (order: 5, 131072 bytes)
> > Mount cache hash table entries: 512 (order: 0, 4096 bytes)
> > Buffer cache hash table entries: 16384 (order: 4, 65536 bytes)
> > Page-cache hash table entries: 65536 (order: 6, 262144 bytes)
> > POSIX conformance testing by UNIFIX
> > PCI: Probing PCI hardware
> > Linux NET4.0 for Linux 2.4
> > Based upon Swansea University Computer Society NET3.039
> > Initializing RT netlink socket
> > Starting kswapd
> > pty: 256 Unix98 ptys configured
> > Serial driver version 5.05c (2001-07-08) with MANY_PORTS SHARE_IRQ
> SERIAL_PCI
> > enabled
> > ttyS00 at 0xfdfea200 (irq = 0) is a 16550A
> > ttyS01 at 0xfdfe9300 (irq = 1) is a 16550A
> > Generic RTC Driver v1.07
> > emac: IBM OCP EMAC Ethernet driver, version 2.1
> > Maintained by Benjamin Herrenschmidt <benh@kernel.crashing.org>
> > mal0: Initialized, 8 tx channels, 4 rx channels
> > zmii0: input 0 in SMII mode
> > eth0: IBM emac, MAC 00:01:73:01:dd:ac
> > eth0: Found Generic MII PHY (0x01)
> > zmii0: input 1 in SMII mode
> > eth1: IBM emac, MAC 00:01:73:01:dd:ad
> > eth1: Found Generic MII PHY (0x02)
> > zmii0: input 2 in SMII mode
> > rgmii0: input 0 in RGMII mode
> > eth2: IBM emac, MAC 00:01:73:01:dd:ae
> > eth2: Found CIS8201 Gigabit Ethernet PHY (0x10)
> > zmii0: input 3 in SMII mode
> > rgmii0: input 1 in RGMII mode
> > eth3: IBM emac, MAC 00:01:73:01:dd:af
> > eth3: Found CIS8201 Gigabit Ethernet PHY (0x18)
> > NET4: Linux TCP/IP 1.0 for NET4.0
> > IP Protocols: ICMP, UDP, TCP
> > IP: routing cache hash table of 2048 buckets, 16Kbytes
> > TCP: Hash tables configured (established 16384 bind 32768)
> > IP-Config: Complete:
> >       device=eth0, addr=192.168.80.2, mask=255.255.0.0, gw=
> 255.255.255.255,
> >      host=ocotea, domain=, nis-domain=(none),
> >      bootserver=192.168.1.1, rootserver=192.168.1.1, rootpath=
> > NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.
> > Looking up port of RPC 100003/2 on 192.168.1.1
> > eth0: Link is Up
> > eth0: Speed: 100, Full duplex.
> > Looking up port of RPC 100005/1 on 192.168.1.1
> > VFS: Mounted root (nfs filesystem).
> > Freeing unused kernel memory: 232k init
> > modprobe: modprobe: Can't open dependencies
> > file /lib/modules/2.4.25/modules.dep (No such file or directory)
> > INIT: version 2.84 booting
> >                 Welcome to DENX Embedded Linux Environment
> >                 Press 'I' to enter interactive startup.
> > Building the cache [  OK  ]
> > Mounting proc filesystem:  [  OK  ]
> > Configuring kernel parameters:  [  OK  ]
> > Setting clock : Wed Feb  8 08:38:58 MET 2006 [  OK  ]
> > Setting hostname ocotea:  [  OK  ]
> > modprobe: Can't open dependencies file /lib/modules/2.4.25/modules.dep
> (No
> > such file or directory)
> > Activating swap partitions:  [  OK  ]
> > Finding module dependencies:  depmod: Can't
> > open /lib/modules/2.4.25/modules.dep for writing
> > [FAILED]
> > Checking filesystems
> > [  OK  ]
> > Mounting local filesystems:  [  OK  ]
> > Enabling swap space:  [  OK  ]
> > modprobe: Can't open dependencies file /lib/modules/2.4.25/modules.dep
> (No
> > such file or directory)
> > INIT: Entering runlevel: 3
> > Entering non-interactive startup
> > Setting network parameters:  [  OK  ]
> > Bringing up loopback interface:  [  OK  ]
> > Starting system logger: [  OK  ]
> > Starting kernel logger: [  OK  ]
> > Initializing random number generator:  [  OK  ]
> > Starting portmapper: [  OK  ]
> > Mounting NFS filesystems:  [  OK  ]
> > Mounting other filesystems:  [  OK  ]
> > Starting xinetd: [  OK  ]
> >
> > ocotea login:
> >
> >
> > Best regards,
> > Stefan
> >
>
>
> -------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc. Do you grep through log
> files
> for problems?  Stop!  Download the new AJAX search engine that makes
> searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
> http://sel.as-us.falkag.net/sel?cmdlnk&kid\x103432&bid#0486&dat\x121642
> _______________________________________________
> U-Boot-Users mailing list
> U-Boot-Users at lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/u-boot-users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.denx.de/pipermail/u-boot/attachments/20060215/cdfa6961/attachment.htm 

[U-Boot-Users] u-boot kernel parameters

[Travis B. Sawyer]

Simon Yang wrote:
> Dear All,
>  
> Now I am working on CIS8201 PHY for RGMII mode, I have modified Reg 
> 23(0x17h) from 0000 to 1300, but CIS8201 doesn't work under RGMII 
> mode, are there other registers I need to set? Please give me your 
> comment. Thanks a lot! 
> 
Simon:
If you're using the ocotea, phy reg 0x17 should be written with 0x1000 
for rgmii mode, not 0x1300.  0x300 enables clock skewing for boards with 
short etch, like the Sandburst Metrobox and Karef boards.  The ocotea 
has full length etch and doesn't (or rather should not) use clock skewing.

Das U-Boot current source should 'just work' on the ocotea board.

(I can't verify the current source as I haven't done a git sync since 
Stefan merged/fixed the 4xx files, too many time constraints here at 
work, so I'm working with an 'older' tree).

-travis

[U-Boot-Users] u-boot kernel parameters

[Bizzu]

Das U-Boot current source should 'just work' on the ocotea board.

Travis,
I am not sure I understand the question from Simon entirely but:
I am booting the 2.4 head with the u-boot head on Ocotea.
U-boot is in flash and linux in flash or tftp.
All devices on the board accounted for.
Bizzu
--
View this message in context: http://www.nabble.com/u-boot-kernel-parameters-t1077794.html#a2956582
Sent from the Uboot - Users forum at Nabble.com.

[U-Boot-Users] u-boot kernel parameters

[Simon Yang]

Hi Travis,

Thanks for your reply. I still have a question, for rgmii mode the bits 11:9
of phy reg 0x17 should be 001 which means the I/O pin operate from 2.5V,
default is 3.3V if the value of bits 11:9 is 000, so whether I should
set reg 0x17 to 1200.

The cpu we use is MPC8349E, I set the reg ECNTRL to 0x00001010 , I can
meature the signals on TSEC1_GTX_CLK, Tx_EN and Tx_D[0:3], the RGMII should
operate on 2.5v but the voltage I meature on Tx_D is 3.3v , so there is a
problem  that the value of reg SICRH(in local memory offset is 0x118) is
always 00000002(GMII mode and RGMII mode), but in the datasheet of MPC8349E
the bits 30 and 31of reg SICRH (TSOBI1 and TSOBI2) controls the output
buffer impedance of the TSEC1and TSEC2 output signals, so I think the value
I get is not what I expected. Cany anybody tell me how the reg SICRH get
this value? Seems SICRH only use in /cpu/mpc83xx/cpu_init.c file. Thanks a
lot!


2006/2/15, Travis B. Sawyer <tsawyer@sandburst.com>:
>
> Simon Yang wrote:
> > Dear All,
> >
> > Now I am working on CIS8201 PHY for RGMII mode, I have modified Reg
> > 23(0x17h) from 0000 to 1300, but CIS8201 doesn't work under RGMII
> > mode, are there other registers I need to set? Please give me your
> > comment. Thanks a lot!
> >
> Simon:
> If you're using the ocotea, phy reg 0x17 should be written with 0x1000
> for rgmii mode, not 0x1300.  0x300 enables clock skewing for boards with
> short etch, like the Sandburst Metrobox and Karef boards.  The ocotea
> has full length etch and doesn't (or rather should not) use clock skewing.
>
>
> Das U-Boot current source should 'just work' on the ocotea board.
>
> (I can't verify the current source as I haven't done a git sync since
> Stefan merged/fixed the 4xx files, too many time constraints here at
> work, so I'm working with an 'older' tree).
>
> -travis
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.denx.de/pipermail/u-boot/attachments/20060217/3c5a4b9c/attachment.htm