Re: [Ltib] How do we do firmware version control for Embedded Linux Device?

[Stuart Hughes]

Hi Quentin,

This is not really a LTIB question so much as a configuration management
 policy.

LTIB and other build systems are not really intended to provide
configuration management for packages.  The idea is they use some
pristine upstream release and then add as few patches on top as are
needed to get the thing working.  Furthermore in an ideal world the
patch that are generally useful should be pushed back to the upstream
maintainer.

Given this point, if you just add a patch to an existing package in
LTIB, then you should just update the Revision in the package.

If you change the baseline, you should change the package version,
generally to match the released package version.

Regards, Stuart

Quentin YANG wrote:
> Hi,
> 
> When new drivers are added into Linux Kernel and new board info is added
> into u-boot to work on customized prototype hardware, clearly from that
> point on we need to have some way to maintain the version of these new
> changes.
> 
> When bugs do appear in modified u-boot and patched Linux Kernel, we need
> to know what U-boot and Linux-Kernel are used in the field.
> 
> So, firstly, is there any rules to change the Linux Kernel version and
> U-Boot version for Embedded Linux Device? (Add extra version after
> kernel version like 2.6.34-0.0.1 or what else? )
> Secondly, where do we change the Linux Kernel version and U-Boot version
> in source files?
> 
> Thanks. Hope someone have thought after and got experience on this.
> 
> 
> Regards,
> Quentin
>