430-mtd-add-myloader-partition-parser.patch 1.6 KB

1234567891011121314151617181920212223242526272829303132333435363738394041424344454647
  1. From: Florian Fainelli <f.fainelli@gmail.com>
  2. Subject: Add myloader partition table parser
  3. [john@phozen.org: shoud be upstreamable]
  4. lede-commit: d8bf22859b51faa09d22c056fe221a45d2f7a3b8
  5. Signed-off-by: Florian Fainelli <f.fainelli@gmail.com>
  6. ---
  7. drivers/mtd/Kconfig | 16 ++++++++++++++++
  8. drivers/mtd/Makefile | 1 +
  9. 2 files changed, 17 insertions(+)
  10. --- a/drivers/mtd/Kconfig
  11. +++ b/drivers/mtd/Kconfig
  12. @@ -178,6 +178,22 @@ menu "Partition parsers"
  13. source "drivers/mtd/parsers/Kconfig"
  14. endmenu
  15. +config MTD_MYLOADER_PARTS
  16. + tristate "MyLoader partition parsing"
  17. + depends on ADM5120 || ATH25 || ATH79
  18. + ---help---
  19. + MyLoader is a bootloader which allows the user to define partitions
  20. + in flash devices, by putting a table in the second erase block
  21. + on the device, similar to a partition table. This table gives the
  22. + offsets and lengths of the user defined partitions.
  23. +
  24. + If you need code which can detect and parse these tables, and
  25. + register MTD 'partitions' corresponding to each image detected,
  26. + enable this option.
  27. +
  28. + You will still need the parsing functions to be called by the driver
  29. + for your particular device. It won't happen automatically.
  30. +
  31. comment "User Modules And Translation Layers"
  32. #
  33. --- a/drivers/mtd/Makefile
  34. +++ b/drivers/mtd/Makefile
  35. @@ -16,6 +16,7 @@ obj-$(CONFIG_MTD_AFS_PARTS) += afs.o
  36. obj-$(CONFIG_MTD_AR7_PARTS) += ar7part.o
  37. obj-$(CONFIG_MTD_BCM63XX_PARTS) += bcm63xxpart.o
  38. obj-$(CONFIG_MTD_BCM47XX_PARTS) += bcm47xxpart.o
  39. +obj-$(CONFIG_MTD_MYLOADER_PARTS) += myloader.o
  40. obj-y += parsers/
  41. # 'Users' - code which presents functionality to userspace.