release: Remove some arm board release config

[manu]

Summary

Those board are mostly obsolete (like gumstix or pandaboard) or
have other images where overwriting u-boot is enough.

[• ian]

Does this mean that cubox-humingboard images will no longer be available for download?

[manu]

In D16237#344539, @ian wrote:

Does this mean that cubox-humingboard images will no longer be available for download?

Yeah.
It is still popular enough so we leave it ?

[• ian]

In D16237#344541, @manu wrote:

In D16237#344539, @ian wrote:

Does this mean that cubox-humingboard images will no longer be available for download?

Yeah.
It is still popular enough so we leave it ?

Yeah. In the imx6 world there are basically two popular product lines of consumer/hobbyist boards: wandboard, and cubox/hummingboard (other product lines tend to be aimed more at OEMs and embedded systems products).

I think it is true that the only difference between a wandboard image and a cubox image is the uboot. I don't know if there's some way to leverage that to generate two downloadable images from one build to save time.

[imp]

Hmmm, I have all these boards except the GUMSTIX :).

Having said that, if the arm install image can create these from a generic image, I'm good.

[imp]

Except maybe the hummingboard one

[gjb]

In D16237#344541, @manu wrote:

In D16237#344539, @ian wrote:

Does this mean that cubox-humingboard images will no longer be available for download?

Yeah.
It is still popular enough so we leave it ?

Personally, I'm in the camp of "why remove supported hardware for the sake of removing supported hardware?"

I don't really see it as "extra" work to keep support, unless however there is special edge-cases in code in the tree that makes it more difficult to retain these boards.