主题 : 用sd卡烧录的android2.3 空间是如何分配的? 复制链接 | 浏览器收藏 | 打印
我的个性签名
级别: 新手上路
UID: 28128
精华: 0
发帖: 42
金钱: 210 两
威望: 42 点
综合积分: 84 分
注册时间: 2010-09-06
最后登录: 2013-08-07
楼主  发表于: 2011-09-05 20:15

 用sd卡烧录的android2.3 空间是如何分配的?

uboot,
kernel
以及android在flash空间中是如何分配的,

已经运行态时的地址空间又是如何?

我的硬件是:tiny6410,ram128M的那种。
我的个性签名
级别: 新手上路
UID: 28128
精华: 0
发帖: 42
金钱: 210 两
威望: 42 点
综合积分: 84 分
注册时间: 2010-09-06
最后登录: 2013-08-07
1楼  发表于: 2011-09-06 19:39
来个人,回答下啊,
没找到相关资料,只有刷机手册。
我的个性签名
级别: 新手上路
UID: 28128
精华: 0
发帖: 42
金钱: 210 两
威望: 42 点
综合积分: 84 分
注册时间: 2010-09-06
最后登录: 2013-08-07
2楼  发表于: 2011-09-16 17:17
<6>s3c6400-uart.0: s3c2410_serial0 at MMIO 0x7f005000 (irq = 16) is a S3C6400/10
<6>s3c6400-uart.1: s3c2410_serial1 at MMIO 0x7f005400 (irq = 20) is a S3C6400/10
<6>s3c6400-uart.2: s3c2410_serial2 at MMIO 0x7f005800 (irq = 24) is a S3C6400/10
<6>s3c6400-uart.3: s3c2410_serial3 at MMIO 0x7f005c00 (irq = 28) is a S3C6400/10
<6>loop: module loaded
<6>pmem: 1 init
<4>S3C NAND Driver, (c) 2008 Samsung Electronics
<4>S3C NAND Driver is using hardware ECC.
<6>NAND device: Manufacturer ID: 0xec, Chip ID: 0xda (Samsung NAND 256MiB 3,3V 8-bit)
<5>Creating 3 MTD partitions on "NAND 256MiB 3,3V 8-bit":
<5>0x000000000000-0x000000080000 : "Bootloader"
<5>0x000000080000-0x000000580000 : "Kernel"
<5>0x000000580000-0x000010000000 : "File System"

<5>UBI: attaching mtd2 to ubi0
<5>UBI: physical eraseblock size:   131072 bytes (128 KiB)
<5>UBI: logical eraseblock size:    129024 bytes
<5>UBI: smallest flash I/O unit:    2048
<5>UBI: sub-page size:              512
<5>UBI: VID header offset:          512 (aligned 512)
<5>UBI: data offset:                2048
<5>UBI: max. sequence number:       199
<5>UBI: attached mtd2 to ubi0
<5>UBI: MTD device name:            "File System"
<5>UBI: MTD device size:            250 MiB
<5>UBI: number of good PEBs:        2002
<5>UBI: number of bad PEBs:         2
<5>UBI: max. allowed volumes:       128
<5>UBI: wear-leveling threshold:    4096
<5>UBI: number of internal volumes: 1
<5>UBI: number of user volumes:     1
<5>UBI: available PEBs:             0
<5>UBI: total number of reserved PEBs: 2002
<5>UBI: number of PEBs reserved for bad PEB handling: 20
<5>UBI: max/mean erase counter: 2/0
<5>UBI: image sequence number:  1329773958
<5>UBI: background thread "ubi_bgt0d" started, PID 540
<6>PPP generic driver version 2.4.2
<6>PPP Deflate Compression module registered
--More--