* Santosh Shilimkar <santosh.shilimkar@xxxxxx> [130918 07:15]: > On Wednesday 18 September 2013 10:05 AM, Nishanth Menon wrote: > > OMAP5 ES1.0 was intended as a test chip and has major register level > > differences w.r.t ES2.0 revision of the chip. All register defines, > > dts support has been solely added for ES2.0 version of the chip. > > Further, all ES1.0 chips and platforms are supposed to have been > > removed from circulation. Hence, there is no need to further retain > > any resemblence of ES1.0 support in id detection code. > > > > Remove the omap_revision handling and BUG() instead to prevent folks > > who mistakenly try an older unsupported chip and report bogus errors. > > > > Cc: Santosh Shilimkar <santosh.shilimkar@xxxxxx> > > Signed-off-by: Nishanth Menon <nm@xxxxxx> > > --- > > ref: http://marc.info/?l=linux-omap&m=137951198232339&w=2 > > based on 3.12-rc1 tag > > > That was quick ... > Acked-by: Santosh Shilimkar <santosh.shilimkar@xxxxxx> Heh, it was made, but not supposed to be used, and still merged to mainline kernel.. I guess this is the way to deal with this issue as we don't have really any omap5 es1 support in place. So applying into omap-for-v3.13/soc branch. Tony -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
