Hi YAFFSers
I have applied some of Frank's patches. I think I have applied all of the
patches that do functional things (the kill_sb and sendfile patches). The
ones that clean up warnings etc have not been applied yet. Things seem to get
away from you at Christmas time (remember in NZ we're a day ahead of most
people :-), but I will still get around to the rest of this fixing as I can.
I have also done some directory restructuring. From the new README:
Where do you want to go today?
------------------------------
direct This is the userspace/RTOS variant of YAFFS. This is used for
yaffs
core development and for embedding YAFFS in products that don't use
Linux or WinCE
linux-module This allows you to build YAFFS as a free-standing Linux kernel
module. By "free standing", I mean that this build happens
outside the kernel tree. Generally you'd use this for testing.
linux-kernel This allows you to hook YAFFS into the kernel tree, to build
YAFFS within the kernel tree.
utils These are some utilities for Linux.
wince Windows CE support. Horribly dated. Contact Aleph One is you're
considering YAFFS for a WinCE project.
mtdemul An mtd NAND emulation driver for testing YAFFS under Linux.
Documentation Some YAFFS documents. Also visit www.aleph1.co.uk.
The idea behind this is that you choose the working directory dependent on
what you're trying to achieve. Everything is symlinked from that directory to
the common code.
Linux folks: for now the linux-module gives you what you had. linux-kernel is
still work in progress, (I still need to do the patchin script), but the idea
is that yaffs will get symlinked into the kernel tree. symlinks keep
everything very modular and allow an extra level of plug and play for
patching etc.
Non-linux folk: Nothing has really changed with the new directory structure.
(text/plain)