分类：
2011-03-29 09:19:05
| $ make s3c2410_defconfig |
| $ cp arch/arm/configs/s3c2410_defconfig ./.config |
| $ make menuconfig |
| $ make xconfig |
| $ make zImage |
| 目的都是生成一个.config文件,这三个命令中，make xconfig的界面最为友好，如果你可以使用Xwindow，你就用这个好了，这个比较方便，也好设置。如果你不能使用Xwindow，那么就使用 make menuconfig好了。界面虽然比上面一个差点，总比make config的要好多了。 |
| $ tar jxvf linux-2.6.26.tar.bz2 $ cd linux-2.6.26 |
| #ARCH ?= $(SUBARCH) #CROSS_COMPILE ?= ARCH ?= arm CROSS_COMPILE ?= $HOME/toolchain/crosstool/gcc-4.1.0-glibc-2.3.2/arm-linux-gnu/bin/arm-linux-gnu- |
| $ make s3c2410_defconfig |
| config DEVFS_FS bool "/dev file system support (OBSOLETE)" depends on EXPERIMENTAL help This is support for devfs, a virtual file system (like /proc) which provides the file system interface to device drivers, normally found in /dev. Devfs does not depend on major and minor number allocations. Device drivers register entries in /dev which then appear automatically, which means that the system administrator does not have to create character and block special device files in the /dev directory using the mknod command (or MAKEDEV script) anymore. This is work in progress. If you want to use this, you *must* read the material in , especially the file README there. Note that devfs no longer manages /dev/pts! If you are using UNIX98 ptys, you will also need to mount the /dev/pts filesystem (devpts). Note that devfs has been obsoleted by udev, <>. It has been stripped down to a bare minimum and is only provided for legacy installations that use its naming scheme which is unfortunately different from the names normal Linux installations use. If unsure, say N. config DEVFS_MOUNT bool "Automatically mount at boot" depends on DEVFS_FS help This option appears if you have CONFIG_DEVFS_FS enabled. Setting this to 'Y' will make the kernel automatically mount devfs onto /dev when the system is booted, before the init thread is started. You can override this with the "devfs=nomount" boot option. If unsure, say N. config DEVFS_DEBUG bool "Debug devfs" depends on DEVFS_FS help If you say Y here, then the /dev file system code will generate debugging messages. See the file for more details. If unsure, say N. |
| /*s3c24xx_init_clocks(16934400);*/ s3c24xx_init_clocks(12000000); |
| /* fix mtd partition to be same with bootloader */ /* a flash all in 64M bit size have been devided into 4 partition: */ /* 1. boot : offset is 0 and size is 192k */ /* 2. kernel : offset is 0x30000 and size is 1856k */ /* 3. rootfs : offset is 0x200000 and size is 30M */ /* 4. ext-fs1 : offset is 0x2000000 and size is 32M */ static struct mtd_partition smdk_default_nand_part[] = { [0] = { .name = "boot", /* default is "Boot Agent", by qspy */ .size = SZ_64K*3, /* default is SZ_16K, qspy fix it to 192K*/ .offset = 0, }, [1] = { .name = "kernel", /* default is "S3C2410 flash partition 1", by qspy */ .offset = SZ_64K*3,/* default is 0, by qspy */ .size = SZ_64K*29,/* default is SZ_2M, qspy fix it to 1856K*/ }, [2] = { .name = "rootfs",/* default is "S3C2410 flash partition 2", by qspy */ .offset = SZ_2M,/* default is SZ_4M, by qspy */ .size = SZ_1M*30,/* default is SZ_4M, qspy fix it to 30M*/ }, [3] = { .name = "ext-fs1",/* default is "S3C2410 flash partition 2", by qspy */ .offset = SZ_32M,/* default is SZ_8M, by qspy */ .size = SZ_32M,/* default is SZ_2M, qspy fix it to 30M*/ } /*, [4] = { .name = "S3C2410 flash partition 4", .offset = SZ_1M * 10, .size = SZ_4M, }, [5] = { .name = "S3C2410 flash partition 5", .offset = SZ_1M * 14, .size = SZ_1M * 10, }, [6] = { .name = "S3C2410 flash partition 6", .offset = SZ_1M * 24, .size = SZ_1M * 24, }, [7] = { .name = "S3C2410 flash partition 7", .offset = SZ_1M * 48, .size = SZ_16M, } */ }; |
| /*chip->ecc.mode = NAND_ECC_SOFT; */ chip->ecc.mode = NAND_ECC_NONE; |
| $ make xconfig |
| |---Boot options | |---Default kernel command string: [root=/dev/mtdblock2 rootfstype=cramfs init=/linuxrc console=ttySAC1,115200 devfs=mount mem=64] |
| |---File systems | |---Pseudo filesystems | | |---/dev file system support | | | |---Automatically mount at boot | | | |---Debug devfs |
| |---System Type | |---S3C2410 Machines | | |---SMDK2410/A9M2410 |
| Nand flash status = c0 Set boot params = root=/dev/mtdblock2 init=/linuxrc load_ramdisk=0 console=ttySAC1,115200 mem=65536K devfs=mount display=shp480 Load Kernel... 8???腳c?洤''D?G#溰 ?`納 { 悃\'榌 |
| IP route cache hash table entries: 1024 (order: 0, 4096 bytes) TCP established hash table entries: 2048 (order: 2, 16384 bytes) TCP bind hash table entries: 2048 (order: 1, 8192 bytes) TCP: Hash tables configured (established 2048 bind 2048) TCP reno registered NET: Registered protocol family 1 NetWinder Floating Point Emulator V0.97 (double precision) msgmni has been set to 120 io scheduler noop registered io scheduler anticipatory registered (default) io scheduler deadline registered io scheduler cfq registered Console: switching to colour frame buffer device 30x40 fb0: s3c2410fb frame buffer device s3c2440-uart.0: s3c2410_serial0 at MMIO 0x50000000 (irq = 70) is a S3C2440 s3c2440-uart.1: s3c2410_serial1 at MMIO 0x50004000 (irq = 73) is a S3C2440 s3c2440-uart.2: s3c2410_serial2 at MMIO 0x50008000 (irq = 76) is a S3C2440 brd: module loaded usbcore: registered new interface driver ub dm9000 Ethernet Driver, V1.30 Linux video capture interface: v2.00 NFTL driver: nftlcore.c $Revision: 1.98 $, nftlmount.c $Revision: 1.41 $ S3C24XX NAND Driver, (c) 2004 Simtec Electronics s3c2440-nand s3c2440-nand: Tacls=1, 10ns Twrph0=4 40ns, Twrph1=1 10ns NAND device: Manufacturer ID: 0xec, Chip ID: 0x76 (Samsung NAND 64MiB 3,3V 8-bit) s3c2410_nand_update_chip: chip c3d7d4bc: 9 Scanning device for bad blocks Bad eraseblock 357 at 0x00594000 Bad eraseblock 3335 at 0x0341c000 Bad eraseblock 3995 at 0x03e6c000 Creating 4 MTD partitions on "NAND 64MiB 3,3V 8-bit": 0x00000000-0x00030000 : "boot" 0x00030000-0x00200000 : "kernel" 0x00200000-0x02000000 : "rootfs" 0x02000000-0x04000000 : "ext-fs1" usbmon: debugfs is not available s3c2410-ohci s3c2410-ohci: S3C24XX OHCI s3c2410-ohci s3c2410-ohci: new USB bus registered, assigned bus number 1 s3c2410-ohci s3c2410-ohci: irq 42, io mem 0x49000000 usb usb1: configuration #1 chosen from 1 choice hub 1-0:1.0: USB hub found hub 1-0:1.0: 2 ports detected Initializing USB Mass Storage driver... usbcore: registered new interface driver usb-storage USB Mass Storage support registered. mice: PS/2 mouse device common for all mice i2c /dev entries driver s3c2440-i2c s3c2440-i2c: slave address 0x10 s3c2440-i2c s3c2440-i2c: bus frequency set to 390 KHz s3c2440-i2c s3c2440-i2c: i2c-0: S3C I2C adapter S3C2410 Watchdog Timer, (c) 2004 Simtec Electronics s3c2410-wdt s3c2410-wdt: watchdog inactive, reset disabled, irq enabled Registered led device: led4 Registered led device: led5 Registered led device: led6 Registered led device: led7 TCP cubic registered RPC: Registered udp transport module. RPC: Registered tcp transport module. end_request: I/O error, dev mtdblock2, sector 2 EXT2-fs: unable to read superblock end_request: I/O error, dev mtdblock2, sector 0 Buffer I/O error on device mtdblock2, logical block 0 end_request: I/O error, dev mtdblock2, sector 0 Buffer I/O error on device mtdblock2, logical block 0 end_request: I/O error, dev mtdblock2, sector 8 Buffer I/O error on device mtdblock2, logical block 1 end_request: I/O error, dev mtdblock2, sector 8 Buffer I/O error on device mtdblock2, logical block 1 end_request: I/O error, dev mtdblock2, sector 16 Buffer I/O error on device mtdblock2, logical block 2 end_request: I/O error, dev mtdblock2, sector 16 Buffer I/O error on device mtdblock2, logical block 2 end_request: I/O error, dev mtdblock2, sector 24 Buffer I/O error on device mtdblock2, logical block 3 end_request: I/O error, dev mtdblock2, sector 24 Buffer I/O error on device mtdblock2, logical block 3 end_request: I/O error, dev mtdblock2, sector 0 FAT: unable to read boot sector VFS: Cannot open root device "mtdblock2" or unknown-block(31,2) Please append a correct "root=" boot option; here are the available partitions: 1f00 192 mtdblock0 (driver?) 1f01 1856 mtdblock1 (driver?) 1f02 30720 mtdblock2 (driver?) 1f03 32768 mtdblock3 (driver?) Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(31,2) |
| Linux video capture interface: v2.00 NFTL driver: nftlcore.c $Revision: 1.98 $, nftlmount.c $Revision: 1.41 $ S3C24XX NAND Driver, (c) 2004 Simtec Electronics s3c2440-nand s3c2440-nand: Tacls=1, 10ns Twrph0=4 40ns, Twrph1=1 10ns NAND device: Manufacturer ID: 0xec, Chip ID: 0x76 (Samsung NAND 64MiB 3,3V 8-bit) s3c2410_nand_update_chip: chip c3d704bc: 9 NAND_ECC_NONE selected by board driver. This is not recommended !! Scanning device for bad blocks Bad eraseblock 357 at 0x00594000 Bad eraseblock 3335 at 0x0341c000 Bad eraseblock 3995 at 0x03e6c000 Creating 4 MTD partitions on "NAND 64MiB 3,3V 8-bit": 0x00000000-0x00030000 : "boot" 0x00030000-0x00200000 : "kernel" 0x00200000-0x02000000 : "rootfs" 0x02000000-0x04000000 : "ext-fs1" usbmon: debugfs is not available s3c2410-ohci s3c2410-ohci: S3C24XX OHCI s3c2410-ohci s3c2410-ohci: new USB bus registered, assigned bus number 1 s3c2410-ohci s3c2410-ohci: irq 42, io mem 0x49000000 usb usb1: configuration #1 chosen from 1 choice hub 1-0:1.0: USB hub found hub 1-0:1.0: 2 ports detected Initializing USB Mass Storage driver... usbcore: registered new interface driver usb-storage USB Mass Storage support registered. mice: PS/2 mouse device common for all mice i2c /dev entries driver s3c2440-i2c s3c2440-i2c: slave address 0x10 s3c2440-i2c s3c2440-i2c: bus frequency set to 390 KHz s3c2440-i2c s3c2440-i2c: i2c-0: S3C I2C adapter S3C2410 Watchdog Timer, (c) 2004 Simtec Electronics s3c2410-wdt s3c2410-wdt: watchdog inactive, reset disabled, irq enabled Registered led device: led4 Registered led device: led5 Registered led device: led6 Registered led device: led7 TCP cubic registered RPC: Registered udp transport module. RPC: Registered tcp transport module. VFS: Mounted root (cramfs filesystem) readonly. Freeing init memory: 124K cramfs: bad compressed blocksize 989432407 cramfs: bad compressed blocksize 4274059297 Failed to execute /linuxrc. Attempting defaults... Kernel panic - not syncing: No init found. Try passing init= option to kernel. |
