ARM: pxa: enable pxafb unconditionally for some boards
The SAAR and TAVOREVB machines try to call functions from the PXAFB frame buffer driver from their platform code, which only works if that driver is built-in. This patch ensures that both the generic frame buffer code and the specific pxafb driver are always enabled when we build a kernel for one of the two boards. Signed-off-by: Arnd Bergmann <arnd@arndb.de> Cc: Eric Miao <eric.y.miao@gmail.com> Cc: Russell King <linux@arm.linux.org.uk> Cc: Haojian Zhuang <haojian.zhuang@gmail.com> Cc: Daniel Mack <zonque@gmail.com>
This commit is contained in:
parent
a0ad0fdb88
commit
e914f19f03
|
@ -53,12 +53,16 @@ config MACH_TAVOREVB
|
|||
select CPU_PXA930
|
||||
select CPU_PXA935
|
||||
select PXA3xx
|
||||
select FB
|
||||
select FB_PXA
|
||||
|
||||
config MACH_SAAR
|
||||
bool "PXA930 Handheld Platform (aka SAAR)"
|
||||
select CPU_PXA930
|
||||
select CPU_PXA935
|
||||
select PXA3xx
|
||||
select FB
|
||||
select FB_PXA
|
||||
|
||||
comment "Third Party Dev Platforms (sorted by vendor name)"
|
||||
|
||||
|
|
Loading…
Reference in New Issue