[oe] [RFC] Rebuild external kernel modules on kernel change

[Tom Rini]

On Sat, Apr 04, 2009 at 03:31:25PM +0200, Koen Kooi wrote:

> Hi,
>
> For beagleboard I have a few things I need to rebuild everytime the  
> kernel changes:
>
> * powervr kerneldrivers
> * sdma kernel module
> * dmai kernel module
> * codec-engine
>
> And I have roughly two kinds of kernel changes:
>
> 1) version upgrade (e.g. 2.6.29 -> 2.6.29)

Based on the rest of the email, I assume you mean 2.6.28 -> 2.6.29

> 2) config changes (e.g. enable ethernet bridging)

So, by coincidence I had this thread around still.  For (1), you already
have kernel-abiversion, but maybe we need some helpers to make this more
useful?  For (2) that's not true unless you're changing one of the
variables that actually changes the running kernel abi (which isn't
caught in kernel-abiversion file).  This shouldn't be a frequent
operation.  There is, I suppose a 3rd problem which would be within
version API changes, for new and in-progress features.  This I'm not
sure we need a complex mechanism around for.  Use/publish WIP stuff,
make sure users understand it's WIP and bump PRs as needed, manually.

-- 
Tom Rini