Linux booting problems in the IBM Bubinga Board

Linux booting problems in the IBM Bubinga Board

[Nivedita Pitre]

I am using U-boot to boot linux kernel on the IBM Bubinga (405EP board). Using kernel version 2.6.7, which has a default config file for this board. Changed the board info structure to match u-boot's board information structure. Using the mkimage utility in u-boot to create a uImage, which I am downloading via tftpserver to u-boot. Uboot recognizes this image, and jumps into the kernel, after which the system hangs. The last message I see is uncompressing kernel -- OK. I read the manual for u-boot, which suggests modifying the board information structure, and I did that, still have the same problem. After this, I turned on kernel hacking in the config, the CONFIG_SERIAL_TEXT_DEBUG on. This allows me to see some progress on the serial port, the ppc_mach_dep calls output some messages. This tells me that code reaches in start_kernel, however, after console_init, the serial port dies. I assume this is because we initialize the serial port, and turn off early debug. I commented o
 u!
t this part, and enabled early debug messages to continue throughout the start_kernel routine. Also added my own debug messages. So far as I can see, the code goes through till the end of start_kernel without hanging. This makes me think this is a serial port problem in the kernel, but I cannot think what it is. I have configured the UART_TTYSO, SERIAL_CONSOLE, and 8250 drivers in the .config file, and so far as I can see, all the relevant .o files are created, so these drivers are getting compiled. Does anyone have any suggestions for debugging. I am setting up BDI200 to debug this problem. Let me know if there is something else that I am not doing right.

Thanks.


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

Re: Linux booting problems in the IBM Bubinga Board

[Wolfgang Denk]

In message <s1110fc4.060@gateway.p-com.com> you wrote:
>
> I am using U-boot to boot linux kernel on the IBM Bubinga (405EP board). Using kernel version 2.6.7, which has a default config file for this board. Changed the board info structure to match u-boot's board information structure. Using the mkimage utilit

PLEASE don't use such long lines. Press ENTER after some 60...70
characters or so.

> ach_dep calls output some messages. This tells me that code reaches in start_kernel, however, after console_init, the serial port dies. I assume this is because we initialize the serial port, and turn off early debug. I commented o

Did you pass some "console=..." boot argument?

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
One difference between a man and a machine is that a machine is quiet
when well oiled.

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

How to remove JFFS2 'Making dirty' display on RPXlite DW?

[Song Sam]

Hi,

When creating a JFFS2 filesytem with DENX SELF ramdisk
as follows,the target displayed some wired
message,what would be problem be?

=====================================================

After unpacking SELF,I use the following command to
create a jffs2 filesystem:

eraseall /dev/mtd3

mkfs.jffs2 -r /tmp/tmp -e 0x10000 -o image.jffs2 -b

dd if=image.jffs2 of=/dev/mtd3 bs=256k

mount -t jffs2 /dev/mtdblock3 /mnt

====================================================

U-Boot 1.1.2 (Jul 15 2004 - 17:26:45)

CPU:   PPC823EZTnnB2 at 48 MHz: 16 kB I-Cache 8 kB
D-Cache
Board: RPXlite_DW
DRAM:  64 MB
FLASH: 16 MB
In:    serial
Out:   serial
Err:   serial
Net:   SCC ETHERNET
-boot>pri
bootcmd=run flash_self
baudrate=9600
loads_echo=1
ethaddr=00:10:EC:00:37:5B
netdev=eth0
addip=setenv bootargs $(bootargs)
ip=$(ipaddr):$(serverip):$(gatewayip):$(netmask):$(hostname):$(netdev):off
panic=1
flash_nfs=run nfsargs addip;bootm $(kernel_addr)
net_nfs=tftp 200000 $(bootfile);run nfsargs
addip;bootm
ethact=SCC ETHERNET
ramdisk_addr=ff900000
rootpath=/workspace/myfilesystem/target/
bootfile=uImage.rpxmtd
nfsargs=setenv bootargs console=ttyS0,9600
root=/dev/nfs rw nfsroot=$(serverip):$(rootpath)
flash_self=run ramargs addip;bootm $(kernel_addr)
ramargs=setenv bootargs console=ttyS0,9600
root=/dev/mtdblock3 rw
stdin=serial
stdout=serial
stderr=serial
filesize=abfeb
fileaddr=100000
gatewayip=172.16.115.254
netmask=255.255.255.0
ipaddr=172.16.115.7
serverip=172.16.115.6
kernel_addr=ff080000

