Oooopps!
I mismatch my question... I said "if i try to boot from flash" when I wanted to say "if I try to boot from ram".
So... The question is: I cannot boot my ramdisk from ram (kernel is also in ram)... The rest of the mail was correct.
Thanks for your answers.
Miguel Ángel
Wolfgang Denk escribió:
In message 47B15940.8030901@gmail.com you wrote:
The problem: I can start a Linux kernel and its filesystem from flash (linux image made using mkimage, and filesystem in cramfs format). However, if I try to boot them from flash (this time both images have been constructed using mkimage), the kernel starts, but a "No filesystem could mount root, tried: cramfs romfs" appears.
...
As you can see, I do not use initrd param because I suppose it is directly passed to the kernel.
The kernel.org tree does not recognize a ramdisk image in flash. Patches have been posted here since 2.4.17 times, but never made it upstream. See the archives ...
Best regards,
Wolfgang Denk
This message (and any associated files) is intended only for the use of the individual or entity to which it is addressed and may contain information that is confidential, subject to copyright or constitutes a trade secret. If you are not the intended recipient you are hereby notified that any dissemination, copying or distribution of this message, or files associated with this message, is strictly prohibited. If you have received this message in error, please notify us immediately by replying to the message and deleting it from your computer. Messages sent to and from us may be monitored.
Internet communications cannot be guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. Therefore, we do not accept responsibility for any errors or omissions that are present in this message, or any attachment, that have arisen as a result of e-mail transmission. If verification is required, please request a hard-copy version. Any views or opinions presented are solely those of the author and do not necessarily represent those of the company.