On Tue, Feb 07, 2017 at 08:33:53PM +0100, Richard Weinberger wrote: > Am 10.01.2017 um 20:30 schrieb Zach Brown: > > From: Jeff Westfahl <[email protected]> > > > > If the user has not set max_beb_per1024 using either the cmdline or > > Kconfig options for doing so, use the MTD function 'max_bad_blocks' to > > compute the UBI bad_peb_limit. > > > > Signed-off-by: Jeff Westfahl <[email protected]> > > Signed-off-by: Zach Brown <[email protected]> > > Acked-by: Boris Brezillon <[email protected]> > > Does this patch go via the MTD tree? > In this case: > Acked-by: Richard Weinberger <[email protected]>
I thought we had said something about going through the UBI tree. But I don't care. I'm not sure what's happening with patches 3-5 yet either. I'm applying patch 1 to l2-mtd.git. Depending on the following, I can apply patch 2 as well... ...but this is still a bit awkward; AFAICT, if you use the default Kconfig (MTD_UBI_BEB_LIMIT == 20) then this won't take effect. Accepting the default seems a little different than "I chose a value in Kconfig." I think we could probably reconcile this by dropping the Kconfig (as Richard suggested), and defaulting to 20 if neither cmdline nor autodetect (e.g., ONFI) have said otherwise. Or if y'all agree that the behavior I mentioned is fine, I can still take this on behalf of Richard. Brian
