From: Tony Lindgren <tony@atomide.com>
To: Hemant Pedanekar <hemantp@ti.com>
Cc: linux-omap@vger.kernel.org, khilman@ti.com, paul@pwsan.com
Subject: Re: [PATCH v5 1/4] TI816X: Update common omap platform files
Date: Wed, 9 Feb 2011 17:39:10 -0800 [thread overview]
Message-ID: <20110210013910.GF20795@atomide.com> (raw)
In-Reply-To: <1297270555-32447-1-git-send-email-hemantp@ti.com>
Hi,
* Hemant Pedanekar <hemantp@ti.com> [110209 08:54]:
>
> 1) Multi-OMAP build with CONFIG_SOC_OMAPTI816X: The kernel built only for
> TI816X OMAP3 SoCs along with any other OMAP2/4 (e.g., OMAP4s). May not boot
> on other OMAP3 SoCs.
This option does not sound right. For the multi-omap builds we need to have
the system working for all the processors, there should not be any reason
not to have things working.
Do you have some example in mind where other omaps break? If so, we should
just fix that issue.
Regards,
Tony
next prev parent reply other threads:[~2011-02-10 1:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-09 16:55 [PATCH v5 1/4] TI816X: Update common omap platform files Hemant Pedanekar
2011-02-10 1:39 ` Tony Lindgren [this message]
2011-02-10 17:37 ` Pedanekar, Hemant
2011-02-10 18:25 ` 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=20110210013910.GF20795@atomide.com \
--to=tony@atomide.com \
--cc=hemantp@ti.com \
--cc=khilman@ti.com \
--cc=linux-omap@vger.kernel.org \
--cc=paul@pwsan.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.