yaffs2 NAND fs
in [Kernel]
|
From: Peter Paul on 2 Mar 2010 00:10 Hi, I was wondering why the yaffs2 file system has not gone for mainline yet. It's rather popular flash file system in the embedded world, while it is rather easy to patch a kernel to have yaffs2 support [1] it would be even nicer if it was just in mainline. The source of the GPLv2 file system can be found at [2] [1] http://www.yaffs.net/howto-incorporate-yaffs [2] http://www.aleph1.co.uk/cgi-bin/viewcvs.cgi/yaffs2/ -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo(a)vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
From: Arnd Bergmann on 2 Mar 2010 09:00 On Tuesday 02 March 2010, Peter Paul wrote: > I was wondering why the yaffs2 file system has not gone for mainline > yet. It's rather popular flash file system in the embedded world, while > it is rather easy to patch a kernel to have yaffs2 support [1] it would > be even nicer if it was just in mainline. > The source of the GPLv2 file system can be found at [2] > > [1] http://www.yaffs.net/howto-incorporate-yaffs > [2] http://www.aleph1.co.uk/cgi-bin/viewcvs.cgi/yaffs2/ I would guess it's a combination of multiple reasons: 1. It has not been submitted for upstream inclusion, at least not during the last few years. 2. We don't have a staging area like drivers/staging for file systems in the way that we have for drivers 3. There is now ubifs and (soon) logfs upstream, both of which appear to be superior to yaffs in many ways. Arnd -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo(a)vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
From: Maxin John on 3 Mar 2010 10:20 Hi, On Tue, Mar 2, 2010 at 7:21 PM, Arnd Bergmann <arnd(a)arndb.de> wrote: > On Tuesday 02 March 2010, Peter Paul wrote: >> I was wondering why the yaffs2 file system has not gone for mainline >> yet. It's rather popular flash file system in the embedded world, while >> it is rather easy to patch a kernel to have yaffs2 support [1] it would >> be even nicer if it was just in mainline. >> The source of the GPLv2 file system can be found at [2] >> >> [1] http://www.yaffs.net/howto-incorporate-yaffs >> [2] http://www.aleph1.co.uk/cgi-bin/viewcvs.cgi/yaffs2/ > > I would guess it's a combination of multiple reasons: > > 1. It has not been submitted for upstream inclusion, at least not > � during the last few years. > 2. We don't have a staging area like drivers/staging for file systems > � in the way that we have for drivers > 3. There is now ubifs and (soon) logfs upstream, both of which appear > � to be superior to yaffs in many ways. This means there should be no reference to YAFFS2 in the upstream kernel? Because, I have located some defconfigs in upstream kernel where YAFFS2 support is enabled by default. ie: CONFIG_YAFFS_YAFFS2=y CONFIG_YAFFS_AUTO_YAFFS2=y in below listed files: 1. arch/arm/configs/msm_defconfig 2. arch/blackfin/configs/IP0X_defconfig 3. arch/blackfin/configs/SRV1_defconfig 4. arch/blackfin/configs/BlackStamp_defconfig 5. arch/blackfin/configs/BF533-EZKIT_defconfig 6. arch/arm/configs/cam60_defconfig 7. arch/blackfin/configs/BF538-EZKIT_defconfig 8. arch/blackfin/configs/BF533-STAMP_defconfig 9. arch/blackfin/configs/PNAV-10_defconfig 10. arch/blackfin/configs/BF537-STAMP_defconfig 11. arch/blackfin/configs/BF526-EZBRD_defconfig 12. arch/blackfin/configs/BF527-EZKIT_defconfig, Please let me know your opinion on this. Best Regards, Maxin B. John -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo(a)vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
From: Mike Frysinger on 3 Mar 2010 19:30 On Wed, Mar 3, 2010 at 10:09, Maxin John wrote: > On Tue, Mar 2, 2010 at 7:21 PM, Arnd Bergmann wrote: >> On Tuesday 02 March 2010, Peter Paul wrote: >>> I was wondering why the yaffs2 file system has not gone for mainline >>> yet. It's rather popular flash file system in the embedded world, while >>> it is rather easy to patch a kernel to have yaffs2 support [1] it would >>> be even nicer if it was just in mainline. >>> The source of the GPLv2 file system can be found at [2] >>> >>> [1] http://www.yaffs.net/howto-incorporate-yaffs >>> [2] http://www.aleph1.co.uk/cgi-bin/viewcvs.cgi/yaffs2/ >> >> I would guess it's a combination of multiple reasons: >> >> 1. It has not been submitted for upstream inclusion, at least not >> during the last few years. >> 2. We don't have a staging area like drivers/staging for file systems >> in the way that we have for drivers >> 3. There is now ubifs and (soon) logfs upstream, both of which appear >> to be superior to yaffs in many ways. > > This means there should be no reference to YAFFS2 in the upstream > kernel? Because, I have located some defconfigs in upstream kernel > where YAFFS2 support is enabled by default. irrelevant noise -mike -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo(a)vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
From: Arnd Bergmann on 4 Mar 2010 08:50 On Thursday 04 March 2010, Wookey wrote: > So, I guess this is another kick. I'll update the mainline patch I > have (which is essentially just YAFFS2 with all the "#ifdef kernel > nnn" code taken out, and the YAFFS-direct and ecos and WinCE code > removed, to current kernel (which also means updating balloon3 to current > kernel so I can actually test it). I'll put that in git and ask people > to take a look. Detailed suggestions on what extra info is needed or > changes made would be very helpful. > > Unless of course there is already concensus that this is a waste of > time and Peter and I are the only people that want to see it in > mainline? The bar for getting stuff into the kernel has gotten a lot lower these days, at least for the staging part, see http://www.kroah.com/log/linux/linux-staging-update.html The basic requirement would be that you can get a patch that adds a populated drivers/staging/yaffs2 directory actually builds, ideally even mounts existing file sytem images without crashing every time ;-) From there, you can do all the cleanups that are necessary to get it moved to fs/yaffs2, including the stuff you mention above and whatever else comes up (put it into drivers/staging/yaffs2/TODO). Arnd -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo(a)vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
|
Pages: 1 Prev: nfs: use 4*rsize readahead size Next: Don't change direction flags in struct request. |