Re: [microblaze-uclinux] SystemAce and mb-uClinux

[John Williams <jwilliams@itee.uq.edu.au>]

[Forwarded to the list after majordomo bounced it]

Hi John


 >>Have you tried the driver without hardware present?  Is it reasonable to
 >>modify the driver so it can gracefully abort if the hardware isn't
 >>present?  Or is it reasonable that the user shouldn't select the driver,
 >>if they don't have the hardware?


Sorry I forgot about this. I have not checked it without the hardware being
present.
Maybe that is the reason, that MontaVista is only offering support for the
ml300.
Their drivers seem to be very specific.

I will dig into this topic. But that may need some time.
As I will have ot understand how this driver works
(actually I will have to understand how drivers in Linux
work in general - I have just ordered the books you
recommended, so I hope I will make some progress addressing
this topic)

The good news is: We got Linux booting right from SystemAce
at powerup. Jan did quite a good job writing all the
TCL scripts to convert the image.bin to svf, add them
to the bitfile's svf and generating .ace file from there,
which finally is used when systemAce start.
Our current solution is far from beeing optimal.
(3MB image.bin + 1MB bitfile add up to
95 MB ace - there seems to be some overhead ;))
But we can see the light...

I am still addressing the problem of mounting the
SystemAce's compact flash as root file system.
I hard coded a command line, but neither
root=/dev/xsysacea1 nor root=fe00 nor
root=fe01 did the trick.  I guess I found
the parts in do_mounts.c where all this stuff
is done. But I still have not found how
1f00 (the ramdisk) is mounted. But today
I have not spend much time on this, so I
expect to solve this tomorrow.

- Erik


___________________________
microblaze-uclinux mailing list
microblaze-uclinux@itee.uq.edu.au
Project Home Page : http://www.itee.uq.edu.au/~jwilliams/mblaze-uclinux
Mailing List Archive : http://www.itee.uq.edu.au/~listarch/microblaze-uclinux/