Hi,
You have several options.
1/ Hack at the 'full' root file system image on the DM6446 with 'rm'.
You can use the .tgz in the restore partition of the disk to start with.
Not a good idea really.
2/ Licence 'DevRocket' for MontaVista and use that to produce the
filesystem. OK provided you (or your Company) are prepared to pay up. It
is Java, it is sloooow but it gets the job done. Beware of conflicts
between 'busybox' and the real tools. I found the 'strip' options a
little too zealous with the C/C++ library - our application found
symbols missing and would not load. Had to force a package reload later
on in the build process to get round this.
3/ Download LTIB and use that. This does work but the final file system
is not MV like if that matters to you.
4/ Cross compile 'Linux From Scratch' for the ARM. A lot of work....LTIB
was originally designed to automate this process. You will end up with
something similar to LTIB for that reason.
I came up with another idea that requires knowledge of RPM and the
realisation that the DM6446 filesystem on disk is RPM managed. Knowing
that you can take the existing root filesystem and use RPM on the target
to remove packages. Any missing packages are in the MV toolchain area
and can be copied to the target and installed. You can fool a host RPM
into doing this if you want to generate the filesystem on a host but it
helps a lot if your host is RPM based - although you can use 'mvl-rpm'
if not. 'mvl-rpmbuild' can be used should you want to package your
application (it is configured to cross compile). IMHO it makes sense to
keep everything in the root filesystem packaged up the same.
In theory you should be able to start with the RPM packages in the MV
tree (MontaVista rename the packages as .mvl for reasons unknown but
'file' confirms that they are RPMs). A 'full' file system would be an
install of '*mvl' in theory, however some packages may provide duplicate
functionality (busybox for example) so some 'intelligence' may be needed
to sort this out. I guess this is why you pay for DevRocket. It is your
call whether you are able to spend the time/money to do it yourself or
get DevRocket and then spend time learning how to use it and work around
its quirks.
Regards
Phil Q
Joshua Hintze wrote:
Hi guys,
I’ve been working with the Davinci now for over a year and I’ve had a
lot of success. My current setup I use NAND flash for uImage/uboot and
then I load my rootfs from an IDE hard drive.
I have a new project now where we are not going to use the IDE hard
drive anymore and so I’m tasked to get the file system to fit on NAND
flash. So what’s the best way to create/strip down the filesystem that
fits into 64 megs of NAND flash?
My main components I need are the Codec engine modules, Apache
Webserver, Samaba, and commonly used routines.
Thanks for any suggestions,
Josh
------------------------------------------------------------------------
_______________________________________________
Davinci-linux-open-source mailing list
[email protected]
http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
_______________________________________________
Davinci-linux-open-source mailing list
[email protected]
http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