Environment size: 806/32764 bytes
u-boot>run flash_self
## Booting image at ff080000 ...
   Image Name:   Linux-2.4.18_mvl30-rpxlite
   Image Type:   PowerPC Linux Kernel Image (gzip
compressed)
   Data Size:    704427 Bytes = 687.9 kB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK
   Uncompressing Kernel Image ... OK
...
Kernel command line: console=ttyS0,9600
root=/dev/mtdblock3 rw
ip=172.16.115.7:172.16.115.6:172.16.115.254:255.255.255.0::eth0:off
panic=1
Decrementer Frequency = 180000000/60
...
RPX Lite or CLLF flash device: 1000000 at ff000000
 Amd/Fujitsu Extended Query Table v1.2 at 0x0040
number of CFI chips: 1
Creating 3 MTD partitions on "RPX":
0x00000000-0x00080000 : "RPXLITE flash U-BOOT
partition"
0x00080000-0x00200000 : "RPXLITE flash KERNEL
partition"
0x00200000-0x01000000 : "RPXLITE flash APPLICATION
partition"
...
IP-Config: Complete:
      device=eth0, addr=172.16.115.7,
mask=255.255.255.0, gw=172.16.115.254,
     host=172.16.115.7, domain=, nis-domain=(none),
     bootserver=172.16.115.6, rootserver=172.16.115.6,
rootpath=
NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.
jffs2_scan_empty(): Empty block at 0x0000fffc ends at
0x00010000 (with 0x1985e002)! Marking dirty
jffs2_scan_empty(): Empty block at 0x0001fffc ends at
0x00020000 (with 0x1985e002)! Marking dirty
jffs2_scan_empty(): Empty block at 0x0002fffc ends at
0x00030000 (with 0x1985e002)! Marking dirty
jffs2_scan_empty(): Empty block at 0x0004ff60 ends at
0x00050000 (with 0x1985e002)! Marking dirty
jffs2_scan_empty(): Empty block at 0x0005fffc ends at
0x00060000 (with 0x1985e002)! Marking dirty
jffs2_scan_empty(): Empty block at 0x0006ff78 ends at
0x00070000 (with 0x1985e002)! Marking dirty
jffs2_scan_empty(): Empty block at 0x0008fffc ends at
0x00090000 (with 0x1985e002)! Marking dirty
jffs2_scan_empty(): Empty block at 0x0009fffc ends at
0x000a0000 (with 0x1985e002)! Marking dirty
jffs2_scan_empty(): Empty block at 0x000afffc ends at
0x000b0000 (with 0x1985e002)! Marking dirty
jffs2_scan_empty(): Empty block at 0x000cfffc ends at
0x000d0000 (with 0x1985e002)! Marking dirty
jffs2_scan_empty(): Empty block at 0x000dfffc ends at
0x000e0000 (with 0x1985e002)! Marking dirty
jffs2_scan_empty(): Empty block at 0x000efffc ends at
0x000f0000 (with 0x1985e002)! Marking dirty
jffs2_scan_empty(): Empty block at 0x0010fffc ends at
0x00110000 (with 0x1985e002)! Marking dirty
jffs2_scan_empty(): Empty block at 0x0011fffc ends at
0x00120000 (with 0x1985e002)! Marking dirty
jffs2_scan_empty(): Empty block at 0x0014fffc ends at
0x00150000 (with 0x1985e002)! Marking dirty
jffs2_scan_empty(): Empty block at 0x0015fffc ends at
0x00160000 (with 0x1985e002)! Marking dirty
jffs2_scan_empty(): Empty block at 0x0016fffc ends at
0x00170000 (with 0x1985e002)! Marking dirty
jffs2_scan_empty(): Empty block at 0x0018fffc ends at
0x00190000 (with 0x1985e002)! Marking dirty
jffs2_scan_empty(): Empty block at 0x0019fffc ends at
0x001a0000 (with 0x1985e002)! Marking dirty
jffs2_scan_empty(): Empty block at 0x001afffc ends at
0x001b0000 (with 0x1985e002)! Marking dirty
jffs2_scan_empty(): Empty block at 0x001cfffc ends at
0x001d0000 (with 0x1985e002)! Marking dirty
jffs2_scan_empty(): Empty block at 0x001dffd0 ends at
0x001e0000 (with 0x1985e002)! Marking dirty
jffs2_scan_empty(): Empty block at 0x001efffc ends at
0x001f0000 (with 0x1985e002)! Marking dirty
jffs2_scan_empty(): Empty block at 0x0020fffc ends at
0x00210000 (with 0x1985e002)! Marking dirty
jffs2_scan_empty(): Empty block at 0x0021fffc ends at
0x00220000 (with 0x1985e002)! Marking dirty
VFS: Mounted root (jffs2 filesystem).
Freeing unused kernel memory: 76k init
My application is running ... Sam Song

