I use tools/indent.sh when I need to reformat a file.  It is imperfect, but
can reduce the 1000's to 100's (see the README for quirks).  It doesn't fix
naming, of course.

On Sat, Jan 15, 2022 at 6:30 AM fft <f...@feedforward.com.cn> wrote:

> It seems that there are thousands of coding style problem,I was
> frightened....this is a difficult task for me,Is there any tools that can
> automatically modify the coding style problem?&nbsp;
> &nbsp;
> ------------------&nbsp;Original&nbsp;------------------
> From: &nbsp;"Alan&nbsp;Carvalho&nbsp;de&nbsp;Assis"<acas...@gmail.com&gt;;
> Date: &nbsp;Sat, Jan 15, 2022 07:38 PM
> To: &nbsp;"dev"<dev@nuttx.apache.org&gt;;
>
> Subject: &nbsp;Re: Support of SPARC architecture
>
> &nbsp;
>
> That is a great news mister Zou!
>
> I saw there are some file that need to have its coding style fixed to
> pass in the CI test:
>
> https://github.com/apache/incubator-nuttx/runs/4826456444?check_suite_focus=true
>
> You can also check locally the coding style using the checkpatch, this way:
>
> $ ./tools/checkpatch.sh -f arch/arm/src/am335x/am335x_boot.c
>
> In this case am335x_boot.c doesn't have any issue, then it doesn't
> return anything, but your files with issues will return hints
> explaining which line you need to modify.
>
> BR,
>
> Alan
>
> On 1/15/22, fft <f...@feedforward.com.cn&gt; wrote:
> &gt; I have commit code to add SPARC support&amp;nbsp;
> &gt; &amp;nbsp;
> &gt; ------------------&amp;nbsp;Original&amp;nbsp;------------------
> &gt; From: &amp;nbsp;"Alan&amp;nbsp;Carvalho&amp;nbsp;de&amp;nbsp;Assis"<
> acas...@gmail.com&amp;gt;;
> &gt; Date: &amp;nbsp;Wed, Jan 12, 2022 08:57 PM
> &gt; To: &amp;nbsp;"dev"<dev@nuttx.apache.org&amp;gt;;
> &gt;
> &gt; Subject: &amp;nbsp;Re: Support of SPARC architecture
> &gt;
> &gt; &amp;nbsp;
> &gt;
> &gt; Hi Zou,
> &gt;
> &gt; That is amazing! We have already companies using NuttX for satellites
> &gt; (there is a video about it at NuttX Channel).
> &gt;
> &gt; Yes, please submit a Pull Request in our github to add Spark support,
> &gt; that will be welcome!
> &gt;
> &gt; BR,
> &gt;
> &gt; Alan
> &gt;
> &gt; On 1/12/22, fft <f...@feedforward.com.cn&amp;gt; wrote:
> &gt; &amp;gt;
> &gt; &amp;gt; Hi, Teams
> &gt; &amp;gt;
> &gt; &amp;gt;
> &gt; &amp;gt;Two years ago, we tried to use NuttX on satellites,
> &gt; &amp;gt; and I started the work to porting nuttx to BM3803, a SPARC V8
> &gt; &amp;gt; architecture chip manufactured by BMTI(Beijing
> Microelectronics
> &gt; Technology
> &gt; &amp;gt; Institute) which is based on open source CPU core----LEON 2
> released
> &gt; &amp;gt; by Cobham Gaisler. about the SPARC V8 and LEON 2 see :
> &gt; &amp;gt;
> &gt; &amp;gt; https://www.gaisler.com/index.php/products/processors
> &gt <https://www.gaisler.com/index.php/products/processors&gt>; &amp;gt;
> &gt; &amp;gt; BTW the chip of AT697F of ESA(European Space
> &gt; &amp;gt; Agency) is also based on LEON 2 see:
> &gt; &amp;gt;
> &gt; &amp;gt;
> &gt;
> https://amstel.estec.esa.int/tecedm/website/conferences/PresentationDays/AT697_Atmel.pdf
> &gt; &amp;gt;
> &gt; &amp;gt;I finished the whole work last year, Include
> &gt; &amp;gt; architecture support code and board support code, I even
> completed and
> &gt; &amp;gt; verified the Tickless OS mode and ELF file separate load on
> this SPARC
> &gt; V8
> &gt; &amp;gt; chip. Due to some reasons, the project leader did not adopt
> nuttx in
> &gt; the
> &gt; &amp;gt; end, and I want to contribute code to the community.
> &gt; &amp;gt;
> &gt; &amp;gt;
> &gt; &amp;gt; The Toolchain of SPARC V8 is standard SPARC gnu gcc
> &gt; &amp;gt; released by Gaisler which can be download at:
> &gt; &amp;gt;
> &gt; &amp;gt;
> &gt; &amp;gt; https://www.gaisler.com/index.php/downloads/compilers
> &gt <https://www.gaisler.com/index.php/downloads/compilers&gt>; &amp;gt;
> &gt; &amp;gt;
> &gt; &amp;gt; I initiated this discussion to seek your opinions,
> &gt; &amp;gt; whether NuttX agree to include the SPARC arch in the scope
> of support
> &gt; ?
> &gt; &amp;gt;
> &gt; &amp;gt;
> &gt; &amp;gt; Best regards,
> &gt; &amp;gt; Zou

Reply via email to