From: Kevin Hilman <khilman@deeprootsystems.com>
To: Elvis Dowson <elvis.dowson@mac.com>
Cc: Linux OMAP Users <linux-omap@vger.kernel.org>
Subject: Re: Overo defconfig for omap-2.6.30
Date: Wed, 15 Jul 2009 10:25:45 -0700 [thread overview]
Message-ID: <874otd97ty.fsf@deeprootsystems.com> (raw)
In-Reply-To: <F2B67B67-3E11-4CEF-8FB4-49EE9C05F2B9@mac.com> (Elvis Dowson's message of "Wed\, 15 Jul 2009 21\:07\:27 +0400")
Elvis Dowson <elvis.dowson@mac.com> writes:
> Could you give me a copy of a defconfig file
> that you have for the Overo, for omap-2.6.30 and the one that you are
> using currently for your current development efforts on the pm
> branch?
I use omap3_pm_defconfig for all boards.
The default in that config is for UART1 console which works for SDP
and omap3evm. For all others (beagle, rx51, zoom2, Overo) I simply
change the low-level debug UART to UART3.
This allows me to test the same defconfig on all boards.
Kevin
next parent reply other threads:[~2009-07-15 17:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <F2B67B67-3E11-4CEF-8FB4-49EE9C05F2B9@mac.com>
2009-07-15 17:25 ` Kevin Hilman [this message]
[not found] ` <DB30225E-E3F3-4626-9B5D-5BD72DF25DA9@mac.com>
2009-07-15 18:16 ` Overo defconfig for omap-2.6.30 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=874otd97ty.fsf@deeprootsystems.com \
--to=khilman@deeprootsystems.com \
--cc=elvis.dowson@mac.com \
--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