BusyBox v0.60.1 (2002.10.24-04:52+0000) Built-in shell
(msh)
Enter 'help' for a list of built-in commands.

#        Feb.7,2004
Hello Shanghai Univ.
Hi Everybody!

---------------------------------------------

The 'Making dirty' display took up about 5 seconds.I
need to remove them.

Thanks for any input!

Best regards,

Sam

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

Re: How to remove JFFS2 'Making dirty' display on RPXlite DW?

[David Ho]

> When creating a JFFS2 filesytem with DENX SELF ramdisk
> as follows,the target displayed some wired
> message,what would be problem be?
>
> =====================================================
>
> After unpacking SELF,I use the following command to
> create a jffs2 filesystem:
>
> eraseall /dev/mtd3
>
> mkfs.jffs2 -r /tmp/tmp -e 0x10000 -o image.jffs2 -b
>
> dd if=image.jffs2 of=/dev/mtd3 bs=256k
>
> mount -t jffs2 /dev/mtdblock3 /mnt
>
> ====================================================

What is the block size you specified when you do a mkfs.jffs2?

It has to match with your flash erase block size.  Care should be taken if
you have paralle banks.

I'm not sure this is your problem but it is a problem I ran into.

David

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

Re: How to remove JFFS2 'Making dirty' display on RPXlite DW?

[Mark Chambers]

BTW, I've been able to skip a step by just:

mkfs.jffs2  -o /dev/mtd3

I think your problem is a mis-match in block size.

Mark Chambers

----- Original Message -----
From: "Song Sam" <samlinuxppc@yahoo.com.cn>
To: <linuxppc-embedded@lists.linuxppc.org>
Sent: Thursday, August 05, 2004 12:21 AM
Subject: How to remove JFFS2 'Making dirty' display on RPXlite DW?


