eas-dev April 2019

eas-dev@lists.linaro.org

7 participants
7 discussions

IoT Customers Marketing Contact Information

by angie.campos＠craftinsoft.com

<div dir="ltr"><div dir="ltr"><div>Hi,</div><div><br></div><div>I guess this is the appropriate time for you to target Competitors IoT Install Base with Service Providers/Partners/Resellers as for your strategic marketing and channel opportunities for 2019.</div><div><br></div><div>We also have distinctive Types Of development customers like: IBM IoT Users, AWS IoT Users, Cisco IoT Users, Prophet IoT Users , SAP IoT Users , Siemens IoT Users , PTC IoT Users, Autodesk IoT Users, Salesforce IoT Users </div><div><br></div><div>Kindly review and let me know if we can connect or let me know if I can share more insights on this.</div><div><br></div><div>Await your response!</div><div><br></div><div>Warm Regards</div><div>Angie Campos</div><div>Demand Generation</div><div><br></div><div><br></div><div><br></div><div>If you don't want to include yourself in our mailing list, please reply back “Leave Out"" in a subject line"</div><div><br></div></div></div> <p> </p><a style='display: block; margin: 32px 0 40px 0; padding: 10px; font-size: 1em; text-align: center; border: 0; border-top: 1px solid gray; ' href='chrome.google.com/webstore/detail/gsm-mailmerge/fjimadonilpeknihlnnkbgmlmjn…'>powered by GSM. Free mail merge and email marketing software for Gmail.</a>

5 years, 1 month

[Integration Branch] Update 12-Apr-2019

by Dietmar Eggemann

Hi, A new EAS integration branch eas/next/integration is available on http://linux-arm.org/git?p=linux-power.git . For further information about main features, test coverage and work items for next integration have a look at: https://developer.arm.com/tools-and-software/open-source-software/linux-ker… . Best Regards, -- Dietmar

5 years, 1 month

Re: [Eas-dev] M27500-22SB1T23-9-9 16400FT Container

by SHAANXIEng LLC

Good Morning, Please send me your best price as follows, thanks. 1. M27500-22SB1T23-9-9 16400FT Container 2. M22759/34-22-9 16400FT Container 3. M22759/34-24-9 16400FT Container 4. M22759/34-26-9 16400FT Container 5. M22759/34-20-9 16400FT Container 6. M22759/34-16-9 16400FT Container 7. M22759/6777-22-9 16400FT Container 8. M22759/333-24-9 16400FT Container 9. M22759/2222-26-9 16400FT Container 10. M22759/888-20-9 16400FT Container 11. M22759/999-16-9 16400FT Container Description and Spec has been attached Thanks & Best Regards Sally SHAANXI AIRCRAFT INDUSTRY(GROUP) AVIATION ELECTRONICS ENGINEERING CO., LTD Room2201,Blaock A, Gaoke Plaza,NO.1 Gaoxin 4 Road XI'AN City. TEL:0086+29-81879305 FAX:0086+29-81879306

5 years, 1 month

Re: [Eas-dev] FINS/1819/NSK/PO438 Confirmed

by WESMEC ENGINEERING PVT.LTD

Dear Sir, With reference to your PO NO. FINS/1819/NSK/PO438, the material is ready at our work. Please find attached herewith Proforma invoice for your reference. You are requested to please make the payment so that we can proceed further. Thanks & Regards, Ms. Meena Chavan, Account’s Manager - 8097070830 WESMEC ENGINEERING PVT.LTD

5 years, 1 month

Possible scheduling bug with Pixel 3 / Question for Google/CAF EAS Devs

by Zachariah Kennedy

