kobs-ng: new package

---
 package/Config.in             |    1 +
 package/kobs-ng/Config.in     |    4 ++
 package/kobs-ng/kobs-ng.mk    |   18 +++++++++++
 package/kobs-ng/kobs-ng.patch |   67 +++++++++++++++++++++++++++++++++++++++++
 4 files changed, 90 insertions(+), 0 deletions(-)
 create mode 100644 package/kobs-ng/Config.in
 create mode 100644 package/kobs-ng/kobs-ng.mk
 create mode 100644 package/kobs-ng/kobs-ng.patch

index ed373de..c16b306 100644
@@ -207,6 +207,7 @@ source "package/f2fs-tools/Config.in"
 source "package/flashbench/Config.in"
 source "package/genext2fs/Config.in"
 source "package/genromfs/Config.in"
+source "package/kobs-ng/Config.in"
 source "package/makedevs/Config.in"
 source "package/mtd/Config.in"
 source "package/nfs-utils/Config.in"

new file mode 100644
index 0000000..6204af4
@@ -0,0 +1,4 @@
+config BR2_PACKAGE_KOBS_NG
+	bool "kobs-ng"
+	help
+	  Build freescale kobs-ng utility for burning bootstreams to NAND

new file mode 100644
index 0000000..8f877ca
@@ -0,0 +1,18 @@
+################################################################################
+#
+# kobs-ng
+#
+################################################################################
+
+# kobs-ng versions have never made much sense :(
+KOBS_NG_VERSION = 3.0.35-4.0.0
+KOBS_NG_SOURCE = kobs-ng-$(KOBS_NG_VERSION).tar.gz
+KOBS_NG_SITE = http://repository.timesys.com/buildsources/k/kobs-ng/kobs-ng-$(KOBS_NG_VERSION)/
+KOBS_NG_LICENSE = GPLv2
+KOBS_NG_LICENSE_FILES = COPYING
+
+define KOBS_NG_INSTALL_TARGET_CMDS
+  install -D -m 0755 $(@D)/src/kobs-ng $(TARGET_DIR)/usr/sbin
+endef
+
+$(eval $(autotools-package))

1.7.8.6

Dear Paul B. Henson,

Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com

The menu says "Filesystem and flash utilities", kobs-ng is a flash utility, so it initially made sense to me. I can move it to the hardware section if you prefer.

There isn't really an upstream URL for this specific package. Although it is GPL, and freely distributable, Freescale releases it as part of their board support packages, not as a standalone package. The only way to get it from Freescale is by downloading an entire BSP, each one of which usually has a different version of kobs-ng in it.

It's similar to the existing Freescale elftosb package already in the tree. Although it doesn't look like there is a Config.in in the elftosb directory, only elftosb.mk, so I'm not sure what the current status of that package is.

I see there are also a few other Freescale specific firmware and library packages in the tree (freescale-imx directory), they all say "This library is provided by Freescale as-is and doesn't have an upstream.", should I just put something similar?

You mean the source line, not the version line, right?

I remember having problems with it on an earlier version, I'll test again with this version and see if they were resolved.

Yes, the tool is typically used on the target itself. I don't have extensive experience with freescale, but my understanding is you typically bootstrap via some other boot method (SD card, USB-DFU, etc) to initially burn a bootstream to NAND. At that point, you can update the bootloader in an environment booted from NAND. u-boot has a tool called mxsboot that tries to generate a bootstream image that can be burned directly to NAND, but it makes a lot of assumptions about things kobs-ng determines dynamically and it seems more reliable to use the freescale purposed tool on the actual target environment.

I'll add a header. I'm really not sure how one would submit changes to freescale upstream; AFAIK their code repository is not public and they don't have a mailing list for this tool's development. They have some general-purpose forums, and there are a fair number of freescale employees subscribed to various embedded oriented mailing lists (perhaps even this one?), but short of purchasing a support contract I don't know that there is any way to get official freescale notice of a patch submission.

Thanks?

I resubmitted the patch to add kobs-ng; I think I addressed all of your feedback other than the category. I don't think I saw a response to this, so I left it in the flash utility category. I can move it to the hardware handling category and resubmit if you still think that's a better place for it.

Thanks...