[EMAIL PROTECTED] said: > While the topic is raised..., I've hacked up cramfs for linear > addressing to kill the "double buffering" effiect. However as David > mentions the block device support thing is an issue here. What is a > reasonable way to allow a cramfs partition to access the device > directly, like the patch that I wrote, and be picked up in a > reasonable way by the init system? So far, I just cheat. JFFS doesn't need a block device, but uses the minor# to determine which MTD device to use. You could use the same trick. -- dwmw2 - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
- Re: Patch (repost): cramfs memory corru... Christoph Rohland
- Re: Patch (repost): cramfs memory ... Christoph Hellwig
- Re: Patch (repost): cramfs mem... Christoph Rohland
- Re: Patch (repost): cramfs memory ... Alan Cox
- Re: Patch (repost): cramfs mem... Christoph Rohland
- Re: Patch (repost): cramfs memory corruptio... David L. Parsley
- Re: Patch (repost): cramfs memory corru... Linus Torvalds
- Re: Patch (repost): cramfs memory corruption fix Linus Torvalds
- Re: Patch (repost): cramfs memory corruption fix David Woodhouse
- Re: Patch (repost): cramfs memory corruption fi... Shane Nay
- [PATCH] one-liner fix for bforget() honoring BH... David Woodhouse
- [PATCH] one-liner fix for bforget() honoring BH_Pro... David L. Parsley
- Re: [PATCH] one-liner fix for bforget() honorin... Linus Torvalds