[PATCH v3 2/2] update README with instructions for stm32 patch

[Vijay Kumar Banerjee]

Hi Robin,

Looks like this patch answers one of my questions in the other patch.
This looks good and can be merged after the first patch.

Thanks!

On Sun, Oct 24, 2021 at 4:59 AM Robin Müller <robin.mueller.m at gmail.com> wrote:
>
> Hi,
>
> This patch now contains all files which have the problematic license so the
> RTMES LwIP code stays free of them.
> Actually, it probably would be a better idea if the patch is applied as
> part of the build process.. Does anyone have experience how to do this with
> waf?
>
> Kind Regards
> Robin Müller
>
> On Sun, 24 Oct 2021 at 12:54, Robin Mueller <robin.mueller.m at gmail.com>
> wrote:
>
> > ---
> >  README.md | 10 ++++++++++
> >  1 file changed, 10 insertions(+)
> >
> > diff --git a/README.md b/README.md
> > index ebbef12..3653b67 100644
> > --- a/README.md
> > +++ b/README.md
> > @@ -17,6 +17,16 @@ It is recommended that the user supplies the
> > `lwipopts.h` configuration file. Th
> >  contain template option files to get started. The user can copy and
> > rename this files into the
> >  application and then pass the include path to the build system using the
> > `--lwip-opts` option.
> >
> > +# Applying the STM32 patch file
> > +
> > +Some STM32 files are problematic due to the used license. Therefore, they
> > are applied in form of
> > +a patch. You need to perform the following steps in order to use the
> > STM32H7 BSP:
> > +
> > +```sh
> > +wget -O stm32.patch
> > https://raw.githubusercontent.com/robamu-org/rtems-stm32-lwip-port-patch/main/stm32-bsp-eth-dhcp-files.patch
> > +git am stm32.patch
> > +```
> > +
> >  # Building with waf
> >
> >  It is assumed that the path(s) containing the `lwipopts.h` file was
> > stored in the environmental
> > --
> > 2.32.0
> >
> >
> _______________________________________________
> devel mailing list
> devel at rtems.org
> http://lists.rtems.org/mailman/listinfo/devel