From: tigmac <chromy@asix.cz>
To: buildroot@busybox.net
Subject: [Buildroot] svn commit: trunk/buildroot/target/device/Atmel/at91bootstrap
Date: Tue, 3 Feb 2009 00:23:37 -0800 (PST) [thread overview]
Message-ID: <21805444.post@talk.nabble.com> (raw)
I am afraid that AT91Bootstrap version 2.10 is broken regarding NAND flash.
The main problem being in Makefile:
ifeq ($(CONFIG_NANDFLASH),y)
CPPFLAGS += -DCONFIG_NAND_FLASH
endif
See the extra underscore which should not be there?
Unfortunately this is not the only problem, even if Makefile is corrected,
there is an #include missing
in driver/nandflash.c causing the compilation to fail. In other words
version 2.10 is buggy like hell,
at least concerning NADN flash.
Unless you are willing to fix it yourself, I recommend using version 2.4.
BTW if I would like to submit a patch for AT91Bootstrap, where should I send
it so that it makes its way
info the official release?
--
View this message in context: http://www.nabble.com/svn-commit%3A-trunk-buildroot-target-device-Atmel-at91bootstrap-tp21404604p21805444.html
Sent from the BuildRoot mailing list archive at Nabble.com.
next reply other threads:[~2009-02-03 8:23 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-03 8:23 tigmac [this message]
2009-02-03 8:30 ` [Buildroot] svn commit: trunk/buildroot/target/device/Atmel/at91bootstrap Peter Korsgaard
-- strict thread matches above, loose matches on Subject: below --
2009-01-29 21:28 ulf at uclibc.org
2009-01-29 20:52 ulf at uclibc.org
2009-01-11 21:44 ulf at uclibc.org
2009-01-13 17:00 ` Matt Wood
2009-01-15 22:47 ` Ulf Samuelsson
2009-01-06 16:36 ulf at uclibc.org
2008-04-10 21:05 ulf at uclibc.org
2008-03-11 16:19 ninevoltz at uclibc.org
2007-10-21 20:13 ulf at uclibc.org
2007-09-24 22:24 ulf at uclibc.org
2007-08-15 9:42 ulf at uclibc.org
2007-07-29 7:09 ulf at uclibc.org
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=21805444.post@talk.nabble.com \
--to=chromy@asix.cz \
--cc=buildroot@busybox.net \
/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.