Walnut boot problem solved

Walnut boot problem solved

[Jacky Lam]

[-- Attachment #1: Type: text/plain, Size: 383 bytes --]

Dear all,

    I have figured out why my kernel hanged while booting on Walnut
platform. It is because the structure of board_info is different between
u-boot-0.4.8 and linuxppc-2.4-devel. After syncing the structure, I can boot
up to where the kernel tries to mount the filesystem. Attached is a patch
for the fix.

    Thanks for all help and suggestions.

Best regards,
Jacky Lam

[-- Attachment #2: patch --]
[-- Type: application/octet-stream, Size: 1508 bytes --]

--- walnut.h	Mon Oct  6 11:04:08 2003
+++ walnut.h.orig	Mon Oct  6 11:03:59 2003
@@ -37,26 +37,14 @@
  */
 
 typedef struct board_info {
-        unsigned long bi_memstart;
-        unsigned long bi_memsize;
-        unsigned long bi_flashstart;
-        unsigned long bi_flashsize;
-        unsigned long bi_flashoffset;
-        unsigned long bi_sramstart;
-        unsigned long bi_sramsize;
-        unsigned long bi_bootflags;
-        unsigned long bi_ip_addr;
-        unsigned char bi_enetaddr[6];
-        unsigned short bi_ethspeed;
-        unsigned long bi_intfreq;
-        unsigned long bi_busfreq;
-        unsigned long bi_baudrate;
-        unsigned char bi_s_version[4];
-        unsigned char bi_r_version[32];
-        unsigned int bi_procfreq;
-        unsigned int bi_plb_busfreq;
-        unsigned int bi_pci_busfreq;
-        unsigned char bi_pci_enetaddr[6];
+	unsigned char	 bi_s_version[4];	/* Version of this structure */
+	unsigned char	 bi_r_version[30];	/* Version of the IBM ROM */
+	unsigned int	 bi_memsize;		/* DRAM installed, in bytes */
+	unsigned char	 bi_enetaddr[6];	/* Local Ethernet MAC address */
+	unsigned char	 bi_pci_enetaddr[6];	/* PCI Ethernet MAC address */
+	unsigned int	 bi_intfreq;		/* Processor speed, in Hz */
+	unsigned int	 bi_busfreq;		/* PLB Bus speed, in Hz */
+	unsigned int	 bi_pci_busfreq;	/* PCI Bus speed, in Hz */
 } bd_t;
 
 /* Some 4xx parts use a different timebase frequency from the internal clock.

Re: Walnut boot problem solved

[Wolfgang Denk]

Hi Jacky,

in message <009a01c38bb6$ceb84f40$2803050a@JackyLam> you wrote:
>
>     I have figured out why my kernel hanged while booting on Walnut
> platform. It is because the structure of board_info is different between
> u-boot-0.4.8 and linuxppc-2.4-devel. After syncing the structure, I can boot

Does the fact that this is a FAQ tell you something?

> up to where the kernel tries to mount the filesystem. Attached is a patch
> for the fix.

This patch is not really useful. Instead of redefining the  structure
yourself you should simply #include <asm/ppcboot.h>.

Best regards,

Wolfgang Denk

--
Software Engineering:  Embedded and Realtime Systems,  Embedded Linux
Phone: (+49)-8142-4596-87  Fax: (+49)-8142-4596-88  Email: wd@denx.de
By the way, ALL software projects are done by iterative  prototyping.
Some companies call their prototypes "releases", that's all.

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

Re: Walnut boot problem solved

[Jacky Lam]

----- Original Message -----
From: "Wolfgang Denk" <wd@denx.de>
To: "Jacky Lam" <jackylam@astri.org>
Cc: <linuxppc-embedded@lists.linuxppc.org>
Sent: Tuesday, October 07, 2003 6:40 AM
Subject: Re: Walnut boot problem solved


> Hi Jacky,
>
> in message <009a01c38bb6$ceb84f40$2803050a@JackyLam> you wrote:
> >
> >     I have figured out why my kernel hanged while booting on Walnut
> > platform. It is because the structure of board_info is different between
> > u-boot-0.4.8 and linuxppc-2.4-devel. After syncing the structure, I can
boot
>
> Does the fact that this is a FAQ tell you something?

    No...just my blind guess while tracing the code.
>
> > up to where the kernel tries to mount the filesystem. Attached is a
patch
> > for the fix.
>
> This patch is not really useful. Instead of redefining the  structure
> yourself you should simply #include <asm/ppcboot.h>.

    Thanks. (Will you change it in next release?)

Regards,
Jacky


** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

Re: Walnut boot problem solved

[Wolfgang Denk]

In message <000d01c38c5b$99ebdcf0$0202a8c0@homevl9biy3v7e> you wrote:
>
> > This patch is not really useful. Instead of redefining the  structure
> > yourself you should simply #include <asm/ppcboot.h>.
>
>     Thanks. (Will you change it in next release?)

I am not in the position to make such a change.

Best regards,

Wolfgang Denk

--
Software Engineering:  Embedded and Realtime Systems,  Embedded Linux
Phone: (+49)-8142-4596-87  Fax: (+49)-8142-4596-88  Email: wd@denx.de
Lots of people drink from the wrong bottle sometimes.
	-- Edith Keeler, "The City on the Edge of Forever",
	   stardate unknown

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

Walnut boot problem solved

[Jacky Lam]

Dear all,

    I have figured out why my kernel hanged while booting on Walnut
platform. It is because the structure of board_info is different between
u-boot-0.4.8 and linuxppc-2.4-devel. After syncing the structure, I can boot
up to where the kernel tries to mount the filesystem. Attached is a patch
for the fix.

    Thanks for all help and suggestions.

Best regards,
Jacky Lam


** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/