Le dimanche 22 février 2015 à 16:45 +0100, Paul Kocialkowski a écrit :
> > > Workarounds applied in omap3_setup_aux_cr are only necessary for ARM core
> > > revisions prior to r3p2 (such as OMAP35xx but apparently not OMAP36xx and
> > > DM37xx)
> >
> > If this is true, I can see some (potential) p
Le dimanche 22 février 2015 à 16:45 +0100, Paul Kocialkowski a écrit :
> > > Workarounds applied in omap3_setup_aux_cr are only necessary for ARM core
> > > revisions prior to r3p2 (such as OMAP35xx but apparently not OMAP36xx and
> > > DM37xx)
> >
> > If this is true, I can see some (potential) p
> > Workarounds applied in omap3_setup_aux_cr are only necessary for ARM core
> > revisions prior to r3p2 (such as OMAP35xx but apparently not OMAP36xx and
> > DM37xx)
>
> If this is true, I can see some (potential) problems with the patch.
> Please, check out my thoughts on this below.
In any ca
Hi Paul,
On 02/22/15 13:36, Paul Kocialkowski wrote:
> Workarounds applied in omap3_setup_aux_cr are only necessary for ARM core
> revisions prior to r3p2 (such as OMAP35xx but apparently not OMAP36xx and
> DM37xx)
If this is true, I can see some (potential) problems with the patch.
Please, check
Workarounds applied in omap3_setup_aux_cr are only necessary for ARM core
revisions prior to r3p2 (such as OMAP35xx but apparently not OMAP36xx and
DM37xx) and require similar workarounds in the kernel, or it will cause numerous
segmentation faults. This allows (when the option is not used) properl
5 matches
Mail list logo