Re: Making use of the BigRamPlus?
On 2013-12-17 09:44, Geert Uytterhoeven wrote:
But when mkswap /dev/mtd0 I get this:
Dec 17 07:59:06 spice kernel: [ 440.710000] phram: bigram device:
0x10000000 at 0x5000000
Dec 17 07:59:47 spice kernel: [ 480.410000] Unable to handle kernel
access
at virtual address d0180000
You're sure 0x5000000 is the right address? cat /proc/iomem or lszorro
-v will
tell you.
spice:/home/ij# lszorro -v
00: MacroSystems USA Warp Engine 40xx [Accelerator, SCSI Host Adapter
and RAM Expansion]
40000000 (512K)
01: Village Tronic Picasso II/II+ RAM [Graphics Card]
00200000 (2M)
02: Village Tronic Picasso II/II+ [Graphics Card]
00e90000 (64K)
03: Hydra Systems Amiganet [Ethernet Card]
00ea0000 (64K)
04: Unknown device 0e3b:20:00
50000000 (256M)
Uhm... you're right! A zero was missing, it seems... ;)
spice:/home/ij# modprobe phram phram=bigram,0x50000000,200Mi
spice:/home/ij# mkswap /dev/mtd0
mkswap: warning: truncating swap area to 17179869184 KiB
Setting up swapspace version 1, size = 17179869180 KiB
no label, UUID=4b8f8895-4304-4d13-bfe4-d04487f1296d
mkswap: fsync failed
Hmm... some progress at least...
CONFIG_MTD=m
CONFIG_MTD_CMDLINE_PARTS=m
CONFIG_MTD_BLKDEVS=m
CONFIG_MTD_SWAP=m
CONFIG_MTD_MAP_BANK_WIDTH_1=y
CONFIG_MTD_MAP_BANK_WIDTH_2=y
CONFIG_MTD_MAP_BANK_WIDTH_4=y
CONFIG_MTD_CFI_I1=y
CONFIG_MTD_CFI_I2=y
CONFIG_MTD_SLRAM=m
CONFIG_MTD_PHRAM=m
CONFIG_MTD_BLOCK2MTD=m
Still, the exception means that there's nothing mapped at the accessed
address,
so either phram is using the wrong address, or we have a bug in
ioremap().
Adding "#define DEBUG" at the top of arch/m68k/mm/kmap.c may give a
hint.
I don't have any Z3 devices myself, but we do have users of Z3 graphics
cards,
right?
I think PicassoII is Z2, but I've a PicassoIV laying around somewhere. I
hope it is not at my parents home, though... ;)
BTW: speaking of graphic cards: I can't use cirrusfb as framebuffer
device currently, but different story... ;)
--
Ciao... // Fon: 0381-2744150
. Ingo \X/ http://blog.windfluechter.net
gpg pubkey: http://www.juergensmann.de/ij_public_key.
Reply to: