On Mon, Feb 17, 2014 at 03:35:18PM +0000, One Thousand Gnomes wrote:

We've identified a correct working approach which is to simply add a
CONFIG entry to the ARM tree and a few ifdefs to the problem drivers to
make the "problem" (in fact a complete fictional non-problem) go away and
to get rid of the mess over time completely as the drivers are set
dynamic and it turns out that all the userspace happens to already handle
this just fine.

It's a very real problem which affects actual kernels that distro style
users are building.