Good day, First, I apologize for the information overload below. I just wanted to make sure to provided as much detail as possible. I do kernel development as a hobby for XDA and other communities. For a given device that we support, we tend to follow the same sched changes as Google and will pull in changes from upstream. One of the devices we dev for is the OnePlus6 and 6T. It uses the same SD845 SOC as the P3. Long story short, I started to notice an issue that we did not have on our Oneplus5 Device (SD835 same as the Pixel 2). When boosting top-app/schedtune.boost to 50 for example, it would appear to boost both small and big cores. With a boost of 50, this means both clusters would be running at 1766MHz and above. But this behavior was inconsistent. I could reboot, and sometimes only the big cluster would appear to be affected by the stune boost but it would seem that after hours/days of up time, the issue would occur again and both clusters would be affected. So I started kernel tracing trying to narrow down a culprit. One of the things I noticed between a trace that had the bug captured and a trace where the bug isn't occurring, is the boost margin assigned each cpu. I could tell this bug would occur when the boosted task could easily fit on a big core due to low utilization and margin assigned to them. Also, there was not any other noticeable reason I could discern. Below is an example of what I am referring to. Also note that I had a friend with a Pixel 3 confirm it had the problem as well before writing here and the logs/info below are taken from a P3. Kernel version: Linux version 4.9.124-gdff097c-ab5226088 (android-build@abfarm934) (Android clang version 5.0.1 (https://us3-mirror-android.googlesource.com/toolchain/clang 00e4a5a67eb7d626653c23780ff02367ead74955) (https://us3-mirror-android.googlesource.com/toolchain/llvm ef376ecb7d9c1460216126d102bb32fc5f73800d) (based on LLVM 5.0.1svn)) #0 SMP PREEMPT Fri Jan 11 21:28:03 UTC 2019 Extracted from PQ2A.190305.002 factory images Events used: sched_boost_cpu sched:sched_find_best_target sched:sched_boost_task sched:sched_load_balance sched:sched_migrate_task sched:sched_switch sched:sched_wakeup_new sched:sched_waking sched:sched_task_util sched:sched_tune_boostgroup_update sched:sched_tune_tasks_update Bug (no interaction): <idle>-0 [000] d.H9 12042.557751: sched_boost_cpu: cpu=0 util=22 margin=100 <idle>-0 [000] d.H9 12042.557756: sched_boost_cpu: cpu=1 util=26 margin=0 <idle>-0 [000] d.H9 12042.557759: sched_boost_cpu: cpu=2 util=0 margin=0 <idle>-0 [000] d.H9 12042.557761: sched_boost_cpu: cpu=3 util=4 margin=0 <idle>-0 [000] d.H9 12042.557764: sched_boost_cpu: cpu=4 util=0 margin=0 <idle>-0 [000] d.H9 12042.557767: sched_boost_cpu: cpu=5 util=0 margin=0 <idle>-0 [000] d.H9 12042.557770: sched_boost_cpu: cpu=6 util=0 margin=102 <idle>-0 [000] d.H9 12042.557772: sched_boost_cpu: cpu=7 util=0 margin=102 Bug during interactions: <...>-640 [000] d.H8 12044.737723: sched_boost_cpu: cpu=0 util=33 margin=495 <...>-640 [000] d.H8 12044.737725: sched_boost_cpu: cpu=1 util=22 margin=0 <...>-640 [000] d.H8 12044.737727: sched_boost_cpu: cpu=2 util=47 margin=0 <...>-640 [000] d.H8 12044.737728: sched_boost_cpu: cpu=3 util=12 margin=0 <...>-640 [000] d.H8 12044.737730: sched_boost_cpu: cpu=4 util=119 margin=0 <...>-640 [000] d.H8 12044.737732: sched_boost_cpu: cpu=5 util=83 margin=0 <...>-640 [000] d.H8 12044.737736: sched_boost_cpu: cpu=6 util=0 margin=512 <...>-640 [000] d.H8 12044.737738: sched_boost_cpu: cpu=7 util=2 margin=511 NO Bug during interactions: ndroid.settings-10354 [004] d.hb 117.480930: sched_boost_cpu: cpu=0 util=50 margin=0 ndroid.settings-10354 [004] d.hb 117.480932: sched_boost_cpu: cpu=1 util=184 margin=0 ndroid.settings-10354 [004] d.hb 117.480933: sched_boost_cpu: cpu=2 util=66 margin=0 ndroid.settings-10354 [004] d.hb 117.480934: sched_boost_cpu: cpu=3 util=46 margin=0 ndroid.settings-10354 [004] d.hb 117.480935: sched_boost_cpu: cpu=4 util=119 margin=452 ndroid.settings-10354 [004] d.hb 117.480936: sched_boost_cpu: cpu=5 util=2 margin=0 ndroid.settings-10354 [004] d.hb 117.480936: sched_boost_cpu: cpu=6 util=112 margin=0 ndroid.settings-10354 [004] d.hb 117.480937: sched_boost_cpu: cpu=7 util=7 margin=0 When you take a closer look at what is running on the small cores, I started to notice something else. With the event: sched_tune_tasks_update I noticed a pattern with tasks that had "boost=0 max_boost=50". When the bug is occurring, you would see small cores running tasks with "boost=0 max_boost=50" and when no bug, only big cores would have tasks with "boost=0 max_boost=50". I have not been able to track down why sometimes these tasks that received a boost as some point are running on small cores. I also cannot discern why this issue has been inconsistent. I wanted to give a heads up and would appreciate any assistance or information anyone here might have with regards to a possible solution. Thanks for the great work! I look forward to hearing back from you guys. I have uploaded the a number of traces captured to my G Drive here: https://drive.google.com/open?id=11YTlGezAMllmlVr9CtMNCz56CTfrJGBd If there is a better method, please let me know. Regards, Zachariah Kennedy

5 years, 2 months

[Integration Branch] Update 29-Mar-2019

by Dietmar Eggemann

5 years, 2 months

Re: [Eas-dev] Container# HLBU9223308 -DRAFT SHIPPING DOCUMENTS VSL ETA

by sandi cables LLC

Good Day! Please see attached copies of final documents that should be couriered this week by DHL to us. The details are below: kindly prepare the layouts and send to us also.. after which kindly send us DHL tracking : include all the invoices incase of remittance. All the best, Elisa Southon Nick kim Transaction Manager, Allodu cables LLC. Tel.:- +551 6 5985128 Fax.:- +551 6 5915102

5 years, 2 months

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

eas-dev April 2019