aboutsummaryrefslogtreecommitdiffstats
path: root/common/mel
AgeCommit message (Collapse)Author
2019-07-18common: remove mentor specific mini-x-session display resolution configArsalan H. Awan
This removes a mentor specific mini-x-session display resolution setting where mini-x-session sets the display resolution to 1024x768 by default by invoking xrandr, whereas we wanted the system to make use of all the available resolution on the 4k displays. This isn't applicable anymore, therefore removing it in preparation for yocto based warrior branch Signed-off-by: Arsalan H. Awan <Arsalan_Awan@mentor.com>
2018-11-15mini-x-session: do not force a display sizeAwais Belal
The mini-x-session forces a display size of 1024x768 which is way too low where our platforms support 4k displays. Simply remove the forcing of the display size from the session manager so the maximum is picked up automatically. Signed-off-by: Awais Belal <awais_belal@mentor.com>
2018-06-22Created IMAGE_FEATURES to be used by AMD BSPs removing all img.bbappendsArsalan H. Awan
This defines AMD Features that can be added as EXTRA_IMAGE_FEATURES to different machines based on what is supported on a machine. This adds a broad flexibility and control over packages being installed on a machine for any image without needing to create bbappends for all the images that are to be supported. > Each feature can contain packages and packagegroups as its components. > Feature components can be dependent on DISTRO, IMAGE_FEATURE, or any variable in general. e.g.: Components of "amd-feature-graphics" may be dependent on "x11-base" as an IMAGE_FEATURE. Some packages may only be included for a specific DISTRO. Some packages may only be installed if user allows them in local.conf etc. > Each machine must add the required features to EXTRA_IMAGE_FEATURES in its own machine config file. > All required features must be added to a machine regardless of the image being built, but make sure that feature components are included based on dependency conditions. e.g. say "amd-feature-graphics" was added to a machine that supported graphics, but components of this feature must not be installed on an image that is only console based such as "core-image-base", therefore such components must depend on an IMAGE_FEATURE that is based on graphics such as "x11-base". > Each machine can also override feature components in its own machine config when adding the feature to EXTRA_IMAGE_FEATURES. e.g.: a feature may be added to a specific machine with minimal (or extended) packages based on requirement. Features are classified as: * amd-common-pkgs : Common pkgs to be added to all machines * amd-feature-multimedia : Multimedia packages (it does not depend on graphics because a machine may not have a GUI but could play videos and sounds from console) * amd-feature-graphics : Graphics packages * amd-feature-networking : Networking packages * amd-feature-debug-profile : Debugging and Profiling tools * More features may be added later as needed Signed-off-by: Arsalan H. Awan <Arsalan_Awan@mentor.com>
2018-04-24Merge remote-tracking branch 'morty' into 'master'Awais Belal
2018-03-29console-image: install strongswan for snowyowlAwais Belal
Install the strongswan package conditionally for the snowyowl BSP only. Signed-off-by: Awais Belal <awais_belal@mentor.com>
2016-12-28core-image-minimal-*: allow using extrausers functionalityAwais Belal
This fixes the do_rootfs issues that come up while using the extrausers functionality. The extrausers class requires shadow as well as base-passwd to leverage the functionality of the class. In case of initramfs images the PACKAGE_INSTALL variable is overriden in a way that the additions done through extrausers bbclass are rendered useless. Signed-off-by: Awais Belal <awais_belal@mentor.com>
2016-06-23amd-multimedia: change to amd-commonMichael
2015-02-10Fix console-image supportMichael