From: Igor Stoppa <igor.stoppa@nokia.com>
To: ext Girish <girishsg@ti.com>
Cc: linux-omap-open-source@linux.omap.com
Subject: Re: [PATCH 0/2] CPU id and silicon rev check support
Date: Fri, 26 Oct 2007 19:03:03 +0300 [thread overview]
Message-ID: <1193414583.23273.6.camel@localhost.localdomain> (raw)
In-Reply-To: <000101c817e6$59bb6770$6a8918ac@ent.ti.com>
Hi,
On Fri, 2007-10-26 at 21:09 +0530, ext Girish wrote:
> Sorry, I guess the previous patch series might have got auto wrapped. Resending the patch series without auto wrapping.
>
> Hi,
> I am sending across patch series to support CPU identification and run-time silicon revision check for OMAP2/3.
Is there any way to identify at runtime a speed sorted omap vs a
standard one?
Then some of the code we have for N800/N810 could be moved from board to
arch.
--
Cheers, Igor
Igor Stoppa <igor.stoppa@nokia.com>
(Nokia Multimedia - CP - OSSO / Helsinki, Finland)
next prev parent reply other threads:[~2007-10-26 16:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-26 15:39 [PATCH 0/2] CPU id and silicon rev check support Girish
2007-10-26 16:03 ` Igor Stoppa [this message]
2007-10-26 17:20 ` Woodruff, Richard
-- strict thread matches above, loose matches on Subject: below --
2007-10-26 15:11 Girish
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=1193414583.23273.6.camel@localhost.localdomain \
--to=igor.stoppa@nokia.com \
--cc=girishsg@ti.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