parisc: always detect multiple physical ranges
This patch unbreaks the current logic in that way, that even if CONFIG_DISCONTIGMEM isn't set, the user may be informed, that he should turn on CONFIG_DISCONTIGMEM for his machine. Signed-off-by: John David Anglin <dave.anglin@bell.net> Signed-off-by: Helge Deller <deller@gmx.de>
This commit is contained in:
parent
5ca8b91df8
commit
872420b3b8
1 changed files with 2 additions and 3 deletions
|
@ -1,9 +1,10 @@
|
||||||
#ifndef _PARISC_MMZONE_H
|
#ifndef _PARISC_MMZONE_H
|
||||||
#define _PARISC_MMZONE_H
|
#define _PARISC_MMZONE_H
|
||||||
|
|
||||||
|
#define MAX_PHYSMEM_RANGES 8 /* Fix the size for now (current known max is 3) */
|
||||||
|
|
||||||
#ifdef CONFIG_DISCONTIGMEM
|
#ifdef CONFIG_DISCONTIGMEM
|
||||||
|
|
||||||
#define MAX_PHYSMEM_RANGES 8 /* Fix the size for now (current known max is 3) */
|
|
||||||
extern int npmem_ranges;
|
extern int npmem_ranges;
|
||||||
|
|
||||||
struct node_map_data {
|
struct node_map_data {
|
||||||
|
@ -60,7 +61,5 @@ static inline int pfn_valid(int pfn)
|
||||||
return 0;
|
return 0;
|
||||||
}
|
}
|
||||||
|
|
||||||
#else /* !CONFIG_DISCONTIGMEM */
|
|
||||||
#define MAX_PHYSMEM_RANGES 1
|
|
||||||
#endif
|
#endif
|
||||||
#endif /* _PARISC_MMZONE_H */
|
#endif /* _PARISC_MMZONE_H */
|
||||||
|
|
Loading…
Add table
Reference in a new issue