From: Nishanth Menon <menon.nishanth@gmail.com>
To: Paul Walmsley <paul@pwsan.com>
Cc: linux-omap-open-source@linux.omap.com
Subject: Are we ready for 3430?
Date: Wed, 16 May 2007 21:24:05 -0500 [thread overview]
Message-ID: <464BBCC5.4080905@gmail.com> (raw)
In-Reply-To: <20070517005638.997832459@pwsan.com>
Paul/Tony,
Paul Walmsley stated on 5/16/2007 7:56 PM:
> These patches add OMAP3430 support to the PRCM framework. The patches
> add 3430-specific register and register bit defines.
>
What platform can I test this on? I suspect more code needs to flow in
before we are ready with 3430 base rt - what about base defines etc? are
we about to see more 3430 patches? Are we planning on pushing all these
changes to a seperate tree and integrate to mainline as we did it with 2430?
Regards,
Nishanth Menon
next prev parent reply other threads:[~2007-05-17 2:24 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-17 0:56 [PATCH 0/7] Add OMAP3430 PRCM register, regbits support Paul Walmsley
2007-05-17 0:56 ` [PATCH 1/7] omap2: add OMAP3430 modules to prcm_common.h Paul Walmsley
2007-05-17 0:56 ` [PATCH 2/7] omap2: add OMAP3430 register bit defines shared between CM and PRM Paul Walmsley
2007-05-17 0:56 ` [PATCH 3/7] omap2: add OMAP3430 Clock Management register defines to cm.h Paul Walmsley
2007-05-17 0:56 ` [PATCH 4/7] omap2: add OMAP3430 Power/Reset Management register defines to prm.h Paul Walmsley
2007-05-17 0:56 ` [PATCH 5/7] omap2: add OMAP3430 Clock Management register bit defines Paul Walmsley
2007-05-17 0:56 ` [PATCH 6/7] omap2: add OMAP3430 Power/Reset " Paul Walmsley
2007-05-17 0:56 ` [PATCH 7/7] omap2: add OMAP3430 base defines Paul Walmsley
2007-05-17 2:24 ` Nishanth Menon [this message]
2007-05-17 3:03 ` Are we ready for 3430? Syed Mohammed, Khasim
2007-05-17 17:56 ` 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=464BBCC5.4080905@gmail.com \
--to=menon.nishanth@gmail.com \
--cc=linux-omap-open-source@linux.omap.com \
--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.