Can CMEM take account of 'memmap=' kernel boot parameter

Mike Whittaker

We have a 6467T board with 512M of memory.

Currently only using the first 120M for Linux as per the SDK: mem=120M allowing the rest for CMEM etc.

However it would be useful to include the remainder above 90000000 so we changed the boot config to 'mem=512M memmap=132M$87800000' to leave a hole for CMEM.

However CMEM now complains:

"CMEMK Error: CMEM phys_start (0x87800000) overlaps kernel (0x80000000 -> 0xa0000000)" even though there is a hole reserved for CMEM

I am aware that there is a CMEM overlap parameter, but would it not be better if CMEM could detect that there was actually no overlap with the kernel memory map ?

over 13 years ago

0 Mike Whittaker over 13 years ago

Intellectual 410 points

Will try a different approach - just hoist the CMEM up to 0x978... from 0x878... and give the Linux 'mem=' a correspondingly smaller amount, ie. 512-(128+8) M

0 Vincent W. over 13 years ago in reply to Mike Whittaker

TI__Genius 12865 points

Not sure if this is what you meant by "CMEM overlap parameter", but in newer versions of CMEM you can specify "allowOverlap=1" when you insmod cmemk.ko. It will allow "overlapping ranges" as a result.

In any case, things may be more straightforward if you can lump the linux memory together into a single contiguous range as in your second post.

Best regards,

Vincent

0 Mike Whittaker over 13 years ago in reply to Mike Whittaker

Intellectual 410 points

Test post - TI forum not accepting posts ?

Processors

Processors forum

Can CMEM take account of 'memmap=' kernel boot parameter