Zhang,

Unfortunately, I have no experience with the MVL 5.0 release and cannot offer 
any assistance on the matter.  I'm sure there were significant changes to the 
kernel, drivers, etc. between the two releases, but I wouldn't be able to tell 
you what could be causing the different behaviors you are seeing.  I would 
recommend contacting MontaVista to see if they could detail the changes between 
the releases.

Regards,
Daniel

Daniel Allred
Application Processors & Floating Point DSP
________________________________
From: shaofeng zhang [mailto:[email protected]]
Sent: Tuesday, May 05, 2009 9:58 PM
To: Allred, Daniel
Cc: [email protected]
Subject: Some questions about MontaVista Linux

Hi, Daniel,

I am facing some probelms when  I use the MontaVista Linux on my DM6446 EVM.

1. I am use the LargePage Nand Flash (ST's NAND01GR3B2B NAND Flash ) on my 
DM6446 EVM, When I use the MVL4.0 kernel on my board, I found that the kernel 
would scan all the blocks of the whole nand flash as  bad blocks. However, When 
I use the MVL 5.0 Kernel on my board, the kernel would find no bad blocks of 
the whole nand flash. So I want to know how to
update the MTD drivers for the nand flash from MVL 4.0 to MVL 5.0? could you 
give me some advies about that situation?

2. If the above problem would not be sovled correctly, I have to change my 
kernel from MVL 4.0 to MVL 5.0. While I found that the MVL 5.0 kernel could not 
mount the NFS correctly, the kernel would halt mounting the NFS for ever, the 
following is the messages:
=======================
IP-Config: Complete:
      device=eth0, addr=192.168.0.125, mask=255.255.255.0, gw=192.168.0.1,
     host=XJTUIPCEVM, domain=, nis-domain=(none),
     bootserver=192.168.0.238, rootserver=192.168.0.238, rootpath=
Looking up port of RPC 100003/2 on 192.168.0.238
portmap: server 192.168.0.238 not responding, timed out
Root-NFS: Unable to get nfsd port number from server, using default
Looking up port of RPC 100005/1 on 192.168.0.238
========================
But When I use the MVL 4.0 kernel, I found that the kernel woud correctly mount 
the NFS with no errors. Between the two situations my u-boot ENV is the same 
configurations:
bootargs=mem=120M console=ttyS0,115200n8 root=/dev/nfs noinitrd rw 
ip=192.168.0.125:192.168.0.238:192.168.0.1:255.255.255.0:XJTUIPCEVM 
nfsroot=192.168.0.238:/home/workdir/rootfs,nolock video=dm64xxfb:output=pal
So I want to know whether there are some necessary differences about the kernel 
configurations between the MVL 4.0 and MVL 5.0 or not. Such as "make 
menuconfig", "u-boot env setting (bootargs, etc.)"

Thand you, Hope for your reply.

Zhang


_______________________________________________
Davinci-linux-open-source mailing list
[email protected]
http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source

Reply via email to