* Pali Rohár <pali.rohar@xxxxxxxxx> [150316 14:15]: > On Monday 16 March 2015 22:01:43 Tony Lindgren wrote: > > * Pali Rohár <pali.rohar@xxxxxxxxx> [150316 13:59]: > > > On Monday 16 March 2015 16:29:39 Tony Lindgren wrote: > > > > I believe the last pending issues is the support for > > > > ATAG_REVISION in device tree mode as posted by Pali. > > > > > > No. In DT boot there is missing /proc/atags file (readable > > > by userspace processes). > > > > Oh OK thanks for the update. > > > > > And also broken AES/SHA/MD5 support. Fix for crypto DT stuff > > > I already sent. > > > > But this is not a regression in mainline with legacy boot vs > > device tree based booting, right? Sounds like it never worked > > in the mainline or am thinking of some other set of patches? > > > > Regards, > > > > Tony > > In legacy board code are DMA channels defined. In DT files not. > So I think this is regression. Omap secure devices are broken in > both legacy & DT code, but non secure could work with legacy > code. But all devices booted with DT are broken. OK I'll apply the DMA channels into omap-for-v4.0/fixes in that case. Regards, 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