>
> Hi,
>
> When creating a JFFS2 filesytem with DENX SELF ramdisk
> as follows,the target displayed some wired
> message,what would be problem be?
>
> =====================================================
>
> After unpacking SELF,I use the following command to
> create a jffs2 filesystem:
>
> eraseall /dev/mtd3
>
> mkfs.jffs2 -r /tmp/tmp -e 0x10000 -o image.jffs2 -b
>
> dd if=image.jffs2 of=/dev/mtd3 bs=256k
>
> mount -t jffs2 /dev/mtdblock3 /mnt
>
> ====================================================
>
> U-Boot 1.1.2 (Jul 15 2004 - 17:26:45)
>
> CPU:   PPC823EZTnnB2 at 48 MHz: 16 kB I-Cache 8 kB
> D-Cache
> Board: RPXlite_DW
> DRAM:  64 MB
> FLASH: 16 MB
> In:    serial
> Out:   serial
> Err:   serial
> Net:   SCC ETHERNET
> -boot>pri
> bootcmd=run flash_self
> baudrate=9600
> loads_echo=1
> ethaddr=00:10:EC:00:37:5B
> netdev=eth0
> addip=setenv bootargs $(bootargs)
> ip=$(ipaddr):$(serverip):$(gatewayip):$(netmask):$(hostname):$(netdev):off
> panic=1
> flash_nfs=run nfsargs addip;bootm $(kernel_addr)
> net_nfs=tftp 200000 $(bootfile);run nfsargs
> addip;bootm
> ethact=SCC ETHERNET
> ramdisk_addr=ff900000
> rootpath=/workspace/myfilesystem/target/
> bootfile=uImage.rpxmtd
> nfsargs=setenv bootargs console=ttyS0,9600
> root=/dev/nfs rw nfsroot=$(serverip):$(rootpath)
> flash_self=run ramargs addip;bootm $(kernel_addr)
> ramargs=setenv bootargs console=ttyS0,9600
> root=/dev/mtdblock3 rw
> stdin=serial
> stdout=serial
> stderr=serial
> filesize=abfeb
> fileaddr=100000
> gatewayip=172.16.115.254
> netmask=255.255.255.0
> ipaddr=172.16.115.7
> serverip=172.16.115.6
> kernel_addr=ff080000
>
> Environment size: 806/32764 bytes
> u-boot>run flash_self
> ## Booting image at ff080000 ...
>    Image Name:   Linux-2.4.18_mvl30-rpxlite
>    Image Type:   PowerPC Linux Kernel Image (gzip
> compressed)
>    Data Size:    704427 Bytes = 687.9 kB
>    Load Address: 00000000
>    Entry Point:  00000000
>    Verifying Checksum ... OK
>    Uncompressing Kernel Image ... OK
> ...
> Kernel command line: console=ttyS0,9600
> root=/dev/mtdblock3 rw
> ip=172.16.115.7:172.16.115.6:172.16.115.254:255.255.255.0::eth0:off
> panic=1
> Decrementer Frequency = 180000000/60
> ...
> RPX Lite or CLLF flash device: 1000000 at ff000000
>  Amd/Fujitsu Extended Query Table v1.2 at 0x0040
> number of CFI chips: 1
> Creating 3 MTD partitions on "RPX":
> 0x00000000-0x00080000 : "RPXLITE flash U-BOOT
> partition"
> 0x00080000-0x00200000 : "RPXLITE flash KERNEL
> partition"
> 0x00200000-0x01000000 : "RPXLITE flash APPLICATION
> partition"
> ...
> IP-Config: Complete:
>       device=eth0, addr=172.16.115.7,
> mask=255.255.255.0, gw=172.16.115.254,
>      host=172.16.115.7, domain=, nis-domain=(none),
>      bootserver=172.16.115.6, rootserver=172.16.115.6,
> rootpath=
> NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.
> jffs2_scan_empty(): Empty block at 0x0000fffc ends at
> 0x00010000 (with 0x1985e002)! Marking dirty
> jffs2_scan_empty(): Empty block at 0x0001fffc ends at
> 0x00020000 (with 0x1985e002)! Marking dirty
> jffs2_scan_empty(): Empty block at 0x0002fffc ends at
> 0x00030000 (with 0x1985e002)! Marking dirty
> jffs2_scan_empty(): Empty block at 0x0004ff60 ends at
> 0x00050000 (with 0x1985e002)! Marking dirty
> jffs2_scan_empty(): Empty block at 0x0005fffc ends at
> 0x00060000 (with 0x1985e002)! Marking dirty
> jffs2_scan_empty(): Empty block at 0x0006ff78 ends at
> 0x00070000 (with 0x1985e002)! Marking dirty
> jffs2_scan_empty(): Empty block at 0x0008fffc ends at
> 0x00090000 (with 0x1985e002)! Marking dirty
> jffs2_scan_empty(): Empty block at 0x0009fffc ends at
> 0x000a0000 (with 0x1985e002)! Marking dirty
> jffs2_scan_empty(): Empty block at 0x000afffc ends at
> 0x000b0000 (with 0x1985e002)! Marking dirty
> jffs2_scan_empty(): Empty block at 0x000cfffc ends at
> 0x000d0000 (with 0x1985e002)! Marking dirty
> jffs2_scan_empty(): Empty block at 0x000dfffc ends at
> 0x000e0000 (with 0x1985e002)! Marking dirty
> jffs2_scan_empty(): Empty block at 0x000efffc ends at
> 0x000f0000 (with 0x1985e002)! Marking dirty
> jffs2_scan_empty(): Empty block at 0x0010fffc ends at
> 0x00110000 (with 0x1985e002)! Marking dirty
> jffs2_scan_empty(): Empty block at 0x0011fffc ends at
> 0x00120000 (with 0x1985e002)! Marking dirty
> jffs2_scan_empty(): Empty block at 0x0014fffc ends at
> 0x00150000 (with 0x1985e002)! Marking dirty
> jffs2_scan_empty(): Empty block at 0x0015fffc ends at
> 0x00160000 (with 0x1985e002)! Marking dirty
> jffs2_scan_empty(): Empty block at 0x0016fffc ends at
> 0x00170000 (with 0x1985e002)! Marking dirty
> jffs2_scan_empty(): Empty block at 0x0018fffc ends at
> 0x00190000 (with 0x1985e002)! Marking dirty
> jffs2_scan_empty(): Empty block at 0x0019fffc ends at
> 0x001a0000 (with 0x1985e002)! Marking dirty
> jffs2_scan_empty(): Empty block at 0x001afffc ends at
> 0x001b0000 (with 0x1985e002)! Marking dirty
> jffs2_scan_empty(): Empty block at 0x001cfffc ends at
> 0x001d0000 (with 0x1985e002)! Marking dirty
> jffs2_scan_empty(): Empty block at 0x001dffd0 ends at
> 0x001e0000 (with 0x1985e002)! Marking dirty
> jffs2_scan_empty(): Empty block at 0x001efffc ends at
> 0x001f0000 (with 0x1985e002)! Marking dirty
> jffs2_scan_empty(): Empty block at 0x0020fffc ends at
> 0x00210000 (with 0x1985e002)! Marking dirty
> jffs2_scan_empty(): Empty block at 0x0021fffc ends at
> 0x00220000 (with 0x1985e002)! Marking dirty
> VFS: Mounted root (jffs2 filesystem).
> Freeing unused kernel memory: 76k init
> My application is running ... Sam Song
>
> BusyBox v0.60.1 (2002.10.24-04:52+0000) Built-in shell
> (msh)
> Enter 'help' for a list of built-in commands.
>
> #        Feb.7,2004
> Hello Shanghai Univ.
> Hi Everybody!
>
> ---------------------------------------------
>
> The 'Making dirty' display took up about 5 seconds.I
> need to remove them.
>
> Thanks for any input!
>
> Best regards,
>
> Sam
>
>


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

