From: Mario Domenech Goulart <mario@ossystems.com.br>
To: Daiane Angolini <daiane.angolini@freescale.com>
Cc: meta-freescale@yoctoproject.org
Subject: Re: [Documentation][RFC 2/3] RN: Update BSP scope to point external links and Freescale RN
Date: Wed, 11 Jun 2014 18:12:15 +0000 [thread overview]
Message-ID: <87sinbjoxs.fsf@parenteses.org> (raw)
In-Reply-To: <1402508298-5176-2-git-send-email-daiane.angolini@freescale.com> (Daiane Angolini's message of "Wed, 11 Jun 2014 14:38:17 -0300")
Hi Daiane,
On Wed, 11 Jun 2014 14:38:17 -0300 Daiane Angolini <daiane.angolini@freescale.com> wrote:
> The Release Notes for the kernel is out of scope of this RN.
>
> Please, help me to add the better pointer for release notes
> out of scope of FSL Community BSP but important for
> development, such as kernel release notes for linux providers
> others that linux-imx.
>
> Signed-off-by: Daiane Angolini <daiane.angolini@freescale.com>
> ---
> release-notes/source/bsp-scope.rst | 31 +++++++++++++++++++++++++++++--
> 1 file changed, 29 insertions(+), 2 deletions(-)
>
> diff --git a/release-notes/source/bsp-scope.rst b/release-notes/source/bsp-scope.rst
> index 5035403..f036310 100644
> --- a/release-notes/source/bsp-scope.rst
> +++ b/release-notes/source/bsp-scope.rst
> @@ -1,7 +1,34 @@
> -BSP Scope
> +Scope
> =========
>
> -The scope of this release includes both meta-fsl-arm and meta-fsl-arm-extra.
> +FSL Community BSP Scope
> +---------
> +The scope of this Release Notes includes the FSL Community BSP meta layers:
s/Release Notes/Release Notes document/
> +
> + * `meta-fsl-arm <http://git.yoctoproject.org/cgit/cgit.cgi/meta-fsl-arm/?h=daisy>`_:
> + provides the base support and Freescale ARM reference boards;
> + * `meta-fsl-arm-extra <https://github.com/Freescale/meta-fsl-arm-extra/tree/daisy>`_:
> + provides support for 3rd party and partner boards;
> + * `meta-fsl-demos <https://github.com/Freescale/meta-fsl-demos/tree/daisy>`_:
> + provides images recipes, demo recipes, and packagegroups used to easy the development with Yocto Project.
s/easy/ease/
> + * `Documentation <https://github.com/Freescale/Documentation>`_
> + provides the source code for FSL Community BSP Release Notes (RN), User Guide (UG) and
> + Frequentely Asked Question (FAQ)
s/Frequentely/Frequently/
s/Question/Questions/
> +
> +Kernel Release Notes
> +--------------------
> +
> +The FSL Community BSP include support for several kernel providers
s/include/includes/
> , each machine
> +may have a different Linux Kernel provider.
I'd finish the previous sentence and start a new one: ". Each machine
may have a different Linux Kernel provider."
> +
> +For the provider **linux-imx**, Freescale has a Release Notes for each version released,
s/Release Notes/Release Notes document/
> +this document has a list of known issues, new features, list of kernel arguments, and the
> +linux-imx kernel scope for each Freescale Reference Board.
> +
> +See the respective Linux Kernel provider for your machine in section :ref:`linux-providers`
> +
> +Supported Board List
> +--------------------
> Please, see in next table the complete supported board list.
Not part of the diff, but while I'm here, I suggest
Please, see the next table for the complete list of supported boards.
Best wishes.
Mario
--
http://www.ossystems.com.br
next prev parent reply other threads:[~2014-06-11 18:12 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-11 17:38 [Documentation][RFC 1/3] RN: Add pointer to kernel linux section Daiane Angolini
2014-06-11 17:38 ` [Documentation][RFC 2/3] RN: Update BSP scope to point external links and Freescale RN Daiane Angolini
2014-06-11 17:51 ` Daiane.Angolini
2014-06-11 18:12 ` Mario Domenech Goulart [this message]
2014-06-11 18:17 ` Daiane.Angolini
2014-06-12 6:58 ` zhenhua.luo
2014-06-12 12:58 ` Otavio Salvador
2014-06-12 13:18 ` Daiane.Angolini
2014-06-11 17:38 ` [Documentation][RFC 3/3] RN: Add the Release Schedule section Daiane Angolini
2014-06-11 18:02 ` Mario Domenech Goulart
2014-06-18 18:16 ` Daiane Angolini
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87sinbjoxs.fsf@parenteses.org \
--to=mario@ossystems.com.br \
--cc=daiane.angolini@freescale.com \
--cc=meta-freescale@yoctoproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.