[meta-freescale] [Documentation][PATCH] RN: Updates from bitbake-metadata2doc.sh
Daiane Angolini
daiane.list at gmail.com
Sat Nov 15 06:16:25 PST 2014
On Sat, Nov 15, 2014 at 11:29 AM, Daiane Angolini <daiane.list at gmail.com> wrote:
> Signed-off-by: Daiane Angolini <daiane.angolini at freescale.com>
This update is for dizzy.
Now, we have included the LOCALVERSION in the kernel (and bootloader)
providers to be used in Release Notes.
This is important to differentiate if one 3.10.17 kernel is 1.0.0 or
1.0.2 version.
the "+git" sufix indicate the project is something after the tag, in
other words, it includes more commits (from git) after the formal
release version.
However, it highlighted some LOCALVERSION with redundant or useless
content, and this is the point I want to discuss.
> diff --git a/release-notes/source/linux-default.inc b/release-notes/source/linux-default.inc
> index 6387006..0e6060b 100644
> --- a/release-notes/source/linux-default.inc
> +++ b/release-notes/source/linux-default.inc
> @@ -1,45 +1,45 @@
> ====================== =============== =======================
> -Board Kernel Provider Kernel Version
> +Board Kernel Provider Kernel Version
> ====================== =============== =======================
> -cfa10036 linux-cfa 3.12
> -cfa10037 linux-cfa 3.12
> -cfa10049 linux-cfa 3.12
> -cfa10055 linux-cfa 3.12
> -cfa10056 linux-cfa 3.12
> -cfa10057 linux-cfa 3.12
> -cfa10058 linux-cfa 3.12
> -cgtqmx6 linux-congatec 3.10.17-1.0.0_qmx6
> -cubox-i linux-cubox-i 3.14.14-cubox-i+yocto
> -imx233-olinuxino-maxi linux-fslc 3.17+git
> -imx233-olinuxino-micro linux-fslc 3.17+git
> -imx233-olinuxino-mini linux-fslc 3.17+git
> -imx233-olinuxino-nano linux-fslc 3.17+git
> -imx23evk linux-fslc 3.17+git
> +cfa10036 linux-cfa 3.12
> +cfa10037 linux-cfa 3.12
> +cfa10049 linux-cfa 3.12
> +cfa10055 linux-cfa 3.12
> +cfa10056 linux-cfa 3.12
> +cfa10057 linux-cfa 3.12
> +cfa10058 linux-cfa 3.12
> +cgtqmx6 linux-congatec 3.10.17-1.0.0_qmx6
What does _qmx6 means?
> +cubox-i linux-cubox-i 3.14.14-cubox-i+yocto
Does it make sense to have a +yocto sufix for this kernel?
> +imx233-olinuxino-maxi linux-fslc 3.17+git
> +imx233-olinuxino-micro linux-fslc 3.17+git
> +imx233-olinuxino-mini linux-fslc 3.17+git
> +imx233-olinuxino-nano linux-fslc 3.17+git
> +imx23evk linux-fslc 3.17+git
> imx28evk linux-imx 2.6.35.3-maintain+yocto
I really believe this +yocto is not needed any more and I'm going to
send a patch to remove/fix this. (for this and for other linux-imx
boards)
> -imx31pdk linux-fslc 3.17+git
> -imx35pdk linux-fslc 3.17+git
> +imx31pdk linux-fslc 3.17+git
> +imx35pdk linux-fslc 3.17+git
> imx51evk linux-imx 2.6.35.3-maintain+yocto
> imx53ard linux-imx 2.6.35.3-maintain+yocto
> imx53qsb linux-imx 2.6.35.3-maintain+yocto
> -imx6dl-riotboard linux-fslc 3.17+git
> -imx6dlsabreauto linux-imx 3.10.17-1.0.1_ga
> -imx6dlsabresd linux-imx 3.10.17-1.0.1_ga
> -imx6qsabreauto linux-imx 3.10.17-1.0.1_ga
> -imx6qsabrelite linux-boundary 3.10.17-1.0.1_ga+yocto
> -imx6qsabresd linux-imx 3.10.17-1.0.1_ga
> -imx6slevk linux-imx 3.10.17-1.0.1_ga
> -imx6solosabreauto linux-imx 3.10.17-1.0.1_ga
> -imx6solosabresd linux-imx 3.10.17-1.0.1_ga
> -ls1021aqds linux-ls1 3.12+ls1
> -ls1021atwr linux-ls1 3.12+ls1
> -m28evk linux-fslc 3.17+git
> -m53evk linux-denx 3.9-denx
> -nitrogen6x linux-boundary 3.10.17-1.0.1_ga+yocto
> -nitrogen6x-lite linux-boundary 3.10.17-1.0.1_ga+yocto
> -pcl052 linux-timesys 3.0.15-3.0-mvf+yocto
> -pcm052 linux-timesys 3.0.15-3.0-mvf+yocto
> -quartz linux-timesys 3.0.15-3.0-mvf+yocto
> -twr-vf65gs10 linux-timesys 3.0.15-3.0-mvf+yocto
> +imx6dl-riotboard linux-fslc 3.17+git
> +imx6dlsabreauto linux-imx 3.10.17-1.0.2_ga
> +imx6dlsabresd linux-imx 3.10.17-1.0.2_ga
> +imx6qsabreauto linux-imx 3.10.17-1.0.2_ga
> +imx6qsabrelite linux-boundary 3.10.17-1.0.2_ga+yocto
Is +yocto needed in this case?
> +imx6qsabresd linux-imx 3.10.17-1.0.2_ga
> +imx6slevk linux-imx 3.10.17-1.0.2_ga
> +imx6solosabreauto linux-imx 3.10.17-1.0.2_ga
> +imx6solosabresd linux-imx 3.10.17-1.0.2_ga
> +ls1021aqds linux-ls1 3.12+ls1
> +ls1021atwr linux-ls1 3.12+ls1
What does +ls1 mean in this case?
Would it be redundant to have +ls1 included in a kernel running on a ls1 board?
> +m28evk linux-fslc 3.17+git
> +m53evk linux-denx 3.9-denx
> +nitrogen6x linux-boundary 3.10.17-1.0.2_ga+yocto
> +nitrogen6x-lite linux-boundary 3.10.17-1.0.2_ga+yocto
> +pcl052 linux-timesys 3.0.15-3.0-mvf+yocto
> +pcm052 linux-timesys 3.0.15-3.0-mvf+yocto
> +quartz linux-timesys 3.0.15-3.0-mvf+yocto
> +twr-vf65gs10 linux-timesys 3.0.15-3.0-mvf+yocto
> wandboard-dual linux-wandboard 3.10.17-1.0.1-wandboard
> wandboard-quad linux-wandboard 3.10.17-1.0.1-wandboardPlease
> wandboard-solo linux-wandboard 3.10.17-1.0.1-wandboard
Is "wandboard" sufix needed in a kernel running inside a wandboard?
I found almost the same for bootloader.
I'm going to create a patch for linux-imx and u-boot-imx.
Daiane
More information about the meta-freescale
mailing list