From: Brian Swetland <swetland@google.com>
To: linux-omap-open-source@linux.omap.com
Subject: [PATCH] fix omap1 build for 730/p2
Date: Thu, 2 Mar 2006 14:03:57 -0800 [thread overview]
Message-ID: <20060302220357.GA6305@localhost.localdomain> (raw)
[-- Attachment #1: Type: text/plain, Size: 58 bytes --]
Attached is a simple patch to fix the build for 730/P2.
[-- Attachment #2: fix-730.patch --]
[-- Type: text/plain, Size: 573 bytes --]
diff -ur a/include/asm-arm/arch-omap/mcbsp.h b/include/asm-arm/arch-omap/mcbsp.h
--- a/include/asm-arm/arch-omap/mcbsp.h 2006-02-27 12:14:46.000000000 -0800
+++ b/include/asm-arm/arch-omap/mcbsp.h 2006-03-02 12:37:17.000000000 -0800
@@ -40,7 +40,7 @@
#define OMAP24XX_MCBSP1_BASE 0x48074000
#define OMAP24XX_MCBSP2_BASE 0x48076000
-#if defined(CONFIG_ARCH_OMAP15XX) || defined(CONFIG_ARCH_OMAP16XX)
+#if defined(CONFIG_ARCH_OMAP15XX) || defined(CONFIG_ARCH_OMAP16XX) || defined(CONFIG_ARCH_OMAP730)
#define OMAP_MCBSP_REG_DRR2 0x00
#define OMAP_MCBSP_REG_DRR1 0x02
[-- Attachment #3: Type: text/plain, Size: 0 bytes --]
next reply other threads:[~2006-03-02 22:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-02 22:03 Brian Swetland [this message]
2006-03-03 0:42 ` [PATCH] fix omap1 build for 730/p2 Kevin Hilman
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=20060302220357.GA6305@localhost.localdomain \
--to=swetland@google.com \
--cc=linux-omap-open-source@linux.omap.com \
/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