On 2013-12-16 14:41, Geert Uytterhoeven wrote:
On Mon, Dec 16, 2013 at 11:57 AM, Ingo Jürgensmann
BigRamplus is Z3, not Z2, so it won't show up.
Uhm... is there any reason why this is limited to Z2?
Because it's called z2ram?
So far, no one played with Z3 RAM boards.
So far I thought of Z3 being a superset of Z2 and assumed Z3 Ram should
be recognized as Z2 Ram, although it might be rather slow when accessed
as Z2.
You can try CONFIG_MTD_PHRAM to create a block device and use it as
sawp.
But with that I would need to define the memory in memfile, I guess,
but
then again it gets ignored when it's not in the proper order, because
I want
the kernel to get loaded into Fastmem (it doesn't work with the
BigRamPlus
yet anyway).
No, don't put in in the memfile. I haven't looked at the code yet, but
I expect
the driver to ioremap() the RAM based on a kernel command line
parameter.
We could add code to detect it automatically it if the above works.
Ok, built a new kernel with MTD support built in (i.e. not as module).
Have to try it later whether this works... are there any user land tools
needed?
--
Ciao... // Fon: 0381-2744150
. Ingo \X/ http://blog.windfluechter.net
gpg pubkey: http://www.juergensmann.de/ij_public_key.
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
Archive: http://lists.debian.org/bc6887bea9ebdb0a14c00e21c0b86f75@localhost
