O:23:"Drupal\node\Entity\Node":25:{s:10:"in_preview";N;s:9:"*values";a:20:{s:3:"vid";a:1:{s:9:"x-default";s:3:"553";}s:8:"langcode";a:1:{s:9:"x-default";s:3:"und";}s:18:"revision_timestamp";a:1:{s:9:"x-default";s:10:"1495718333";}s:12:"revision_uid";a:1:{s:9:"x-default";s:1:"1";}s:12:"revision_log";a:1:{s:9:"x-default";N;}s:3:"nid";a:1:{s:9:"x-default";s:2:"43";}s:4:"type";a:1:{s:9:"x-default";s:4:"page";}s:4:"uuid";a:1:{s:9:"x-default";s:36:"bc3ba208-5871-418a-9a87-bf3a96135fab";}s:17:"isDefaultRevision";a:1:{s:9:"x-default";s:1:"1";}s:6:"status";a:1:{s:9:"x-default";s:1:"1";}s:5:"title";a:1:{s:9:"x-default";s:13:"Yaffs History";}s:3:"uid";a:1:{s:9:"x-default";s:1:"1";}s:7:"created";a:1:{s:9:"x-default";s:10:"1116849117";}s:7:"changed";a:1:{s:9:"x-default";s:10:"1495718333";}s:7:"promote";a:1:{s:9:"x-default";s:1:"0";}s:6:"sticky";a:1:{s:9:"x-default";s:1:"0";}s:29:"revision_translation_affected";a:1:{s:9:"x-default";N;}s:16:"default_langcode";a:1:{s:9:"x-default";s:1:"1";}s:4:"body";a:1:{s:9:"x-default";a:1:{i:0;a:3:{s:5:"value";s:3826:"<p>Yaffs came about because Toby Churchill Ltd (TCL) needed a flash filing system for their devices. They wanted something reliable and one of their fundamental requirements was fast boot time. We looked at adding NAND support to the existing flash filesystems, JFFS and particularly JFFS2, but it became clear that the boot time and ram consumption (a 128MB NAND would use about 4MB RAM in node tables) were a problem, and adding NAND support wasn't trivial either (but has since been done). In the end we decided a different filing system explicitly for NAND was the way to go. The design was greatly simplified by not including compression in the FS - which makes sense as nearly all the large data files TCL used were compressed anyway, and the larger size of NAND devices makes compression less important. A cramfs filesystem can be mounted within Yaffs if you need to compress some of your data.</p><p>The original work was paid for by <a href="http://www.toby-churchill.com/">Toby Churchill Ltd</a>, the project instigators, and <a href="http://www.brightstareng.com/">Brightstar Engineering</a>.</p><p>Here is a collection of notable events and milestones in the history of Yaffs.</p><ul><li>2006.10 Yaffs updated to work properly with Linux 2.6.17+ MTD on 512B and 2K page NAND</li><li>2006.05.08 Checkpointing added - so start-up scanning time enormously reduced</li><li>2004.08.02 Linux kernel 2.6 support checked in.</li><li>2004.02 Yaffs presentation given at FOSDEM on embedded track</li><li><i>2003.06.21</i> Yaffs runs with Linux kernel 2.5.70.</li><li><i>2003.05</i> First two Yaffs/direct licencees.</li><li><i>2003.04</i> Yaffs/direct non-GPL license option created for those who can't use the GPL.</li><li><i>2003.03.07</i> ViewCVS installed to make CVS browsing much easier and help those behind CVS-blocking firewalls get access to the code.</li><li><i>2003.01</i> Yaffs Direct ported to pSOS.</li><li><i>2003.01.21</i> 'Yaffs Direct Interface' checked in - a version of Yaffs designed for integration into lightweight RTOSs and embedded systems.</li><li><i>2003.01.21</i> Yaffs Bootloader example code checked in, so your bootloader can read directly from Yaffs.</li><li><i>2002.11.04</i> <a href="/drupal/yaffs/yaffs2.html">Yaffs2 spec</a> announced for discussion.</li><li><i>2002.11.08</i> WinCE port code checked-in to CVS.</li><li><i>2002.09.23</i> Announced to the world.</li><li><i>2002.09.17</i> Header files relicensed under LGPL to make it easier to add Yaffs support to bootloaders or other non-free software.</li><li><i>2002.09.13</i> Stand-alone system using Yaffs root partition booted.</li><li><i>2002.08</i> WinCE Yaffs port working.</li><li><i>2002.05.20</i> MTD interface tested on hardware emulation and some real hardware.</li><li><i>2002.05.14</i> v0.1 release. MTD interface done and incorporated. This is essentially untested. yaffs.o provides two file systems (one to support internal RAM emulation [called yaffsram] and the other mtd [called yaffs]). Docs improved/updated. mkyaffs filesystem creator written.</li><li><i>2002.04.24</i> Now includes device contexts, (but as there is only one emulation instance this isn't any practical use yet), some bugs fixed and disk full handling. Still some VFS problems apparent in sub-directories. Statfs, attributes still to do, symlinks and hardlinks not yet wired to VFS layer.</li><li><i>2002.04.15</i> kernel module that runs as an fs on 2MB internal emulation. The core filing-system seems to work pretty well. Some problems remain in the VFS layer producing various odd effects. Only one instance of the fs supported</li><li><i>2002.04.03</i> Core fs runs on emulation layer (instead of real NAND), create/read/write/delte/resize/reanem files, create directories, scans media on startup, garbage collection.</li></ul><p>&nbsp;</p>";s:7:"summary";s:64:"<p>A chronology and list of milestones in Yaffs development.</p>";s:6:"format";s:9:"full_html";}}}s:19:"field_document_type";a:1:{s:9:"x-default";a:1:{i:0;a:1:{s:9:"target_id";s:3:"346";}}}}s:9:"*fields";a:0:{}s:19:"*fieldDefinitions";N;s:12:"*languages";N;s:14:"*langcodeKey";s:8:"langcode";s:21:"*defaultLangcodeKey";s:16:"default_langcode";s:17:"*activeLangcode";s:9:"x-default";s:18:"*defaultLangcode";s:3:"und";s:15:"*translations";a:1:{s:9:"x-default";a:1:{s:6:"status";i:1;}}s:24:"*translationInitialize";b:0;s:14:"*newRevision";b:0;s:20:"*isDefaultRevision";s:1:"1";s:13:"*entityKeys";a:4:{s:6:"bundle";s:4:"page";s:2:"id";s:2:"43";s:8:"revision";s:3:"553";s:4:"uuid";s:36:"bc3ba208-5871-418a-9a87-bf3a96135fab";}s:25:"*translatableEntityKeys";a:6:{s:5:"label";a:1:{s:9:"x-default";s:13:"Yaffs History";}s:8:"langcode";a:1:{s:9:"x-default";s:3:"und";}s:6:"status";a:1:{s:9:"x-default";s:1:"1";}s:9:"published";a:1:{s:9:"x-default";s:1:"1";}s:3:"uid";a:1:{s:9:"x-default";s:1:"1";}s:16:"default_langcode";a:1:{s:9:"x-default";s:1:"1";}}s:12:"*validated";b:0;s:21:"*validationRequired";b:0;s:19:"*loadedRevisionId";s:3:"553";s:15:"*entityTypeId";s:4:"node";s:15:"*enforceIsNew";N;s:12:"*typedData";N;s:16:"*cacheContexts";a:0:{}s:12:"*cacheTags";a:0:{}s:14:"*cacheMaxAge";i:-1;s:14:"*_serviceIds";a:0:{}}