Jump to content


Photo

single image for OEMs ?


  • Please log in to reply
2 replies to this topic

#1 Persian Prince

  • Senior Member
  • 1,982 posts

+247
Excellent

Posted 17 March 2015 - 08:50

Hi friends,
 
As you may know there are some brands and some resellers, in OE we call them OEMs.
When you want to create an image you can create it for the main brand or one of its resellers, for example take a look at https://github.com/o...lude/xp-oem.inc
 
Imagine you want to create for all brands and resellers like us but should we create an image multiple times and upload multiple files for just 1 model which has some small differences in production ?
 
In my opinion it's just a waste of time and resources even for end-users because they need to dig sites and upload centers for the correct file.
 
The main difference is the folder structure ("IMAGEDIR" variable) which you can rename it easily and repack it as a zip, don't worry about splash files they're just bmp pictures and you can remove or replace them. examples :
 
 
We can ship CFE related files with the image but if the image is for multiple models we must not ship it, for example azboxme could be published with MICOM file but releasing an image with CFE for technomate brand is wrong because it's possible that a user try to install it on an OEM and burn his money which I don't want to happen.
 
An example for "MKUBIFS_ARGS" variable which is for nand flash size : https://github.com/o...lackbox-oem.inc
 
In this example we need to compile 2 images because the difference is in flash size like dm7020hd and dm7020hdv2 so it means we would have 2 different image files.
 

In some OEMs it's more complex because we have more variables "MTD_KERNEL" and "MTD_ROOTFS" :
 
 
Which I don't know much about them.
 
Also we have another example for different drivers : https://github.com/o...ude/ini-oem.inc
 
What do you think ? How we can manage to release less images for almost all OEMs ?
 
Maybe we can create a tool (linux or windows) that could repack the main image for OEMs with specific data table, Users could download extra files (kernel, splash, ...) for OEMs and repack them.

 


Open Vision sources: https://github.com/OpenVisionE2


Re: single image for OEMs ? #2 babsy98

  • Senior Member
  • 166 posts

+18
Neutral

Posted 23 March 2015 - 10:35

you are in pli forum not oe-a (atv) forum :P

 

but we dont change it, the build per oem need only 5 min for me its not a big issue



Re: single image for OEMs ? #3 MiLo

  • PLi® Core member
  • 14,042 posts

+298
Excellent

Posted 23 March 2015 - 11:15

OpenEmbedded manages the similarities already pretty well. No need to add additional complexity to solve something that has already been solved.
Real musicians never die - they just decompose


1 user(s) are reading this topic

0 members, 1 guests, 0 anonymous users