From: Dirk Behme <dirk.behme@googlemail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] mtd: Update MTD infrastructure to support 64bit device size
Date: Mon, 22 Jun 2009 20:38:07 +0200 [thread overview]
Message-ID: <4A3FCF8F.1050405@googlemail.com> (raw)
In-Reply-To: <200906222025.36131.sr@denx.de>
Stefan Roese wrote:
> On Monday 22 June 2009 20:12:11 Dirk Behme wrote:
>>>> 1. This preprocessor warning is annoying. Why not enable it in all
>>>> configs where needed and then remove this warning here?
>>> I could have done that, but this would not have been so easy. Especially
>>> with so many new board ports pending in the u-boot-arch/next branches at
>>> that time. And upcoming board ports would probably fallen through the
>>> crack as well. So I decided to do it this way.
>> Is this a long term solution or only waiting for all u-boot-arch/next
>> branches to be merged?
>
> I don't understand this question. The current code with this check is
> available in mainline. Or not?
Sorry, yes, but you mentioned above pending boards and not merged next
branches. So my question was if you plan to change the warning after
all pending boards and next branches are merged.
>> For a long term solution this would be annoying. Maybe we can change
>> this after merge window closed?
>
> Why? There could still be new board ports using this NAND code without
> defining this 64bit printf format option. I don't think this check really
> hurts.
Because every non-U-Boot expert who just downloads recent git and
compiles it will get the warning and will wonder if something is wrong
or not. So yes, the check doesn't hurt, but the warning might confuse
the users, which are non-experts.
It's similar to the "WARNING - bad CRC or NAND, using default
environment." runtime warning. There are tons on questions on various
mailing lists if this is an error or not ;)
> We could get rid of it of course if we would enable this 64bit printf format
> on all platforms and removed this option completely. This would cost a bit of
> image size but would make things easier/simpler. Just my 0.02$...
For OMAP3 I would enabled this option, independent of image size, just
to get rid of the warning.
Best regards
Dirk
next prev parent reply other threads:[~2009-06-22 18:38 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-11 14:03 [U-Boot] [PATCH] mtd: Update MTD infrastructure to support 64bit device size Stefan Roese
2009-05-11 16:27 ` Mike Frysinger
2009-05-11 16:38 ` Stefan Roese
2009-05-11 16:57 ` Mike Frysinger
2009-05-11 20:06 ` Scott Wood
2009-05-11 17:59 ` Wolfgang Denk
2009-05-12 4:39 ` Stefan Roese
2009-05-12 5:11 ` Mike Frysinger
2009-05-12 8:14 ` Wolfgang Denk
2009-05-12 8:26 ` Stefan Roese
2009-06-03 21:49 ` Wolfgang Denk
2009-06-20 5:33 ` Dirk Behme
2009-06-20 8:52 ` Jean-Christophe PLAGNIOL-VILLARD
2009-06-20 17:45 ` Dirk Behme
2009-06-22 12:01 ` Stefan Roese
2009-06-22 18:10 ` Dirk Behme
2009-06-22 18:21 ` Stefan Roese
2009-06-28 5:47 ` Dirk Behme
2009-06-29 14:35 ` Stefan Roese
2009-06-22 12:55 ` Stefan Roese
2009-06-22 18:12 ` Dirk Behme
2009-06-22 18:25 ` Stefan Roese
2009-06-22 18:38 ` Dirk Behme [this message]
2009-06-22 18:50 ` Scott Wood
2009-06-22 19:26 ` Stefan Roese
2009-06-22 19:49 ` Dirk Behme
2009-06-22 19:52 ` Scott Wood
2009-06-22 20:04 ` Dirk Behme
2009-06-22 20:08 ` Scott Wood
2009-06-22 20:15 ` Dirk Behme
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=4A3FCF8F.1050405@googlemail.com \
--to=dirk.behme@googlemail.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