[CELADON] GITHUB 2018_WW44 Kernel 4.19 Rebase Status
by Balan, Swaroop
Hello All,
Celadon Status on GitHub Rebase for kernel 4.19 on WW44
Work Week
WW44
Kernel Tag ( 4.19 )
mainline-tracking-v4.19-rc7-android-181012T051938Z
Validation is done For APL-NUC results:-
Highlights:
Component
Result
Wi-Fi basic connect and disconnect
Pass
WIFI Hotspot
Pass
BT basic connect and disconnect
Pass
BT file transfer
Pass
BT Message send/Receive to Reference phone
Pass
Basic Ethernet
Pass
Audio
Pass
Adb connect over Wi-Fi
Pass
Adb connect over Ethernet
Pass
BT phone call/receive the call
Pass
Security pin lock and Unlock
Pass
Note : Please feel free to report issues if observed with this Kernel rebase .
Regards,
Swaroop Balan
3 years, 11 months
Re: [01.org Celadon] NUC6CAYS/eMMC
by N, Shyjumon
Hi,
eMMC is not supported in celadon as of now.
Means that there is no support in kernel flinger, however the kernel drivers are in place, though it is not validated for eMMC boot or external storage.
Thank you and Regards,
Shyjumon N.
From: Celadon [mailto:celadon-bounces@lists.01.org] On Behalf Of Bernard Carter
Sent: Wednesday, October 10, 2018 11:54 PM
To: celadon(a)lists.01.org<mailto:celadon@lists.01.org>
Subject: [01.org Celadon] NUC6CAYS/eMMC
Hi,
I've been testing Celadon on two platforms, both with eMMC (NUC6CAYS and a Celeron N3350 APL device). For the NUC6CAYS I've disabled the eMMC and used an SATA SSD. Our final product plans, however, require use of eMMC storage. Kernelflinger appears to not support the flavor of eMMC being used by these two devices. When using a GRUB installer image, I'm able to lay it down, but the unit fails to boot and eventually shuts off. Is there any guidance around usage of eMMC storage with Celadon?
Thanks,
Bernard
3 years, 11 months
[ww42] GFX stack release is ready on https://github.com/projectceladon
by Cao, Jenny Q
Swaroop, Rakesh, Sundar
FYI,
The ww42 GFX stack release is ready on https://github.com/projectceladon
The release pass the GFX sanity tests and PnP tests on celadon (IVI).
This round release include fix for following bugs and improvements:
* OAM-68393<https://jira01.devtools.intel.com/browse/OAM-68393> [REG][P Native][MR0][Gordon_Peak][VTS]VtsHalGraphicsComposerV2_1Target#GraphicsComposerHidlTest.CreateVirtualDisplay(default) failed
* OAM-70126<https://jira01.devtools.intel.com/browse/OAM-70126> [P Native][MR0][Gordon_Peak][CTS] SingleLayer_ColorTest_GpuColorOutputCpuRead_R8G8B8X8_UNORM and SingleLayer_ColorTest_GpuColorOutputIsRenderable_R8G8B8X8_UNORM test fail in android.hardware.nativehardware.cts.AHardwareBufferNativeTests test
* OAM-70128<https://jira01.devtools.intel.com/browse/OAM-70128> [P Native][MR0][Gordon_Peak][CTS] android.hardware.nativehardware.cts.AHardwareBufferNativeTests#SingleLayer_ColorTest_GpuSampledImageCanBeSampled_R10G10B10A2_UNORM in CtsNativeHardwareTestCases module test fail
* OAM-70130<https://jira01.devtools.intel.com/browse/OAM-70130> [P Native][MR0][Gordon_Peak][CTS] android.hardware.nativehardware.cts.AHardwareBufferNativeTests#SingleLayer_ColorTest_GpuSampledImageCanBeSampled_R8G8B8_UNORM in CtsNativeHardwareTestCases module test fail
Latest Commit
Hwcomposer (2 commits):
26fd66082d5c74e41dfa545e90519a8c0a1c77e9 Corret the condition check which will casue DestroyVirtualDisplay failure
590e20d84d4f61b22a70163f78b3a8145ca166e9 Set HWC as DRM master when got exclusive lock of /vendor/hwc.lock.
Minigbm(5 commits):
f74457a7ee1eb615b2cd9491dbf8c720af87a0af Revert "Fix GRALLOC1_PFN_LOCK_FLEX multithread issue." for it is causing android.view.cts.SurfaceViewSyncTest regressions
ef696f52e18d448e2323f6d88d316be779780db0 Don't advertise BGR24 as a render/texture target
6560d7e4685b34f2ed05392f472f234874c71fa1 Remove 32bit RGB format support
c6971682cf6d8fed5f6d69b3c3c6c194ac7fdf69 Fix GRALLOC1_PFN_LOCK_FLEX multithread issue.
04ebd80cbb5c58d0f95f5c831ae27fbff0796daa Revert "Added Support for 64bit RGB format" This reverts commit 47bd806579dd The Android framework uses successful allocation of HAL_PIXEL_FORMAT_RGBA_FP16 to test for wide-gamut capabilities. We don't want to advertise this, so let's revert.
Thanks
Jenny
3 years, 11 months
MediaSDK OMX license
by Cyan Dro
Hi,
while going through the Project Celadon repositories I noticed that
https://github.com/projectceladon/mediasdk_release contains
proprietary binaries without any license. It seems like MediaSDK
itself is open-source, but the OMX implementation is still
proprietary. Without any license that at very least allows
redistribution, I'm unable to build on Project Celadon for my project.
Could you clarify the licensing situation for these binaries?
By the way, it's a pity that these are only released as binaries,
given that Project Celadon is an effort to build an *open-source*
software reference stack for the Intel architecture. I'm guessing
there are licensing issues that make it difficult to open-source these
components? Are there still plans to open-source it eventually?
Ideally, I'd like to build on a fully open-source stack for my project
(excluding firmware).
Thanks in advance,
Cyan
3 years, 11 months
dgnss
by Jose Luis
Hi all.
In previous intel android project android-ia, there was support for
BCM4752 dgnss. Is there support for this gps chip in Celadon?
Thanks
3 years, 11 months
Failed to instantiate OMX.Intel.hw_ve.h264 (celadon ) encoder in NUC7i7BNH
by Sathish
Hi,
I am trying to create an encoder instance, for a video calling app that I
am deploying on NUC7i7BNH.
* encoderInstance = MediaCodec.createByCodecName("OMX.Intel.hw_ve.h264");*
l am seeing below error message, not sure why .
Are decoder/encoders support only available on specific NUC variants as of
now ?
Any configurations, required in celadon build to enable this support ?
Appreciate any inputs on this.
10-16 10:00:39.306 4164 6115 I OMXClient: IOmx service obtained
10-16 10:00:39.307 3351 4656 I OMXMaster:
makeComponentInstance(OMX.Intel.hw_ve.h264) in omx(a)1.0-service process
10-16 10:00:39.307 3351 4656 I libva : VA-API version 1.0.0
10-16 10:00:39.307 3351 4656 I libva : va_getDriverName() returns 0
10-16 10:00:39.307 3351 4656 I libva : Trying to open
/vendor/lib//i965_drv_video.so
10-16 10:00:39.308 3351 4656 I libva : Found init function
__vaDriverInit_1_0
10-16 10:00:39.308 3351 4656 I libva : va_openDriver() returns 0
10-16 10:00:39.308 3351 4656 I mediasdk_omx: mfx_omx_dev_android: Driver
version is Intel iHD driver - 2.0.0
10-16 10:00:39.308 3351 4656 D vndksupport: Loading /vendor/lib/hw/
gralloc.project-celadon.so from current namespace instead of sphal
namespace.
10-16 10:00:39.309 3351 4656 D vndksupport: Loading /vendor/lib/hw/
gralloc.project-celadon.so from current namespace instead of sphal
namespace.
*10-16 10:00:39.309 3351 4656 E mediasdk_omx: mfx_omx_venc_component:
Init[line 261]: Failed to create OMX.Intel.hw_ve.h264, error 0x80001001*
10-16 10:00:39.310 3351 4656 I mediasdk_omx: mfx_omx_venc_component:
Destroyed OMX.Intel.hw_ve.h264
10-16 10:00:39.310 3351 4656 E media.codec: Failed to allocate omx
component 'OMX.Intel.hw_ve.h264' err=InsufficientResources(0x80001000)
10-16 10:00:39.310 4164 6115 E ACodec : Unable to instantiate codec
'OMX.Intel.hw_ve.h264' with err 0xfffffff4.
10-16 10:00:39.310 4164 6115 E ACodec : signalError(omxError 0xfffffff4,
internalError -12)
10-16 10:00:39.310 4164 6115 E MediaCodec: Codec reported err 0xfffffff4,
actionCode 0, while in state 1
10-16 10:00:39.309 4164 4164 I .application.ng: type=1400 audit(0.0:108):
avc: denied { read } for name="video4linux" dev="sysfs" ino=8618
scontext=u:r:untrusted_app_27:s0:c512,c768 tcontext=u:object_r:sysfs:s0
tclass=dir permissive=1
Thanks,
Sathish
3 years, 11 months
FW: [ww41] GFX stack release is ready on https://github.com/projectceladon
by Cao, Jenny Q
Resent to celadon project mailing list ,seems yesterday's mail not reach to celadon mailing list
From: Cao, Jenny Q
Sent: Tuesday, October 16, 2018 3:51 PM
To: Balan, Swaroop <swaroop.balan(a)intel.com>; Reddy, RakeshX <rakeshx.reddy(a)intel.com>; Gnanasekaran, Sundar <sundar.gnanasekaran(a)intel.com>; 'celadon(a)lists.01.org' <celadon(a)lists.01.org>
Cc: '1a-gfx-dev(a)eclists.intel.com' <1a-gfx-dev(a)eclists.intel.com>
Subject: [ww41] GFX stack release is ready on https://github.com/projectceladon
Swaroop, Rakesh, Sundar
FYI,
The ww41 GFX stack release is ready on https://github.com/projectceladon
The release pass the GFX sanity tests and PnP tests on celadon (IVI).
This round release include fix for following bugs and improvements:
1. OAM-68565<https://jira01.devtools.intel.com/browse/OAM-68565> [BXT-P][P-MR0-Master][Gordon_Peak] Early EVS exit after boot up to android interface when output via HDMI1 and HDMI2
OAM-68857<https://jira01.devtools.intel.com/browse/OAM-68857> SolidColor Layer can't be show by HWC
OAM-70154<https://jira01.devtools.intel.com/browse/OAM-70154> [reg] HVAC does not response when frequently click
OAM-66461<https://jira01.devtools.intel.com/browse/OAM-66461> [REG][P-MR0-Master]:Delay Observed When adding new user From overview
OAM-67797<https://jira01.devtools.intel.com/browse/OAM-67797> [ACRN][AaaG][MRB ClearLinux][ApolloLake] Android UI reboot randomly during video playback
OAM-67979<https://jira01.devtools.intel.com/browse/OAM-67979> Display Rotation has glitches
OAM-68867<https://jira01.devtools.intel.com/browse/OAM-68867> GP2.0 [HWC] Add functionality to handle PAVP/HDCP tear-down
1.
Latest Commit
Hwcomposer (11 commits):
51116d7e4871af0f2926476097575d270760b5d1 Add function to transfrom source damage to rendering damage this paritial incorparate 145bf9c5853cb5b0de0136a076d1a8b9b0b1c8dc aftering reverting it. Also consider the situation source corp is not the same size with display_rect. That means we also have to scale the output rendering damage rect
a1687b0b78fddfafcfd3fd430a89a174ea56f3e1 Implement PAVP tear down support When any PAVP session disabled, HWC suppose to not compose any protected video
26ba8ac5c1e18efff726eecf86dd4d5e80270600 Added ignore_updates_ to track if HWC needs to ignore rendering request. Don't invoke display's ForceRefresh if ignore_updates_ is true.
c7e6fc4759d23dc9bf25240576c49d559b4d519f Revert "Apply damage transformations in GetLayerDamage" Flicker is observed when start an APK after this patch. for example use Car Launcher
00ae7521e9bad8c41efd6ec96a442804807a4b12 Fix the memory leak in virtualdisplay.cpp. The memory leak causing the dmabuf fd that hwc opened increase all the time. Causing th
76cd727a9324180bc26e1a08509d0edf624ec3e9 Implement display rotation.
2070a38e22953eaa5a0c826f253d4b15f98fcc0d Remove blocking commit wrongly merged It is wrongly added in SolidColor support
62b089ea0791a88577fc8d8a69b9a41dc25751a1 SetOverlayLayer: DisplayPlaneState should also update displayframe and source crop, otherwise if GetDisplayFrame etc is called for
5efa58500dbd9f61811e6b169f67d06a72ec95f4 Add support for SolidColor Type layer in HWC It is a layer without buffer handler, it expected HWC can fill the layer with color (0
19c940d1943c773a5d1ebe8eb0a935299680c678 Removing deinterlace frame by frame check as it because FPS regression for video Also fixed performance regression caused by 21c2f60
ed1de2fc03a7dc1748b4cdb9d16f4ef3525d2698 Update AliOS support
Thanks
Jenny
3 years, 11 months
