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
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
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 loo
[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
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
>large
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
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
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_
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
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/lk
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.
>
D
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 (
f
12 matches
Mail list logo