On Sun, 26 Jan 2014 22:09:07 +0100 Pavel Machek <pavel@xxxxxx> wrote: > On Thu 2014-01-23 19:36:33, Mark Brown wrote: > > On Thu, Jan 23, 2014 at 07:47:56PM +0100, Tomasz Figa wrote: > > > On 23.01.2014 19:40, Mark Brown wrote: > > > > > >We'd need to leave it user selectable rather than enabling it for ARM, > > > >the whole reason this got noticed is that people are trying to build > > > >kernels that support a wider range of devices for ARM. > > > > > What about making it depend on !MULTIPLATFORM and enabled by default? > > > > That'd work, but if we're doing that then substituting in the dynamic > > assignment only when we hit a collision seems smoother and more general. > > That seems like a mess. I had enough fun debugging "WTF is > going on with my serials" as is... > > Plus... collision can happen at runtime when you insert > BT CF card... at that point it is too late to reassign. Agreed entirely - you want predictability here, plus making it happen by magic is going to do the nut of anyone trying to figure out why kernel A works on their platform and kernel B doesn't. It needs to be something you choose to turn on as compatibility, like old sysfs files and so forth. -- To unsubscribe from this list: send the line "unsubscribe linux-serial" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
