Hi,
On 21.01.2016 11:14, Pali Rohár wrote:
On Saturday 09 January 2016 02:23:26 Ivaylo Dimitrov wrote:
Hi,
On 8.01.2016 09:59, Pali Rohár wrote:
On Friday 08 January 2016 07:13:58 Ivaylo Dimitrov wrote:
And it looks like the problems happens sometimes on oops too.
In linux-n900 tree is enabled mtdoops driver which store oops to
specified MTD device. So maybe this access cause it?
The key word here is "sometimes". i.e sometimes it hapens on normal reboot,
sometimes it happens on oops.
So where is problem? In omap-gpmc? mtd? onenand? or ubifs? Or in
different component? Do we know at least this?
I think I made some progress on the issue, it seems I have to have
*both* e7b11dc7b77bfce0a351230a5feeadc1d0bba997
(e7b11dc7b77bfce0a351230a5feeadc1d0bba997) reverted *and*
HWMOD_INIT_NO_RESET restored in omap3xxx_gpmc_hwmod flags to have
working onenand.
Tony, shall I hardcode GPMC_CS_CONFIG4 OEONTIME to be the same as NOLO's
or it does not make sense?
Regards,
Ivo
--
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
