From: Nick Thompson <nick.thompson@ge.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] allow print_size to print large numbers on 32-bit systems
Date: Mon, 12 Apr 2010 17:16:24 +0100 [thread overview]
Message-ID: <4BC34758.3050706@ge.com> (raw)
In-Reply-To: <x2ped82fe3e1004120912u313a0c4du533a91f292ceaccc@mail.gmail.com>
On 12/04/10 17:12, Timur Tabi wrote:
> On Fri, Apr 9, 2010 at 3:40 PM, Wolfgang Denk <wd@denx.de> wrote:
>
>> If we make this change, we can probably use this function as well to
>> print the size of storage devices like NAND, USB Mass Storage, hard
>> disk drives, etc. Eventually we can clean up some pieces of code
>> then...
>
> I'm working on it now. I did notice something odd, though. The
> strings for sizes are GB, MB, and kB. Why is the "k" lowercase?
>
To differentiate from "K", which means 1000, rather than 1024.
Example Kg = 1000 grammes. kB = 1024 Bytes
Nick
next prev parent reply other threads:[~2010-04-12 16:16 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-30 23:02 [U-Boot] [PATCH] [v3] fix print_size printing fractional gigabyte numbers on 32-bit platforms Timur Tabi
2010-03-30 23:02 ` [U-Boot] [PATCH] allow print_size to print large numbers on 32-bit systems Timur Tabi
2010-04-09 20:22 ` Wolfgang Denk
2010-04-09 20:27 ` Timur Tabi
2010-04-09 20:40 ` Wolfgang Denk
2010-04-12 16:12 ` Timur Tabi
2010-04-12 16:16 ` Nick Thompson [this message]
2010-04-12 16:21 ` Timur Tabi
2010-04-12 16:27 ` Nick Thompson
2010-04-12 18:02 ` Wolfgang Denk
2010-04-12 17:59 ` Wolfgang Denk
2010-04-12 18:03 ` Timur Tabi
2010-04-12 18:20 ` Wolfgang Denk
2010-04-12 18:22 ` Scott Wood
2010-04-12 18:30 ` Timur Tabi
2010-04-12 18:50 ` Wolfgang Denk
2010-04-12 19:10 ` Timur Tabi
2010-04-12 19:26 ` Scott Wood
2010-04-09 20:10 ` [U-Boot] [PATCH] [v3] fix print_size printing fractional gigabyte numbers on 32-bit platforms Wolfgang Denk
2010-04-12 16:04 ` Timur Tabi
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=4BC34758.3050706@ge.com \
--to=nick.thompson@ge.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