All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stefan Agner <stefan@agner.ch>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v3 5/5] mtd: nand: mxs_nand: add minimal ECC support
Date: Fri, 22 Jun 2018 13:36:17 +0200	[thread overview]
Message-ID: <296759aaeab66903bdc81a1adb2a123f@agner.ch> (raw)
In-Reply-To: <cbefd969-afc4-2cfa-761a-08db201ca802@denx.de>

On 22.06.2018 10:46, Stefano Babic wrote:
> Hi Stefan,
> 
> On 21/06/2018 18:39, Stefano Babic wrote:
>> Hi Stefan,
>>
>> On 21/06/2018 17:22, Tom Rini wrote:
>>> On Thu, Jun 21, 2018 at 01:46:10PM +0200, Stefan Agner wrote:
>>>
>>>> Tom, Stefano,
>>>>
>>>> Scott Wood seems not to be very active this days in the U-Boot
>>>> community.
>>>>
>>>> This patchsets seem all to be blocked due to that:
>>>> https://patchwork.ozlabs.org/cover/897263/
>>>> https://patchwork.ozlabs.org/cover/901995/
>>>> https://patchwork.ozlabs.org/patch/922907/
>>>>
>>>> Those patches have been around quite a while and I tested them well. Any
>>>> change to get that still in?
>>>
>>> I don't object to those coming in via one of the SoC trees, thanks!
>>>
>>
>> Ok - we have a general agreement, I pick your patches into u-boot-imx.
>>
> 
> I get several broken boards and many warnings when I build with your
> patches. Maybe have I missed some of them ? I have pushed a temporary
> branch (nand-imx) on the server, let me know if I miss something.

Patches look good.

> 
> There are 15 boards broken, errors seem trivial but I do not want to fix
> anything without showing to you. There are mainly two issues, for example:
> 
> drivers/mtd/nand/mxs_nand_spl.c: In function ?mxs_nand_init?:
> drivers/mtd/nand/mxs_nand_spl.c:148:2: error: too many arguments to
> function ?board_nand_init?
>   board_nand_init(&nand_chip);
>   ^~~~~~~~~~~~~~~
> In file included from drivers/mtd/nand/mxs_nand_spl.c:7:0:
> include/nand.h:39:6: note: declared here
>  void board_nand_init(void);
>       ^~~~~~~~~~~~~~~
> make[4]: *** [spl/drivers/mtd/nand/mxs_nand_spl.o] Error 1
> make[3]: *** [spl/drivers/mtd/nand] Error 2
> make[2]: *** [spl/drivers] Error 2
> make[1]: *** [spl/u-boot-spl] Error 2
> make: *** [sub-make] Error 2
> 
> 
> The second one is a missing include, like in mx28evk:
> 
> 
> drivers/mtd/nand/mxs_nand.c: In function ?mxs_nand_calc_ecc_layout_by_info?:
> drivers/mtd/nand/mxs_nand.c:172:7: error: ?SZ_512? undeclared (first use
> in this function)
>   case SZ_512:
>        ^~~~~~
> drivers/mtd/nand/mxs_nand.c:172:7: note: each undeclared identifier is
> reported only once for each function it appears in
> drivers/mtd/nand/mxs_nand.c:175:7: error: ?SZ_1K? undeclared (first use
> in this function)
>   case SZ_1K:
>        ^~~~~
> make[2]: *** [drivers/mtd/nand/mxs_nand.o] Error 1
> make[1]: *** [drivers/mtd/nand] Error 2
> make: *** [sub-make] Error 2
> 
> Can you take a look ?

Hm, I thought I did some testing across all boards, but maybe not with
all patches applied.

Will look into it.

--
Stefan

      reply	other threads:[~2018-06-22 11:36 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-11 16:04 [U-Boot] [PATCH v3 0/5] mtd: nand: mxs_nand: improve ECC support Stefan Agner
2018-04-11 16:04 ` [U-Boot] [PATCH v3 1/5] mtd: nand: mxs_nand: use self init Stefan Agner
2018-04-11 16:04 ` [U-Boot] [PATCH v3 2/5] mtd: nand: mxs_nand: allow to enable BBT support Stefan Agner
2018-04-11 16:04 ` [U-Boot] [PATCH v3 3/5] mtd: nand: mxs_nand: use structure for BCH geometry Stefan Agner
2018-04-11 16:04 ` [U-Boot] [PATCH v3 4/5] mtd: nand: mxs_nand: report correct ECC parameters Stefan Agner
2018-04-11 16:04 ` [U-Boot] [PATCH v3 5/5] mtd: nand: mxs_nand: add minimal ECC support Stefan Agner
2018-04-27  7:31   ` Stefano Babic
2018-04-30  8:08     ` Stefan Agner
2018-05-30 14:51       ` Stefan Agner
2018-06-21 11:46         ` Stefan Agner
2018-06-21 15:22           ` Tom Rini
2018-06-21 16:39             ` Stefano Babic
2018-06-22  8:46               ` Stefano Babic
2018-06-22 11:36                 ` Stefan Agner [this message]

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=296759aaeab66903bdc81a1adb2a123f@agner.ch \
    --to=stefan@agner.ch \
    --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 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.