Re: How to remove JFFS2 'Making dirty' display on RPXlite DW?

[David Woodhouse]

On Thu, 2004-08-05 at 12:21 +0800, Song Sam wrote:
> Hi,
>
> When creating a JFFS2 filesytem with DENX SELF ramdisk
> as follows,the target displayed some wired
> message,what would be problem be?
>
> =====================================================
>
> After unpacking SELF,I use the following command to
> create a jffs2 filesystem:
>
> eraseall /dev/mtd3
>
> mkfs.jffs2 -r /tmp/tmp -e 0x10000 -o image.jffs2 -b

Looks like you should have said '-e 256KiB' or '-e 0x40000' instead.

--
dwmw2


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

Re: How to remove JFFS2 'Making dirty' display on RPXlite DW?

[David Woodhouse]

On Thu, 2004-08-05 at 10:12 -0400, Mark Chambers wrote:
> BTW, I've been able to skip a step by just:
>
> mkfs.jffs2  -o /dev/mtd3

It would be cute if someone would make that work as expected -- get the
right blocksize, erase and prepare the remainder of the device, etc.

We haven't done it yet though.

--
dwmw2


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

Re: How to remove JFFS2 'Making dirty' display on RPXlite DW?

[Mark Chambers]

Well, I've done it.  Dumb luck?  eraseall, then the command as shown, but I
don't remember the rest of the options.
I was just playing with jffs2 to compare performance.  I know I got a
mountable, bootable, read/write-able file system,
but wasn't extensively tested.  Actually, I did a fair amount of add/deletes
in order to guage mount time slowdown...

Mark Chambers

