mirror of
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
synced 2024-08-22 17:01:14 +00:00
mtd: Remove unused symbol CONFIG_MTDRAM_ABS_POS
This has been unused, except as the condition for a fatal error, since
commit c13cbf3b50
("[MTD] mtdram: Quick cleanup of the driver:") in
2.6.13 (!).
Signed-off-by: Ben Hutchings <ben@decadent.org.uk>
Acked-by: Jesper Nilsson <jesper.nilsson@axis.com>
Signed-off-by: Brian Norris <computersforpeace@gmail.com>
This commit is contained in:
parent
9519379625
commit
ef158bdf83
3 changed files with 2 additions and 14 deletions
|
@ -397,7 +397,7 @@ static int __init init_axis_flash(void)
|
||||||
if (!romfs_in_flash) {
|
if (!romfs_in_flash) {
|
||||||
/* Create an RAM device for the root partition (romfs). */
|
/* Create an RAM device for the root partition (romfs). */
|
||||||
|
|
||||||
#if !defined(CONFIG_MTD_MTDRAM) || (CONFIG_MTDRAM_TOTAL_SIZE != 0) || (CONFIG_MTDRAM_ABS_POS != 0)
|
#if !defined(CONFIG_MTD_MTDRAM) || (CONFIG_MTDRAM_TOTAL_SIZE != 0)
|
||||||
/* No use trying to boot this kernel from RAM. Panic! */
|
/* No use trying to boot this kernel from RAM. Panic! */
|
||||||
printk(KERN_EMERG "axisflashmap: Cannot create an MTD RAM "
|
printk(KERN_EMERG "axisflashmap: Cannot create an MTD RAM "
|
||||||
"device due to kernel (mis)configuration!\n");
|
"device due to kernel (mis)configuration!\n");
|
||||||
|
|
|
@ -320,7 +320,7 @@ static int __init init_axis_flash(void)
|
||||||
* but its size must be configured as 0 so as not to conflict
|
* but its size must be configured as 0 so as not to conflict
|
||||||
* with our usage.
|
* with our usage.
|
||||||
*/
|
*/
|
||||||
#if !defined(CONFIG_MTD_MTDRAM) || (CONFIG_MTDRAM_TOTAL_SIZE != 0) || (CONFIG_MTDRAM_ABS_POS != 0)
|
#if !defined(CONFIG_MTD_MTDRAM) || (CONFIG_MTDRAM_TOTAL_SIZE != 0)
|
||||||
if (!romfs_in_flash && !nand_boot) {
|
if (!romfs_in_flash && !nand_boot) {
|
||||||
printk(KERN_EMERG "axisflashmap: Cannot create an MTD RAM "
|
printk(KERN_EMERG "axisflashmap: Cannot create an MTD RAM "
|
||||||
"device; configure CONFIG_MTD_MTDRAM with size = 0!\n");
|
"device; configure CONFIG_MTD_MTDRAM with size = 0!\n");
|
||||||
|
|
|
@ -171,18 +171,6 @@ config MTDRAM_ERASE_SIZE
|
||||||
as a module, it is also possible to specify this as a parameter when
|
as a module, it is also possible to specify this as a parameter when
|
||||||
loading the module.
|
loading the module.
|
||||||
|
|
||||||
#If not a module (I don't want to test it as a module)
|
|
||||||
config MTDRAM_ABS_POS
|
|
||||||
hex "SRAM Hexadecimal Absolute position or 0"
|
|
||||||
depends on MTD_MTDRAM=y
|
|
||||||
default "0"
|
|
||||||
help
|
|
||||||
If you have system RAM accessible by the CPU but not used by Linux
|
|
||||||
in normal operation, you can give the physical address at which the
|
|
||||||
available RAM starts, and the MTDRAM driver will use it instead of
|
|
||||||
allocating space from Linux's available memory. Otherwise, leave
|
|
||||||
this set to zero. Most people will want to leave this as zero.
|
|
||||||
|
|
||||||
config MTD_BLOCK2MTD
|
config MTD_BLOCK2MTD
|
||||||
tristate "MTD using block device"
|
tristate "MTD using block device"
|
||||||
depends on BLOCK
|
depends on BLOCK
|
||||||
|
|
Loading…
Reference in a new issue