On Mon, 2 Nov 2009, Nishanth Menon wrote:
Alexander Shishkin had written, on 11/02/2009 11:01 AM, the following:
[..]
Issues with the strategy of restricting to the current 8 bits:
a) Why extrabits now:
we have 8 bits now and we would have used all 8 bits with 3630 with
the
2009/10/21 Nishanth Menon n...@ti.com:
Paul Walmsley had written, on 10/20/2009 06:14 PM, the following:
Hi Vikram, Nishanth, Richard,
a few comments on this:
On Tue, 20 Oct 2009, Vikram Pandita wrote:
Add bits for future expansion of omap_chip_id type field.
This is needed to accomodate
Alexander Shishkin had written, on 11/02/2009 07:12 AM, the following:
2009/10/21 Nishanth Menon n...@ti.com:
Paul Walmsley had written, on 10/20/2009 06:14 PM, the following:
Hi Vikram, Nishanth, Richard,
a few comments on this:
On Tue, 20 Oct 2009, Vikram Pandita wrote:
Add bits for
Alexander Shishkin had written, on 11/02/2009 11:01 AM, the following:
[..]
Issues with the strategy of restricting to the current 8 bits:
a) Why extrabits now:
we have 8 bits now and we would have used all 8 bits with 3630 with the
mentioned patch. What do we do with the next revision of 3430?
-Original Message-
From: Paul Walmsley [mailto:p...@pwsan.com]
Sent: Tuesday, October 20, 2009 6:15 PM
To: Pandita, Vikram; Woodruff, Richard; Menon, Nishanth
Cc: linux-omap@vger.kernel.org
Subject: Re: [PATCH v2 1/2] omap: add bits for future 3430/3630 ES revisions
Hi Vikram, Nishanth
Paul Walmsley had written, on 10/20/2009 06:14 PM, the following:
Hi Vikram, Nishanth, Richard,
a few comments on this:
On Tue, 20 Oct 2009, Vikram Pandita wrote:
Add bits for future expansion of omap_chip_id type field.
This is needed to accomodate 3630ES1 chip id which is bit10
...