----- Original Message -----
From: "David Woodhouse" <dwmw2@infradead.org>
To: "Mark Chambers" <markc@mail.com>
Cc: "Song Sam" <samlinuxppc@yahoo.com.cn>;
<linuxppc-embedded@lists.linuxppc.org>
Sent: Thursday, August 05, 2004 10:48 AM
Subject: Re: How to remove JFFS2 'Making dirty' display on RPXlite DW?


> On Thu, 2004-08-05 at 10:12 -0400, Mark Chambers wrote:
> > BTW, I've been able to skip a step by just:
> >
> > mkfs.jffs2  -o /dev/mtd3
>
> It would be cute if someone would make that work as expected -- get the
> right blocksize, erase and prepare the remainder of the device, etc.
>
> We haven't done it yet though.
>
> --
> dwmw2
>


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

Re: How to remove JFFS2 'Making dirty' display on RPXlite DW?

[David Woodhouse]

On Thu, 2004-08-05 at 10:59 -0400, Mark Chambers wrote:
> Well, I've done it.  Dumb luck?  eraseall, then the command as shown, but I
> don't remember the rest of the options.

Yeah -- that should work as well as just making an image with the same
options, then writing it. But it would be nicer if it'd do the eraseall,
and interrogate the device to find its characteristics.

Please don't top-post.

--
dwmw2


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

Re: How to remove JFFS2 'Making dirty' display on RPXlite DW?

[Song Sam]

David Woodhouse <dwmw2@infradead.org> wrote£º
> > After unpacking SELF,I use the following command to create a jffs2
> > filesystem:
> >
> > eraseall /dev/mtd3
> >
> > mkfs.jffs2 -r /tmp/tmp -e 0x10000 -o image.jffs2 -b
>
> Looks like you should have said '-e 256KiB' or '-e 0x40000' instead.

After taking your advice,the JFFS2 complaint
disappeared.The command I tested is as follows,it
worked fine:

eraseall /dev/mtd3

mkfs.jffs2 -r /tmp/tmp -e 0x40000 -o /dev/mtd3 -b

Thanks for you all.

Next,I will take Wolfgang's advice on decreasing boot
time to create an ext2+mini_fo filesystem based on MTD
 to get a faster boot process.By now the boot time of
my target is 18-20
seconds(48MHZ[CORE]+24MHZ[BUS]+uncompressed
kernel+JFFS2).

Best regards,

Sam

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

Re: How to remove JFFS2 'Making dirty' display on RPXlite DW?

[David Woodhouse]

On Sat, 2004-08-07 at 15:39 +0800, Song Sam wrote:
> Next,I will take Wolfgang's advice on decreasing boot
> time to create an ext2+mini_fo filesystem based on MTD
>  to get a faster boot process.By now the boot time of
> my target is 18-20
> seconds(48MHZ[CORE]+24MHZ[BUS]+uncompressed
> kernel+JFFS2).

The JFFS2 code in the 2.6 kernel can give about an order of magnitude
improvement in mount time. It's a lot less naïve than the 2.4 code.

--
dwmw2


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

Re: How to remove JFFS2 'Making dirty' display on RPXlite DW?

[Song Sam]

David Woodhouse <dwmw2@infradead.org> wrote£º
>
> The JFFS2 code in the 2.6 kernel can give about an order of magnitude
> improvement in mount time. It's a lot less naïve than the 2.4 code.

Good hints.But 2.6 cannot boot on 8xx via NFS by
now.How can I make a JFFS2?Beats me.Anyway,I will try
it to see how far I would go ...

Thanks

Sam

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

Re: How to remove JFFS2 'Making dirty' display on RPXlite DW?

[Marcelo Tosatti]

On Sat, Aug 07, 2004 at 10:14:11PM +0800, Song Sam wrote:
>
> David Woodhouse <dwmw2@infradead.org> wrote£º
> >
> > The JFFS2 code in the 2.6 kernel can give about an order of magnitude
> > improvement in mount time. It's a lot less naïve than the 2.4 code.
>
> Good hints.But 2.6 cannot boot on 8xx via NFS by
> now.How can I make a JFFS2?Beats me.Anyway,I will try
> it to see how far I would go ...

Unfortunately v2.6 does not seem to be working properly on m8xx yet.

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