public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Wolfgang Denk <wd@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v2 0/4] Add support new arch: c6x
Date: Sun, 24 Jun 2012 15:50:11 +0200	[thread overview]
Message-ID: <20120624135011.2AC1320223E@gemini.denx.de> (raw)
In-Reply-To: <31ab63da18246416f011fefc86653461.squirrel@78.108.93.81>

Dear bond at inmys.ru,

In message <31ab63da18246416f011fefc86653461.squirrel@78.108.93.81> you wrote:
>
> After rework, code in arch/c6x
> tools/checkpatch.pl 0001-Add-support-new-arch-c6x.patch tell me:
> "total: 0 errors, 39 warnings, 3065 lines checked"

Thanks.

> can i try send patch to list, or if not, what i must do with typedefs of
> global_data, volatile in asm/io.h and __kernel... types in
> asm/posix_types.h (all other arch has same code)?

If you really need to come up with your own versions of asm/io.h,
asm/posix_types.h etc. the typedefs are probably OK.

> WARNING: Use of volatile is usually wrong: see
> Documentation/volatile-considered-harmful.txt
> #394: FILE: arch/c6x/include/asm/io.h:14:
> +#define readb(addr) (*(volatile unsigned char *) (addr))

This is indeed unacceptable code, as it does not contain any kind of
memory barrier instructions.  Please use proper I/O accessors, resp.
define such.


Best regards,

Wolfgang Denk

-- 
DENX Software Engineering GmbH,     MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de
Life would be so much easier if we could  just  look  at  the  source
code.                                                   -- Dave Olson

  reply	other threads:[~2012-06-24 13:50 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <add_c6x_arch>
     [not found] ` <1340394370-1550-4-git-send-email-bond@inmys.ru>
2012-06-22 21:57   ` [U-Boot] [PATCH 3/4] c6x: Add suport build davinci SOC with c674x CPUs Tom Rini
2012-06-23 11:11 ` [U-Boot] [PATCH v2 0/4] Add support new arch: c6x Dmitry Bondar
2012-06-23 12:33   ` Wolfgang Denk
2012-06-24 11:40     ` bond at inmys.ru
2012-06-24 13:50       ` Wolfgang Denk [this message]
2012-06-23 11:11 ` [U-Boot] [PATCH v2 1/4] " Dmitry Bondar
2012-06-23 11:11 ` [U-Boot] [PATCH v2 2/4] c6x: Add support c674x CPUs Dmitry Bondar
2012-06-23 11:11 ` [U-Boot] [PATCH v2 3/4] c6x: Add suport build davinci SOC with " Dmitry Bondar
2012-06-23 11:11 ` [U-Boot] [PATCH v2 4/4] c6x: Add support c6745-som board Dmitry Bondar
2012-06-25 18:02 ` [U-Boot] [PATCH v3 0/4] Add support new arch: c6x Dmitry Bondar
2012-06-25 22:31   ` Tom Rini
2012-06-28 17:43     ` Dmitry Bondar
2012-06-28 18:02       ` Tom Rini
2012-06-25 18:02 ` [U-Boot] [PATCH v3 1/4] " Dmitry Bondar
2012-06-25 22:04   ` Tom Rini
2012-06-27 20:36     ` bond at inmys.ru
2012-06-27 20:55       ` Tom Rini
2012-06-27 22:16       ` Wolfgang Denk
2012-07-19  3:53   ` Mike Frysinger
2012-06-25 18:02 ` [U-Boot] [PATCH v3 2/4] c6x: Add support c674x CPUs Dmitry Bondar
2012-06-25 22:44   ` Tom Rini
2012-07-19  3:59   ` Mike Frysinger
2012-06-25 18:02 ` [U-Boot] [PATCH v3 3/4] c6x: Add suport build davinci SOC with " Dmitry Bondar
2012-06-25 22:46   ` Tom Rini
2012-06-27 15:27   ` [U-Boot] [PATCH] davinci, c6x: Always use C version of reset code Tom Rini
2012-06-27 15:28     ` Tom Rini
2012-07-19  4:00   ` [U-Boot] [PATCH v3 3/4] c6x: Add suport build davinci SOC with c674x CPUs Mike Frysinger
2012-06-25 18:02 ` [U-Boot] [PATCH v3 4/4] c6x: Add support c6745-som board Dmitry Bondar
2012-06-25 22:42   ` Tom Rini
2012-07-19  4:05   ` Mike Frysinger
2012-08-10 20:53   ` Wolfgang Denk

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=20120624135011.2AC1320223E@gemini.denx.de \
    --to=wd@denx.de \
    --cc=u-boot@lists.denx.de \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox