Skip to contentSkip to conversation

Size of Samsung NAND id 0xD5 in nand_flash_ids[]

DISCUSSION Vaibhav AGARWAL 2 participants 2 messages Apr 14, 2009 Memory technology devices (MTD)

lore
Share & tools
lore

Vaibhav AGARWAL

author
#0 lore raw

Hi,

I m using Samsung K9WBG08U1M NAND. And after looking at Samsung's product decoder sheet, I can decode it's size as 4GiB. However, on matching it's signature id i.e. 0xD5 in 'nand_flash_ids[]' table, I can see it's size defined to be 2GiB by mtd framework. Is there any specific reason for doing so?

Regards,
Vaibhav.

#1 lore raw

Hi Vaibhav,

In 32 bit operation, max data can be represented upto 4GiB - 1. In this given condition you can map the pages of size 4GiB - 1
(As highest msb in 32 bit operation is represented by 2^31 only);

Regards,
Ravi Kumar

________________________________________
From: [email protected] [[email protected]] On Behalf Of Vaibhav AGARWAL [[email protected]]
Sent: Tuesday, April 14, 2009 16:42
To: [email protected]
Subject: Size of Samsung NAND id 0xD5 in nand_flash_ids[]

Hi,

I m using Samsung K9WBG08U1M NAND. And after looking at Samsung's product decoder sheet, I can decode it's size as 4GiB. However, on matching it's signature id i.e. 0xD5 in 'nand_flash_ids[]' table, I can see it's size defined to be 2GiB by mtd framework. Is there any specific reason for doing so?

Regards,
Vaibhav.

______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
SASKEN BUSINESS DISCLAIMER
-------------------------
This message may contain confidential, proprietary or legally privileged information. In case you are not the original intended Recipient of the message, you must not, directly or indirectly, use, Disclose, distribute, print, or copy any part of this message and you are requested to delete it and inform the sender. Any views expressed in this message are those of the individual sender unless otherwise stated. Nothing contained in this message shall be construed as an offer or acceptance of any offer by Sasken Communication Technologies Limited ("Sasken") unless sent with that express intent and with due authority of Sasken. Sasken has taken enough precautions to prevent the spread of viruses. However the company accepts no liability for any damage caused by any virus transmitted by this email