Re: What flash disks are supported?
Catalin BOIE wrote: >Hi, guys! > >Please, can you tell me your (in)success stories about some flash disks? >Thanks! > A MTD flash device database is now available at: http://www.embeddedlinuxworks.com/db.html - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: What flash disks are supported?
Catalin BOIE wrote: Hi, guys! Please, can you tell me your (in)success stories about some flash disks? Thanks! A MTD flash device database is now available at: http://www.embeddedlinuxworks.com/db.html - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: about linux mips ext2fs
Barry Wu wrote: > >I want port linux to our mipsel system. The kernel >can work and system stop at mount root file system. >I download root file system for mipsel from MIPS >company. Because our system have no ethernet >interface, >I have to copy root file system directly to our hard >disk. I put hard disk under intel linux, and using >fdisk and make ex2fs on it. Then I copy root file >system to hard disk. After finished, I place this hard >disk under our mipsel environment. I do not know if >it can work under this environment, the kernel can >mount root file system? If someone knows, please help >me. > I have MIPSEB, and there is no problems with ext2. As i know, it doesn't matter where you created your rootfs and put it on disk. But you have to take the kernel for a MIPS from oss.sgi.com, by the way. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: about linux mips ext2fs
Barry Wu wrote: I want port linux to our mipsel system. The kernel can work and system stop at mount root file system. I download root file system for mipsel from MIPS company. Because our system have no ethernet interface, I have to copy root file system directly to our hard disk. I put hard disk under intel linux, and using fdisk and make ex2fs on it. Then I copy root file system to hard disk. After finished, I place this hard disk under our mipsel environment. I do not know if it can work under this environment, the kernel can mount root file system? If someone knows, please help me. I have MIPSEB, and there is no problems with ext2. As i know, it doesn't matter where you created your rootfs and put it on disk. But you have to take the kernel for a MIPS from oss.sgi.com, by the way. - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: about mips linux root file system
Qingbo Wu wrote: > >I think if I can use ramdisk using serail port. I do not know >how to combine kernel image with ramdisk root file image. >And where can I get small size root file image for mipsel? >If someone knows, please help me. >Thanks in advance! > There is a way which i use. Take a look at the arch/mips/ld.script linker commandfile. As you can see, you need to create an ELF binary with the ".initrd" section, and link this binary into your kernel. You must put your initial ramdisk into this section. There are ext2fs, romfs, gzipped ext2fs and minixfs ramdisks currently supported. Here is an example with gzipped ramdisk for MIPS linux-2.4.x : NOTE: the 'disk' directory is assumed your root filesystem directory, which you going to be using on your mips 1) First of all, you need the properly MIPS linux kernel: cvs -d :pserver:[EMAIL PROTECTED]:/cvs -z9 co linux 2) Add new target to your specific Makefile (i mean arch/mips//Makefile): ... obj-$(CONFIG_BLK_DEV_INITRD)+= ramdisk.o ... ramdisk.c:ramdisk.bin $(CC) $(CFLAGS) -c -o $@ $< $(OBJCOPY) --add-section=.initrd=ramdisk.bin $@ ... 3) Create the root filesystem gzipped image and copy it to your specific location: # dd if=/dev/zero of=ramdisk bs=1k count=4096 # mke2fs -Fvm0 ramdisk 4096 # mount -o loop ramdisk /tmp/ram # cp -a disk/* /tmp/ram/ # umount /tmp/ram/ # dd if=ramdisk bs=1k count=4096 | gzip -v9 > ramdisk.bin # cp ramdisk.bin linux/arch/mips// 4) Compile the kernel # cd linux # make ... I think that's all Regards. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: about mips linux root file system
Qingbo Wu wrote: I think if I can use ramdisk using serail port. I do not know how to combine kernel image with ramdisk root file image. And where can I get small size root file image for mipsel? If someone knows, please help me. Thanks in advance! There is a way which i use. Take a look at the arch/mips/ld.script linker commandfile. As you can see, you need to create an ELF binary with the .initrd section, and link this binary into your kernel. You must put your initial ramdisk into this section. There are ext2fs, romfs, gzipped ext2fs and minixfs ramdisks currently supported. Here is an example with gzipped ramdisk for MIPS linux-2.4.x : NOTE: the 'disk' directory is assumed your root filesystem directory, which you going to be using on your mips 1) First of all, you need the properly MIPS linux kernel: cvs -d :pserver:[EMAIL PROTECTED]:/cvs -z9 co linux 2) Add new target to your specific Makefile (i mean arch/mips//Makefile): ... obj-$(CONFIG_BLK_DEV_INITRD)+= ramdisk.o ... ramdisk.c:ramdisk.bin $(CC) $(CFLAGS) -c -o $@ $ $(OBJCOPY) --add-section=.initrd=ramdisk.bin $@ ... 3) Create the root filesystem gzipped image and copy it to your specific location: # dd if=/dev/zero of=ramdisk bs=1k count=4096 # mke2fs -Fvm0 ramdisk 4096 # mount -o loop ramdisk /tmp/ram # cp -a disk/* /tmp/ram/ # umount /tmp/ram/ # dd if=ramdisk bs=1k count=4096 | gzip -v9 ramdisk.bin # cp ramdisk.bin linux/arch/mips// 4) Compile the kernel # cd linux # make ... I think that's all Regards. - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: how to patch driver into kernel
[EMAIL PROTECTED] wrote: >hi: > I write a serial driver for linux , and have a personal test . I went >to patch this driver into kernel >but I don't know how to contact serial.c author .. >can any one help me ? > rich.liu > For future patches please read the Documentation/SubmittingPatches and Documentation/SubmittingDrivers files. Regards. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Using cramfs as root filesystem on diskless machine
David L. Parsley wrote >>... >>RAMDISK driver initialized: 16 RAM disks of 4096K size 4096 blocksize >> > ^ >You also need to give the kernel 'ramdisk_size='. I've used >larger cramfs initrd's with no problem, but the kernel has to make >larger ramdisks. By editing rd.c, you can make this stuff default. > >regards, > David > My cramfs ramdisk size is less then 4096, it is only 2304Kb. Matthias Kilian wrote me in the private letter: > The cramfs does uncompression on the fly, i.e. on each file access. > This means that the ramdisk in your example actually uses 2304 k RAM. And besides, i have been tried this option already. But, thank you anyway, now i know that big cramfs initrd`s works. Possibly, some symlinks are broken, or some libraries are missed, on my rootfs... But it is very strange, that ext2fs ramdisk image works with the same rootfs on it. I'll try to investigate it by myself. Regards. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Using cramfs as root filesystem on diskless machine
David L. Parsley wrote: >Mathias Killian wrote a patch to allow cramfs initrd's, see: >http://www.cs.helsinki.fi/linux/linux-kernel/2001-01/1064.html > Thank you. I applied this patch, and recompiled my kernel. All works fine, if the size of root filesystem less than 4096Kb. But when i create an image of root filesystem which size is bigger than 4096Mb, the kernel said: ... RAMDISK driver initialized: 16 RAM disks of 4096K size 4096 blocksize ... RAMDISK: cramfs filesystem found at block 0 RAMDISK: Loading 2300 blocks [1 disk] into ram disk... done. ... Freeing unused kernel memory: 116k freed Algorithmics/MIPS FPU Emulator v1.4 Error -3 while decompressing! 804172a4(-166740)->803da000(4096) bash# As you can see, the size of image is only 2300kb. The kernel command line is: root=/dev/ram init=/bin/bash ramdisk_blocksize=4096 When i tried to mount this image on a running kernel it is all OK. # mount -o loop -t cramfs cramfsdisk.bin /mnt/ramdisk # chroot /mnt/ramdisk /bin/bash I already asked Matthias, but he said that he didn't try cramfs for ram disks larger than 4k. Did anybody try it? Does anybody work on cramfs now? - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Using cramfs as root filesystem on diskless machine
David L. Parsley wrote: Mathias Killian wrote a patch to allow cramfs initrd's, see: http://www.cs.helsinki.fi/linux/linux-kernel/2001-01/1064.html Thank you. I applied this patch, and recompiled my kernel. All works fine, if the size of root filesystem less than 4096Kb. But when i create an image of root filesystem which size is bigger than 4096Mb, the kernel said: ... RAMDISK driver initialized: 16 RAM disks of 4096K size 4096 blocksize ... RAMDISK: cramfs filesystem found at block 0 RAMDISK: Loading 2300 blocks [1 disk] into ram disk... done. ... Freeing unused kernel memory: 116k freed Algorithmics/MIPS FPU Emulator v1.4 Error -3 while decompressing! 804172a4(-166740)-803da000(4096) bash# As you can see, the size of image is only 2300kb. The kernel command line is: root=/dev/ram init=/bin/bash ramdisk_blocksize=4096 When i tried to mount this image on a running kernel it is all OK. # mount -o loop -t cramfs cramfsdisk.bin /mnt/ramdisk # chroot /mnt/ramdisk /bin/bash I already asked Matthias, but he said that he didn't try cramfs for ram disks larger than 4k. Did anybody try it? Does anybody work on cramfs now? - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Using cramfs as root filesystem on diskless machine
David L. Parsley wrote ... RAMDISK driver initialized: 16 RAM disks of 4096K size 4096 blocksize ^ You also need to give the kernel 'ramdisk_size='. I've used larger cramfs initrd's with no problem, but the kernel has to make larger ramdisks. By editing rd.c, you can make this stuff default. regards, David My cramfs ramdisk size is less then 4096, it is only 2304Kb. Matthias Kilian wrote me in the private letter: The cramfs does uncompression on the fly, i.e. on each file access. This means that the ramdisk in your example actually uses 2304 k RAM. And besides, i have been tried this option already. But, thank you anyway, now i know that big cramfs initrd`s works. Possibly, some symlinks are broken, or some libraries are missed, on my rootfs... But it is very strange, that ext2fs ramdisk image works with the same rootfs on it. I'll try to investigate it by myself. Regards. - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: how to patch driver into kernel
[EMAIL PROTECTED] wrote: hi: I write a serial driver for linux , and have a personal test . I went to patch this driver into kernel but I don't know how to contact serial.c author .. can any one help me ? rich.liu For future patches please read the Documentation/SubmittingPatches and Documentation/SubmittingDrivers files. Regards. - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Using cramfs as root filesystem on diskless machine
David Woodhouse wrote: >It's not polite to respond to private messages in public fora. > >On Fri, 15 Jun 2001, Alexandr Andreev wrote: > >>Bootloader only jumps to the kernel entry point. The initrd image is >>compiled inside the kernel. >> > >So it's in a ROM or flash chip? Why copy it into memory then? We have >support for ROM and flash chips. > No any flash, disk, floppy... only RAM, image is inside kernel. #ls -s vmlinux 4852 vmlinux #objdump --headers vmlinux .data .text .bss .initrd <- Here is the image. ... - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Using cramfs as root filesystem on diskless machine
Hi, David. David Woodhouse wrote: >Where does the bootloader get the initrd from? > Bootloader only jumps to the kernel entry point. The initrd image is compiled inside the kernel. ( special section in the ELF kernel binary ) .config: ... CONFIG_BLK_DEV_RAM=y CONFIG_BLK_DEV_RAM_SIZE=8192 CONFIG_BLK_DEV_INITRD=y ... If 'root=/dev/ram' option is set in command line, the root file system will bi in RAM. When the linux kernel is booting, it tries to identify_ramdisk_image() ( at drivers/block/rd.c ). So it can only understand ext2, minix, romfs, and gzipped images. But what about cramfs? How can i use a cramfs image to mount it as my root file system? Is any patches to the rd.c requiried? - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Using cramfs as root filesystem on diskless machine
Hi, list. My MIPS machine has no any disks or flopies. So i obliged to use a RAM disk with a file system on it, which is mounted as root. I use gzipped initrd image, which is linked to the special section in the kernel during compilation. Now, the RAM disk size is really big, so i decide to use cramfs instead of ext2. In scripts/cramfs/ I found an utility that creates cramfs file system image. But i read in rd.c, that RAM disk driver doesn't support the cramfs. After i create an image, how can i mount it as root file system? Where i must put it? Which kernel command line options i must use? Please answer, or point me to any documentation or mailing list. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Using cramfs as root filesystem on diskless machine
Hi, list. My MIPS machine has no any disks or flopies. So i obliged to use a RAM disk with a file system on it, which is mounted as root. I use gzipped initrd image, which is linked to the special section in the kernel during compilation. Now, the RAM disk size is really big, so i decide to use cramfs instead of ext2. In scripts/cramfs/ I found an utility that creates cramfs file system image. But i read in rd.c, that RAM disk driver doesn't support the cramfs. After i create an image, how can i mount it as root file system? Where i must put it? Which kernel command line options i must use? Please answer, or point me to any documentation or mailing list. - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Using cramfs as root filesystem on diskless machine
Hi, David. David Woodhouse wrote: Where does the bootloader get the initrd from? Bootloader only jumps to the kernel entry point. The initrd image is compiled inside the kernel. ( special section in the ELF kernel binary ) .config: ... CONFIG_BLK_DEV_RAM=y CONFIG_BLK_DEV_RAM_SIZE=8192 CONFIG_BLK_DEV_INITRD=y ... If 'root=/dev/ram' option is set in command line, the root file system will bi in RAM. When the linux kernel is booting, it tries to identify_ramdisk_image() ( at drivers/block/rd.c ). So it can only understand ext2, minix, romfs, and gzipped images. But what about cramfs? How can i use a cramfs image to mount it as my root file system? Is any patches to the rd.c requiried? - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Using cramfs as root filesystem on diskless machine
David Woodhouse wrote: It's not polite to respond to private messages in public fora. On Fri, 15 Jun 2001, Alexandr Andreev wrote: Bootloader only jumps to the kernel entry point. The initrd image is compiled inside the kernel. So it's in a ROM or flash chip? Why copy it into memory then? We have support for ROM and flash chips. No any flash, disk, floppy... only RAM, image is inside kernel. #ls -s vmlinux 4852 vmlinux #objdump --headers vmlinux .data .text .bss .initrd - Here is the image. ... - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Does anybody know, where is the MIPS linux mailing list ?
Hi all! I need to ask some questions about linux-2.4.3 for MIPS. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Does anybody know, where is the MIPS linux mailing list ?
Hi all! I need to ask some questions about linux-2.4.3 for MIPS. - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Disabling interrupts before block device request call
Jens Axboe wrote > >Even with dropping io_request_lock, it's not recommended to sleep inside >the request_fn. WIth plugging, you are basically preventing the other >plugged queues from being run until you return. > >You could use a timer or similar to call you on a specified timeout >instead. > Does it mean, that if i need timer interrupts in my block device driver, i need to do sti() instead of unlock io_request_lock? Is there any common rule for device drivers in such case? - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Disabling interrupts before block device request call
Jens Axboe wrote Even with dropping io_request_lock, it's not recommended to sleep inside the request_fn. WIth plugging, you are basically preventing the other plugged queues from being run until you return. You could use a timer or similar to call you on a specified timeout instead. Does it mean, that if i need timer interrupts in my block device driver, i need to do sti() instead of unlock io_request_lock? Is there any common rule for device drivers in such case? - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Disabling interrupts before block device request call
Hi, list In ll_rw_block.c, before calling block device specific request function ( i mean do_hd_request, do_ftl_request, ... ) the io_request_lock is locking, and all interrupts are disabling. I know, that request handler routine have to be atomic, but when we read data from a flash device ( for example ) we use a timeouts. Where do we have to enable timer interrupts, or should we disable all interrupts? - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Disabling interrupts before block device request call
Hi, list In ll_rw_block.c, before calling block device specific request function ( i mean do_hd_request, do_ftl_request, ... ) the io_request_lock is locking, and all interrupts are disabling. I know, that request handler routine have to be atomic, but when we read data from a flash device ( for example ) we use a timeouts. Where do we have to enable timer interrupts, or should we disable all interrupts? - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
