Hi Jo,
On 01.12.2017 14:37, Jo-Philipp Wich wrote:
Hi,
I still have here some concerns/thoughts:
1. I don't know how to deal in above approach with region variant images
but I'm sure we should _somehow_ separate region code from boardname and
other parts of the image filename. IMHO, dash character won't work here.
2. We have some boards versions like "v2.1" which with my above approach
would end up as "v2-1". Maybe we should keep dot as a valid character in
version part?
3. Some of devices come in different RAM/flash configurations and in
case where common image can't support all of them, we include
information about RAM/flash variant sometimes only in image name and
sometimes in both the image name and boardname/compatible string. A
common and defined approach would be required for this as well.
A number of these issues can also be addressed by producing a Manifest
file in the same directory which allows users to map unique board
identifications to an appropriate image file.
This would also work for cases where multiple boards share the very same
file.
That might be a solution but wouldn't it mean more meta data/information
about devices included in building code? Or how could that manifest file
be automatically generated otherwise?
--
Cheers,
Piotr
_______________________________________________
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev
