From: Radek Pilar <mrkva@mrkva.eu>
To: linux-omap@vger.kernel.org
Subject: [PATCH 1/1] Config fix for omap3-touchbook board
Date: Fri, 17 Aug 2012 18:03:43 +0200 [thread overview]
Message-ID: <502E6B5F.8020407@mrkva.eu> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1388 bytes --]
Fix inconsistency between mach-types and CONFIG_ name that prevents touchbook board from booting.
Signed-off-by: Radek Pilar <mrkva@mrkva.eu>
diff -ur linux-3.5.1/arch/arm/mach-omap2/Kconfig linux-3.5.1-mrkva/arch/arm/mach-omap2/Kconfig
--- linux-3.5.1/arch/arm/mach-omap2/Kconfig 2012-08-09 17:23:56.000000000 +0200
+++ linux-3.5.1-mrkva/arch/arm/mach-omap2/Kconfig 2012-08-14 13:48:27.000000000 +0200
@@ -215,10 +215,11 @@
select OMAP_PACKAGE_CBB
select REGULATOR_FIXED_VOLTAGE if REGULATOR
-config MACH_OMAP3_TOUCHBOOK
+config MACH_TOUCHBOOK
bool "OMAP3 Touch Book"
depends on ARCH_OMAP3
default y
+ select OMAP_PACKAGE_CBB
config MACH_OMAP_3430SDP
bool "OMAP 3430 SDP board"
diff -ur linux-3.5.1/arch/arm/mach-omap2/Makefile linux-3.5.1-mrkva/arch/arm/mach-omap2/Makefile
--- linux-3.5.1/arch/arm/mach-omap2/Makefile 2012-08-09 17:23:56.000000000 +0200
+++ linux-3.5.1-mrkva/arch/arm/mach-omap2/Makefile 2012-08-14 13:48:13.000000000 +0200
@@ -221,7 +221,7 @@
obj-$(CONFIG_MACH_CM_T35) += board-cm-t35.o
obj-$(CONFIG_MACH_CM_T3517) += board-cm-t3517.o
obj-$(CONFIG_MACH_IGEP0020) += board-igep0020.o
-obj-$(CONFIG_MACH_OMAP3_TOUCHBOOK) += board-omap3touchbook.o
+obj-$(CONFIG_MACH_TOUCHBOOK) += board-omap3touchbook.o
obj-$(CONFIG_MACH_OMAP_4430SDP) += board-4430sdp.o
obj-$(CONFIG_MACH_OMAP4_PANDA) += board-omap4panda.o
[-- Attachment #1.2: 0xE60DBF0D.asc --]
[-- Type: application/pgp-keys, Size: 6555 bytes --]
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 900 bytes --]
next reply other threads:[~2012-08-17 16:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-17 16:03 Radek Pilar [this message]
2012-08-30 20:55 ` [PATCH 1/1] Config fix for omap3-touchbook board Tony Lindgren
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=502E6B5F.8020407@mrkva.eu \
--to=mrkva@mrkva.eu \
--cc=linux-omap@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).