NetCube-Systems-Austria/kumquat-buildroot
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
4fdf2d642b
kumquat-buildroot/fs/jffs2/Config.in

113 lines
3.3 KiB
Plaintext
Raw Normal View History

menuconfig -> config
2005-02-10 01:59:22 +01:00
config BR2_TARGET_ROOTFS_JFFS2
touchup target menu display
2005-09-09 02:12:13 +02:00
bool "jffs2 root filesystem"
Fix it so we once again build the target root_fs
2004-10-09 06:34:21 +02:00
help
Build a jffs2 root filesystem
target/jffs2: Put all sub options in a BR2_TARGET_ROOTFS_JFFS2 conditional And get rid of all the individual 'depends on B2_TARGET_ROOTFS_JFFS2'
2009-04-07 21:22:43 +02:00
if BR2_TARGET_ROOTFS_JFFS2
Correct JFFS2 Erase Size for AT45 dataflash
2007-07-14 09:26:41 +02:00
choice
target/jffs2: s/Memory Type/Flash Type/
2009-04-07 21:22:46 +02:00
prompt "Flash Type"
Update JFFS2 page/erase size correctly
2007-10-18 00:01:58 +02:00
default BR2_TARGET_ROOTFS_JFFS2_FLASH_128
- Additional JFFS2 options to support Dataflash (Ulf Samuelsson) - cleanup a bit while at it
2007-01-25 00:18:08 +01:00
Update JFFS2 page/erase size correctly
2007-10-18 00:01:58 +02:00
config BR2_TARGET_ROOTFS_JFFS2_DATAFLASH_1056
bool "AT45 dataflash with 1056 byte pagesize"
select BR2_TARGET_ROOTFS_JFFS2_NOCLEANMARKER
Correct JFFS2 Erase Size for AT45 dataflash
2007-07-14 09:26:41 +02:00
Update JFFS2 page/erase size correctly
2007-10-18 00:01:58 +02:00
config BR2_TARGET_ROOTFS_JFFS2_DATAFLASH_528
bool "AT45 dataflash with 528 byte pagesize"
Correct JFFS2 Erase Size for AT45 dataflash
2007-07-14 09:26:41 +02:00
select BR2_TARGET_ROOTFS_JFFS2_NOCLEANMARKER
fs/jffs2: Fix mkfs.jffs2 --pagesize parameter usage Fixes #8186 Mkfs.jffs2 accepts a --pagesize parameter, which allows specifying the size of the virtual memory page size of the target machine, where the image will be used. (This is the value of the PAGE_SIZE macro in Linux.) In most cases the parameter doesn't need to be set as the default value of 4 kB is usually correct. The parameter was used incorrectly in Buildroot -- it was set to the page size of flash memory chip -- this commit fixes this problem. Now the --pagesize parameter is not used at all (unless the user explicitly chooses to use a custom value during configuration). All existing defconfigs were corrected to match the new configuration variable names. [Peter: reword, add Config.in.legacy handling] Signed-off-by: Michał Leśniewski <mlesniew@gmail.com> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2015-05-19 20:26:30 +02:00
config BR2_TARGET_ROOTFS_JFFS2_NANDFLASH_16K
bool "NAND flash with 16 kB erasesize"
target/jffs2: add support for nand flash with 512B page / 16 kB erasesize Closes #663 Signed-off-by: Kelvin Cheung <keguang.zhang@gmail.com> Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
2009-11-22 21:08:37 +01:00
select BR2_TARGET_ROOTFS_JFFS2_NOCLEANMARKER
fs/jffs2: Fix mkfs.jffs2 --pagesize parameter usage Fixes #8186 Mkfs.jffs2 accepts a --pagesize parameter, which allows specifying the size of the virtual memory page size of the target machine, where the image will be used. (This is the value of the PAGE_SIZE macro in Linux.) In most cases the parameter doesn't need to be set as the default value of 4 kB is usually correct. The parameter was used incorrectly in Buildroot -- it was set to the page size of flash memory chip -- this commit fixes this problem. Now the --pagesize parameter is not used at all (unless the user explicitly chooses to use a custom value during configuration). All existing defconfigs were corrected to match the new configuration variable names. [Peter: reword, add Config.in.legacy handling] Signed-off-by: Michał Leśniewski <mlesniew@gmail.com> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2015-05-19 20:26:30 +02:00
config BR2_TARGET_ROOTFS_JFFS2_NANDFLASH_128K
bool "NAND flash with 128 kB erasesize"
Support large sector NAND flash for JFFS2
2009-01-12 01:43:22 +01:00
select BR2_TARGET_ROOTFS_JFFS2_NOCLEANMARKER
Update JFFS2 page/erase size correctly
2007-10-18 00:01:58 +02:00
config BR2_TARGET_ROOTFS_JFFS2_FLASH_128
fs/jffs2: Fix mkfs.jffs2 --pagesize parameter usage Fixes #8186 Mkfs.jffs2 accepts a --pagesize parameter, which allows specifying the size of the virtual memory page size of the target machine, where the image will be used. (This is the value of the PAGE_SIZE macro in Linux.) In most cases the parameter doesn't need to be set as the default value of 4 kB is usually correct. The parameter was used incorrectly in Buildroot -- it was set to the page size of flash memory chip -- this commit fixes this problem. Now the --pagesize parameter is not used at all (unless the user explicitly chooses to use a custom value during configuration). All existing defconfigs were corrected to match the new configuration variable names. [Peter: reword, add Config.in.legacy handling] Signed-off-by: Michał Leśniewski <mlesniew@gmail.com> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2015-05-19 20:26:30 +02:00
bool "Parallel flash with 128 kB erase size"
Correct JFFS2 Erase Size for AT45 dataflash
2007-07-14 09:26:41 +02:00
Update JFFS2 page/erase size correctly
2007-10-18 00:01:58 +02:00
config BR2_TARGET_ROOTFS_JFFS2_FLASH_64
fs/jffs2: Fix mkfs.jffs2 --pagesize parameter usage Fixes #8186 Mkfs.jffs2 accepts a --pagesize parameter, which allows specifying the size of the virtual memory page size of the target machine, where the image will be used. (This is the value of the PAGE_SIZE macro in Linux.) In most cases the parameter doesn't need to be set as the default value of 4 kB is usually correct. The parameter was used incorrectly in Buildroot -- it was set to the page size of flash memory chip -- this commit fixes this problem. Now the --pagesize parameter is not used at all (unless the user explicitly chooses to use a custom value during configuration). All existing defconfigs were corrected to match the new configuration variable names. [Peter: reword, add Config.in.legacy handling] Signed-off-by: Michał Leśniewski <mlesniew@gmail.com> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2015-05-19 20:26:30 +02:00
bool "Parallel flash with 64 kB erase size"
Correct JFFS2 Erase Size for AT45 dataflash
2007-07-14 09:26:41 +02:00
Update JFFS2 page/erase size correctly
2007-10-18 00:01:58 +02:00
config BR2_TARGET_ROOTFS_JFFS2_CUSTOM
fs/jffs2: Fix mkfs.jffs2 --pagesize parameter usage Fixes #8186 Mkfs.jffs2 accepts a --pagesize parameter, which allows specifying the size of the virtual memory page size of the target machine, where the image will be used. (This is the value of the PAGE_SIZE macro in Linux.) In most cases the parameter doesn't need to be set as the default value of 4 kB is usually correct. The parameter was used incorrectly in Buildroot -- it was set to the page size of flash memory chip -- this commit fixes this problem. Now the --pagesize parameter is not used at all (unless the user explicitly chooses to use a custom value during configuration). All existing defconfigs were corrected to match the new configuration variable names. [Peter: reword, add Config.in.legacy handling] Signed-off-by: Michał Leśniewski <mlesniew@gmail.com> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2015-05-19 20:26:30 +02:00
bool "Select custom erase size"
Correct JFFS2 Erase Size for AT45 dataflash
2007-07-14 09:26:41 +02:00
Update JFFS2 page/erase size correctly
2007-10-18 00:01:58 +02:00
endchoice
config BR2_TARGET_ROOTFS_JFFS2_CUSTOM_EBSIZE
Correct JFFS2 Erase Size for AT45 dataflash
2007-07-14 09:26:41 +02:00
hex "Erase block size"
Update JFFS2 page/erase size correctly
2007-10-18 00:01:58 +02:00
depends on BR2_TARGET_ROOTFS_JFFS2_CUSTOM
Correct JFFS2 Erase Size for AT45 dataflash
2007-07-14 09:26:41 +02:00
default 0x20000
Update JFFS2 page/erase size correctly
2007-10-18 00:01:58 +02:00
help
Set to erase size of memory
Correct JFFS2 Erase Size for AT45 dataflash
2007-07-14 09:26:41 +02:00
config BR2_TARGET_ROOTFS_JFFS2_EBSIZE
Update JFFS2 page/erase size correctly
2007-10-18 00:01:58 +02:00
hex
default 0x2100 if BR2_TARGET_ROOTFS_JFFS2_DATAFLASH_1056
default 0x1080 if BR2_TARGET_ROOTFS_JFFS2_DATAFLASH_528
fs/jffs2: Fix mkfs.jffs2 --pagesize parameter usage Fixes #8186 Mkfs.jffs2 accepts a --pagesize parameter, which allows specifying the size of the virtual memory page size of the target machine, where the image will be used. (This is the value of the PAGE_SIZE macro in Linux.) In most cases the parameter doesn't need to be set as the default value of 4 kB is usually correct. The parameter was used incorrectly in Buildroot -- it was set to the page size of flash memory chip -- this commit fixes this problem. Now the --pagesize parameter is not used at all (unless the user explicitly chooses to use a custom value during configuration). All existing defconfigs were corrected to match the new configuration variable names. [Peter: reword, add Config.in.legacy handling] Signed-off-by: Michał Leśniewski <mlesniew@gmail.com> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2015-05-19 20:26:30 +02:00
default 0x4000 if BR2_TARGET_ROOTFS_JFFS2_NANDFLASH_16K
default 0x20000 if BR2_TARGET_ROOTFS_JFFS2_NANDFLASH_128K
Update JFFS2 page/erase size correctly
2007-10-18 00:01:58 +02:00
default 0x20000 if BR2_TARGET_ROOTFS_JFFS2_FLASH_128
default 0x10000 if BR2_TARGET_ROOTFS_JFFS2_FLASH_64
Remove redundant dollar signs in Config.in files Some Config.in(.host) files have constructs like: config FOO_VERSION string default "1.0" if FOO_1_0 default "2.0" if FOO_2_0 default $FOO_CUSTOM_VERSION if FOO_CUSTOM The dollar sign here is not needed and confusing, so can be removed. Signed-off-by: Thomas De Schampheleire <thomas.de.schampheleire@gmail.com> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2013-09-02 22:07:53 +02:00
default BR2_TARGET_ROOTFS_JFFS2_CUSTOM_EBSIZE if BR2_TARGET_ROOTFS_JFFS2_CUSTOM
Correct JFFS2 Erase Size for AT45 dataflash
2007-07-14 09:26:41 +02:00
- Additional JFFS2 options to support Dataflash (Ulf Samuelsson) - cleanup a bit while at it
2007-01-25 00:18:08 +01:00
config BR2_TARGET_ROOTFS_JFFS2_NOCLEANMARKER
- fix some whitespace damage.. - add COPYTO settings for cpio and tar and remove that ugly hardcoded DATE from that was added by Ulf
2007-10-05 14:55:40 +02:00
bool "Do not use Cleanmarker"
Support large sector NAND flash for JFFS2
2009-01-12 01:43:22 +01:00
default y if BR2_TARGET_ROOTFS_JFFS2_DATAFLASH_1056
default y if BR2_TARGET_ROOTFS_JFFS2_DATAFLASH_528
fs/jffs2: Fix mkfs.jffs2 --pagesize parameter usage Fixes #8186 Mkfs.jffs2 accepts a --pagesize parameter, which allows specifying the size of the virtual memory page size of the target machine, where the image will be used. (This is the value of the PAGE_SIZE macro in Linux.) In most cases the parameter doesn't need to be set as the default value of 4 kB is usually correct. The parameter was used incorrectly in Buildroot -- it was set to the page size of flash memory chip -- this commit fixes this problem. Now the --pagesize parameter is not used at all (unless the user explicitly chooses to use a custom value during configuration). All existing defconfigs were corrected to match the new configuration variable names. [Peter: reword, add Config.in.legacy handling] Signed-off-by: Michał Leśniewski <mlesniew@gmail.com> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2015-05-19 20:26:30 +02:00
default y if BR2_TARGET_ROOTFS_JFFS2_NANDFLASH_16K
default y if BR2_TARGET_ROOTFS_JFFS2_NANDFLASH_128K
- Additional JFFS2 options to support Dataflash (Ulf Samuelsson) - cleanup a bit while at it
2007-01-25 00:18:08 +01:00
help
Do not use cleanmarkers if using NAND flash or Dataflash where
the pagesize is not a power of 2
Patch from gtj: http://bugs.uclibc.org/view.php?id=40 0000040: Adds options to jffs2 filesystem creation Brings jffs2 up to the 20041007 build level so it will compile with both 2.4 and 2.6 kernels. Adds ability to specify eraseblock and pad sizes, permissions squash, big/little endian and device table in the configuration. Also adds capability to copy the resulting image to a secondary location like a tftp server's root directory. mtd.patch adds capabilities of the previously attached patch plus allows you to compile a version of the utilities to run on the target system. So now there's a set of config options under package to compile the utils for distribution to the target and a set of config options under target to create a jffs2 filesystem.
2005-01-23 12:16:11 +01:00
config BR2_TARGET_ROOTFS_JFFS2_PAD
bool "Pad output"
Fixup device table location
2005-03-09 18:30:20 +01:00
Patch from gtj: http://bugs.uclibc.org/view.php?id=40 0000040: Adds options to jffs2 filesystem creation Brings jffs2 up to the 20041007 build level so it will compile with both 2.4 and 2.6 kernels. Adds ability to specify eraseblock and pad sizes, permissions squash, big/little endian and device table in the configuration. Also adds capability to copy the resulting image to a secondary location like a tftp server's root directory. mtd.patch adds capabilities of the previously attached patch plus allows you to compile a version of the utilities to run on the target system. So now there's a set of config options under package to compile the utils for distribution to the target and a set of config options under target to create a jffs2 filesystem.
2005-01-23 12:16:11 +01:00
config BR2_TARGET_ROOTFS_JFFS2_PADSIZE
hex "Pad output size (0x0 = to end of EB)"
depends on BR2_TARGET_ROOTFS_JFFS2_PAD
default 0x0
help
- Additional JFFS2 options to support Dataflash (Ulf Samuelsson) - cleanup a bit while at it
2007-01-25 00:18:08 +01:00
Set to 0x0 to pad to end of erase block.
Fixup device table location
2005-03-09 18:30:20 +01:00
Patch from gtj: http://bugs.uclibc.org/view.php?id=40 0000040: Adds options to jffs2 filesystem creation Brings jffs2 up to the 20041007 build level so it will compile with both 2.4 and 2.6 kernels. Adds ability to specify eraseblock and pad sizes, permissions squash, big/little endian and device table in the configuration. Also adds capability to copy the resulting image to a secondary location like a tftp server's root directory. mtd.patch adds capabilities of the previously attached patch plus allows you to compile a version of the utilities to run on the target system. So now there's a set of config options under package to compile the utils for distribution to the target and a set of config options under target to create a jffs2 filesystem.
2005-01-23 12:16:11 +01:00
choice
prompt "Endianess"
fs/jffs2: refactor endianess selection to use BR2_ENDIAN Instead of explicitly listing the sub-architectures or architectures that are big-endian, use BR2_ENDIAN directly. Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
2013-04-07 11:25:24 +02:00
default BR2_TARGET_ROOTFS_JFFS2_BE if BR2_ENDIAN = "BIG"
Fixup device table location
2005-03-09 18:30:20 +01:00
Patch from gtj: http://bugs.uclibc.org/view.php?id=40 0000040: Adds options to jffs2 filesystem creation Brings jffs2 up to the 20041007 build level so it will compile with both 2.4 and 2.6 kernels. Adds ability to specify eraseblock and pad sizes, permissions squash, big/little endian and device table in the configuration. Also adds capability to copy the resulting image to a secondary location like a tftp server's root directory. mtd.patch adds capabilities of the previously attached patch plus allows you to compile a version of the utilities to run on the target system. So now there's a set of config options under package to compile the utils for distribution to the target and a set of config options under target to create a jffs2 filesystem.
2005-01-23 12:16:11 +01:00
config BR2_TARGET_ROOTFS_JFFS2_LE
bool "little-endian"
Fixup device table location
2005-03-09 18:30:20 +01:00
Patch from gtj: http://bugs.uclibc.org/view.php?id=40 0000040: Adds options to jffs2 filesystem creation Brings jffs2 up to the 20041007 build level so it will compile with both 2.4 and 2.6 kernels. Adds ability to specify eraseblock and pad sizes, permissions squash, big/little endian and device table in the configuration. Also adds capability to copy the resulting image to a secondary location like a tftp server's root directory. mtd.patch adds capabilities of the previously attached patch plus allows you to compile a version of the utilities to run on the target system. So now there's a set of config options under package to compile the utils for distribution to the target and a set of config options under target to create a jffs2 filesystem.
2005-01-23 12:16:11 +01:00
config BR2_TARGET_ROOTFS_JFFS2_BE
bool "big-endian"
Fixup device table location
2005-03-09 18:30:20 +01:00
Patch from gtj: http://bugs.uclibc.org/view.php?id=40 0000040: Adds options to jffs2 filesystem creation Brings jffs2 up to the 20041007 build level so it will compile with both 2.4 and 2.6 kernels. Adds ability to specify eraseblock and pad sizes, permissions squash, big/little endian and device table in the configuration. Also adds capability to copy the resulting image to a secondary location like a tftp server's root directory. mtd.patch adds capabilities of the previously attached patch plus allows you to compile a version of the utilities to run on the target system. So now there's a set of config options under package to compile the utils for distribution to the target and a set of config options under target to create a jffs2 filesystem.
2005-01-23 12:16:11 +01:00
endchoice
Add support for summarising JFFS2 images. With support in the kernel this improves mount time significantly.
2008-02-12 06:39:32 +01:00
config BR2_TARGET_ROOTFS_JFFS2_SUMMARY
bool "Produce a summarized JFFS2 image"
jffs2: cleanup Patch by Markus Heidelberg <markus.heidelberg@web.de> * remove needless help in invisible config options * correct wrong indenting * remove unused BR2 variables for default pagesize and devfile
2008-09-07 16:31:39 +02:00
help
A summarised image can be mounted faster if support is
enabled in the kernel (CONFIG_JFFS2_SUMMARY)
Add support for summarising JFFS2 images. With support in the kernel this improves mount time significantly.
2008-02-12 06:39:32 +01:00
fs/jffs2: Fix mkfs.jffs2 --pagesize parameter usage Fixes #8186 Mkfs.jffs2 accepts a --pagesize parameter, which allows specifying the size of the virtual memory page size of the target machine, where the image will be used. (This is the value of the PAGE_SIZE macro in Linux.) In most cases the parameter doesn't need to be set as the default value of 4 kB is usually correct. The parameter was used incorrectly in Buildroot -- it was set to the page size of flash memory chip -- this commit fixes this problem. Now the --pagesize parameter is not used at all (unless the user explicitly chooses to use a custom value during configuration). All existing defconfigs were corrected to match the new configuration variable names. [Peter: reword, add Config.in.legacy handling] Signed-off-by: Michał Leśniewski <mlesniew@gmail.com> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2015-05-19 20:26:30 +02:00
config BR2_TARGET_ROOTFS_JFFS2_USE_CUSTOM_PAGESIZE
bool "Select custom virtual memory page size"
help
Use a custom virtual memory page size. Note that this is not related to
the flash memory page size. Using this option is only needed if Linux is
configured to use a page size different than 4kB.
config BR2_TARGET_ROOTFS_JFFS2_CUSTOM_PAGESIZE
hex "Virtual memory page size"
depends on BR2_TARGET_ROOTFS_JFFS2_USE_CUSTOM_PAGESIZE
default 0x1000
help
Set to virtual memory page size of target system (in bytes). This value
should match the virtual page size in Linux (i.e. this should have the
same value as the value of the PAGE_SIZE macro in Linux). It is not
related to the flash memory page size.
target/jffs2: Put all sub options in a BR2_TARGET_ROOTFS_JFFS2 conditional And get rid of all the individual 'depends on B2_TARGET_ROOTFS_JFFS2'
2009-04-07 21:22:43 +02:00
endif
Reference in New Issue Copy Permalink