In message <000d01c38c5b$99ebdcf0$0202a8c0 at homevl9biy3v7e> you wrote:
>
> > This patch is not really useful. Instead of redefining the structure
> > yourself you should simply #include .
>
> Thanks. (Will you change it in next release?)
I am not in the position to make such a change.
Bes
- Original Message -
From: "Wolfgang Denk" <[EMAIL PROTECTED]>
To: "Jacky Lam"
Cc:
Sent: Tuesday, October 07, 2003 6:40 AM
Subject: Re: Walnut boot problem solved
> Hi Jacky,
>
> in message <009a01c38bb6$ceb84f40$2803050a at JackyLam> you wro
Hi Jacky,
in message <009a01c38bb6$ceb84f40$2803050a at 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
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 p
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 pa
