linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "Jacky Lam" <jackylam@astri.org>
To: <linuxppc-embedded@lists.linuxppc.org>
Subject: Walnut boot problem solved
Date: Mon, 6 Oct 2003 11:06:14 +0800	[thread overview]
Message-ID: <009a01c38bb6$ceb84f40$2803050a@JackyLam> (raw)

[-- 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.

             reply	other threads:[~2003-10-06  3:06 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-06  3:06 Jacky Lam [this message]
2003-10-06 22:40 ` Walnut boot problem solved Wolfgang Denk
2003-10-06 22:45   ` Jacky Lam
2003-10-07  7:39     ` Wolfgang Denk
  -- strict thread matches above, loose matches on Subject: below --
2003-10-06  7:37 Jacky Lam

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='009a01c38bb6$ceb84f40$2803050a@JackyLam' \
    --to=jackylam@astri.org \
    --cc=linuxppc-embedded@lists.linuxppc.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).