On Sat, Oct 09, 2010 at 03:10:57PM +0300, Felipe Contreras wrote:
Well -
1. TI had been complaining last December about vmalloc() creating mappings
with different shared-ness attributes causing problems with OMAP.
2. May 10, TI on the three-weekly conference call were warned about this
change to ioremap with system RAM - and this was noted in the minutes
and circulated. It was brought up again on June 21st, and yet again
on August 2nd.
So, the major players in the OMAP community were repeatedly made plainly
aware of this change and some were aware of the problems caused by
violating these kinds of restrictions.
You tell me - if I've raised the issue on the mailing list to which OMAP
people are aware of (and note that there was a reply from OMAP folk in
the inital thread), if I've raised it several times with TI in conference
calls which include the major players, and still OMAP drivers are doing
things wrongly.
You can lead the horse to water but you can not make it drink. At some
point it either drinks or dies. In this case, it seems death is the
favoured option as the warnings have been repeatedly ignored.
--