On 03/06/2013 10:48 AM, Mark Jackson wrote: > On 06/03/13 16:44, Jon Hunter wrote: >> >> On 03/06/2013 07:30 AM, Mark Jackson wrote: >>> On 06/03/13 10:23, Mark Jackson wrote: > > <snip> > >>>> [ 1.541884] gpmc_probe_nor_child 1 >>>> [ 1.545483] GPMC_CS_CONFIG7_0 : 00000f48 >>>> [ 1.549621] GPMC_CS_CONFIG7_1 : 00000f58 >>>> [ 1.553812] GPMC_CS_CONFIG7_2 : 00000f00 >>>> [ 1.557951] GPMC_CS_CONFIG7_3 : 00000c5a >>> >>> 0x00000c5a is an invalid mode !! >>> >>> I'm trying to use a 64MB address space but not on a 64MB boundary ... oops. >> >> Good catch. So this is now working for you then? > > Not yet ... I got distracted by something else !?! > > I'll take another look tomorrow. > > Do you think it might be worth adding some sanity checking to the cs config > routines to trap similar errors ? Yes, I see what you mean. We should check to ensure that the the base is aligned on a boundary that matches the size being configured. I can add some checking for this case. Cheers Jon -- 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
