public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Jean-Christophe PLAGNIOL-VILLARD <plagnioj@jcrosoft.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] Pull request: nand-flash
Date: Wed, 13 Aug 2008 01:06:33 +0200	[thread overview]
Message-ID: <20080812230633.GC30514@game.jcrosoft.org> (raw)
In-Reply-To: <20080812163747.GA11066@ld0162-tx32.am.freescale.net>

On 11:37 Tue 12 Aug     , Scott Wood wrote:
> These patches are from the testing/mtd-2.6.22.1 branch of
> u-boot-nand-flash.
> 
> Note that this is a significant change to the NAND subsystem (importing a
> newer upstream version) that affects the driver interface.  If your board
> has NAND, please test.
> 
> The following changes since commit cd82919e6c8a73b363a26f34b734923844e52d1c:
>   Wolfgang Denk (1):
>         Coding style cleanup, update CHANGELOG, prepare release
> 
> are available in the git repository at:
> 
>   git://www.denx.de/git/u-boot-nand-flash.git master

With this patchset, a lot of arm board are broken

nand.c: In function 'at91cap9adk_nand_hwcontrol':
nand.c:47: error: 'NAND_CTL_SETCLE' undeclared (first use in this
function)
nand.c:47: error: (Each undeclared identifier is reported only once
nand.c:47: error: for each function it appears in.)
nand.c:50: error: 'NAND_CTL_SETALE' undeclared (first use in this
function)
nand.c:53: error: 'NAND_CTL_CLRNCE' undeclared (first use in this
function)
nand.c:56: error: 'NAND_CTL_SETNCE' undeclared (first use in this
function)
nand.c: In function 'board_nand_init':
nand.c:65: error: 'struct nand_chip' has no member named 'eccmode'
nand.c:69: error: incompatible types in assignment
make[1]: *** [nand.o] Error 1

Configuring for apollon board...
onenand_base.c: In function 'onenand_bufferram_offset':
onenand_base.c:331: error: 'struct mtd_info' has no member named
'oobblock'
onenand_base.c: In function 'onenand_read_ecc':
onenand_base.c:541: error: 'struct mtd_info' has no member named
'oobblock'
onenand_base.c:543: error: 'struct mtd_info' has no member named
'oobblock'
onenand_base.c:544: error: 'struct mtd_info' has no member named
'oobblock'
onenand_base.c:545: error: 'struct mtd_info' has no member named
'oobblock'
onenand_base.c:549: error: 'struct mtd_info' has no member named
'oobblock'
onenand_base.c: In function 'onenand_read_oob':
onenand_base.c:664: error: 'struct mtd_info' has no member named
'oobblock'
onenand_base.c: In function 'onenand_write_ecc':
onenand_base.c:749: error: 'struct mtd_info' has no member named
'oobblock'
onenand_base.c:749: error: 'struct mtd_info' has no member named
'oobblock'
onenand_base.c:760: error: 'struct mtd_info' has no member named
'oobblock'
onenand_base.c:762: error: 'struct mtd_info' has no member named
'oobblock'
onenand_base.c:768: error: 'struct mtd_info' has no member named
'oobblock'
onenand_base.c: In function 'onenand_probe':
onenand_base.c:1212: error: 'struct mtd_info' has no member named
'oobblock'
onenand_base.c:1214: error: 'struct mtd_info' has no member named
'oobblock'
onenand_base.c:1216: error: 'struct mtd_info' has no member named
'oobblock'
onenand_base.c:1219: error: 'struct mtd_info' has no member named
'oobblock'
onenand_base.c:1221: error: 'struct mtd_info' has no member named
'oobblock'
onenand_base.c:1243: error: 'struct mtd_info' has no member named
'read_ecc'
onenand_base.c:1244: error: 'struct mtd_info' has no member named
'write_ecc'
onenand_base.c:1245: warning: assignment from incompatible pointer type
onenand_base.c:1246: warning: assignment from incompatible pointer type
make[1]: *** [onenand_base.o] Error 1

etc...

what do we do?

Best Regards,
J.

  parent reply	other threads:[~2008-08-12 23:06 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-12 16:37 [U-Boot] Pull request: nand-flash Scott Wood
2008-08-12 20:01 ` Wolfgang Denk
2008-08-12 23:06 ` Jean-Christophe PLAGNIOL-VILLARD [this message]
2008-08-13 16:06   ` Scott Wood
  -- strict thread matches above, loose matches on Subject: below --
2008-08-13 23:38 Scott Wood
2008-08-14 11:02 ` Wolfgang Denk
2008-08-21 19:06 Scott Wood
2008-08-22 22:10 ` Wolfgang Denk
2008-09-12 20:13 Scott Wood
2008-09-12 23:46 ` Wolfgang Denk
2008-10-17 15:41 Scott Wood
2008-10-17 19:31 ` 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=20080812230633.GC30514@game.jcrosoft.org \
    --to=plagnioj@jcrosoft.com \
    --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