Searched hist:"3 a0d7a4dd5b3a6545e5764735b48ab84e64af723" (Results 1 – 3 of 3) sorted by relevance
/linux/arch/microblaze/mm/ |
H A D | Makefile | diff 3a0d7a4dd5b3a6545e5764735b48ab84e64af723 Mon Feb 22 12:16:08 CET 2010 Michal Simek <monstr@monstr.eu> microblaze: Add consistent code
Remove ancient Kconfig option for consistent code. MMU uses cache inhibit pages.
noMMU uses UNCACHE SHADOW feature where is used double ram size. For example: Physical ram is 256MB and cache are setup to cover the same size. But if you setup in HW that size is 512MB and cache covers 256MB than you can use adresses from 256-512MB without caches and correspond with 0-256MB with cache. That's why I am using dcache base/high addresses to find out uncache area.
Signed-off-by: Michal Simek <monstr@monstr.eu>
|
H A D | consistent.c | 3a0d7a4dd5b3a6545e5764735b48ab84e64af723 Mon Feb 22 12:16:08 CET 2010 Michal Simek <monstr@monstr.eu> microblaze: Add consistent code
Remove ancient Kconfig option for consistent code. MMU uses cache inhibit pages.
noMMU uses UNCACHE SHADOW feature where is used double ram size. For example: Physical ram is 256MB and cache are setup to cover the same size. But if you setup in HW that size is 512MB and cache covers 256MB than you can use adresses from 256-512MB without caches and correspond with 0-256MB with cache. That's why I am using dcache base/high addresses to find out uncache area.
Signed-off-by: Michal Simek <monstr@monstr.eu>
|
/linux/arch/microblaze/ |
H A D | Kconfig | diff 3a0d7a4dd5b3a6545e5764735b48ab84e64af723 Mon Feb 22 12:16:08 CET 2010 Michal Simek <monstr@monstr.eu> microblaze: Add consistent code
Remove ancient Kconfig option for consistent code. MMU uses cache inhibit pages.
noMMU uses UNCACHE SHADOW feature where is used double ram size. For example: Physical ram is 256MB and cache are setup to cover the same size. But if you setup in HW that size is 512MB and cache covers 256MB than you can use adresses from 256-512MB without caches and correspond with 0-256MB with cache. That's why I am using dcache base/high addresses to find out uncache area.
Signed-off-by: Michal Simek <monstr@monstr.eu>
|