On 15 Jun 2020, at 09.14, cheryl.su@ite.com.tw wrote:

Hi all,

We are ITE and we want to submit our chip support to the upstream.
Our business partners have ever mentioned it in your weekly process meeting.
He says you are compleatedly OK eventhough our chip hasn't been release yet.
We appreciated for it!
Our Chip platform is called "IT8XXX2_evb" and it's RISCV32 base.

We will submit our code to zephyr git in this or next week.
Thanks for your review!

best regards,
Cheryl Su
ITE Tech. INC

I still see the old calendar entry and not the new one.

Thomas

Hi Carles,

 

Thanks.

 

Strange, that is not reflected in my calendar, which is linked to the zephyr calendar, but that must be a problem on my end though.

 

Regards,

  Danny

 

From: Cufi, Carles <Carles.Cufi@...>
Sent: 11. juni 2020 15:35
To: Danny Ørndrup (DAOR) <daor@...>; Rasmussen, Torsten <Torsten.Rasmussen@...>; devel@...
Subject: RE: [Zephyr-devel] Zephyr Toolchain Working Group Meeting – 11 June 2020 postponed to 18 June 2020

 

This message comes from outside of the corporate network. Please do not click links or open attachments unless you recognize the source of this e-mail and know the content is safe.

 

Hi Danny,

 

The calendar was updated earlier today.

 

Carles

 

From: devel@... <devel@...> On Behalf Of Danny Ørndrup (DAOR) via lists.zephyrproject.org
Sent: 11 June 2020 14:45
To: Rasmussen, Torsten <Torsten.Rasmussen@...>; devel@...
Subject: Re: [Zephyr-devel] Zephyr Toolchain Working Group Meeting – 11 June 2020 postponed to 18 June 2020

 

Hi Torsten,

 

Could you update the calendar? If not already done.

I believe that many will miss out, if the calendar does not reflect the rescheduling of the meeting.

 

Regards,

  Danny

 

From: devel@... <devel@...> On Behalf Of Rasmussen, Torsten via lists.zephyrproject.org
Sent: 11. juni 2020 11:45
To: devel@...
Subject: [Zephyr-devel] Zephyr Toolchain Working Group Meeting – 11 June 2020 postponed to 18 June 2020

 

This message comes from outside of the corporate network. Please do not click links or open attachments unless you recognize the source of this e-mail and know the content is safe.

 

Today’s meeting has been postponed to 18 June.

 

Sorry for the late notice.

 

See you all in a weeks’ time from now.

 

Best regards

 

Torsten T. Rasmussen           

 

Live meeting minutes: https://docs.google.com/document/d/1IQKBK-GcJNZG0O9QArqYfvb6Huk5xHscN-XIGEZr-z8/edit#heading=h.x36xe8bnwr9r

________________________________________________________________________________

 

Join Microsoft Teams Meeting

+1 213-437-3346   United States, Los Angeles (Toll)

Conference ID: 570 955 823#

Local numbers | Reset PIN | Learn more about Teams | Meeting options

________________________________________________________________________________

 

Hi Carles,

 

Thanks.

 

Strange, that is not reflected in my calendar, which is linked to the zephyr calendar, but that must be a problem on my end though.

 

Regards,

  Danny

 

From: Cufi, Carles <Carles.Cufi@...>
Sent: 11. juni 2020 15:35
To: Danny Ørndrup (DAOR) <daor@...>; Rasmussen, Torsten <Torsten.Rasmussen@...>; devel@...
Subject: RE: [Zephyr-devel] Zephyr Toolchain Working Group Meeting – 11 June 2020 postponed to 18 June 2020

 

This message comes from outside of the corporate network. Please do not click links or open attachments unless you recognize the source of this e-mail and know the content is safe.

 

Hi Danny,

 

The calendar was updated earlier today.

 

Carles

 

From: devel@... <devel@...> On Behalf Of Danny Ørndrup (DAOR) via lists.zephyrproject.org
Sent: 11 June 2020 14:45
To: Rasmussen, Torsten <Torsten.Rasmussen@...>; devel@...
Subject: Re: [Zephyr-devel] Zephyr Toolchain Working Group Meeting – 11 June 2020 postponed to 18 June 2020

 

Hi Torsten,

 

Could you update the calendar? If not already done.

I believe that many will miss out, if the calendar does not reflect the rescheduling of the meeting.

 

Regards,

  Danny

 

From: devel@... <devel@...> On Behalf Of Rasmussen, Torsten via lists.zephyrproject.org
Sent: 11. juni 2020 11:45
To: devel@...
Subject: [Zephyr-devel] Zephyr Toolchain Working Group Meeting – 11 June 2020 postponed to 18 June 2020

 

This message comes from outside of the corporate network. Please do not click links or open attachments unless you recognize the source of this e-mail and know the content is safe.

 

Today’s meeting has been postponed to 18 June.

 

Sorry for the late notice.

 

See you all in a weeks’ time from now.

 

Best regards

 

Torsten T. Rasmussen           

 

Live meeting minutes: https://docs.google.com/document/d/1IQKBK-GcJNZG0O9QArqYfvb6Huk5xHscN-XIGEZr-z8/edit#heading=h.x36xe8bnwr9r

________________________________________________________________________________

 

Join Microsoft Teams Meeting

+1 213-437-3346   United States, Los Angeles (Toll)

Conference ID: 570 955 823#

Local numbers | Reset PIN | Learn more about Teams | Meeting options

________________________________________________________________________________

 

Hi Torsten,

Could you update the calendar? If not already done.

I believe that many will miss out, if the calendar does not reflect the rescheduling of the meeting.

Regards,

  Danny

Are there any plans for Zephyr 2.3 to be BT SIG certified for host, controller, or profile (mesh) subsystems?

Here’s the agenda topics for this week:

* struct device - plans for 2.4:

https://github.com/zephyrproject-rtos/zephyr/issues/22941
https://github.com/zephyrproject-rtos/zephyr/issues/26072
https://github.com/zephyrproject-rtos/zephyr/issues/26073

* Any PR/issues w/dev-review tag

* Any topics anyone else has.

- k

Dear Zephyr developers,
According to the Zephyr Project Roles and Contribution Guidelines
documentation
(https://docs.zephyrproject.org/latest/contribute/project_roles.html#m
erge-criteria), pull requests against the Project’s main branch may be
merged with 2 approvals. Until now, we have been applying this policy
in GitHub, exclusively during Zephyr release stabilization periods
(applying 1-approval policy, otherwise). I would like to notify
everyone that as of now we will permanently enforce the 2-approval
policy.
Consequently, from now on, we will be needing extra assistance in PR
reviews to maintain a high-enough rate of getting PRs approved and
merged to Zephyr master branch.

A big thanks-in-advance to all for your extra efforts in PR reviewing
😊 Best Regards,
Ioannis glaropoulos | R&D
P +47 21 08 88 37 | Oslo, Norway
nordicsemi.com<http://www.nordicsemi.com/> |
devzone.nordicsemi.com<https://devzone.nordicsemi.com/>

[Nordic_logo_signature]<http://www.nordicsemi.com/>

Hi Carles,

thanks, I managed like this:

/ {
aliases {
eeprom_0 = &eeprom0;
};
};

but eeprom_0 is not a valid alias:

dtlib.DTError: /aliases: alias property name 'eeprom_0' should include
only characters from [0-9a-z-]

may I open an issue?

Stefano

Il giorno mar 9 giu 2020 alle ore 10:27 Cufi, Carles
<Carles.Cufi@nordicsemi.no> ha scritto:

For properties there is /delete-property/ to delete one and then be able to override it.
In the case of an alias I am not sure, have you tried to override it directly?

Carles

On 08/06/2020, 19:31, "devel@lists.zephyrproject.org on behalf of Stefano Manni via lists.zephyrproject.org" <devel@lists.zephyrproject.org on behalf of stefano.manni=gmail.com@lists.zephyrproject.org> wrote:

Hi there,

I'm trying to compile test/drivers/eeprom for my board. I see that the
code requires the alias 'eeprom_0' defined, but my board does not have
it natively.

I managed to compile changing in the test app some lines like below:

- eeprom = device_get_binding(DT_LABEL(DT_ALIAS(eeprom_0)));
+ eeprom = device_get_binding(DT_LABEL(DT_NODELABEL(eeprom0)));

where eeprom0 is defined in an overlay for my boards.

But I'd prefer to use the alias and not change the app.
What is the right way to override an alias in an overlay file? Sorry
if my question is already addressed somewhere in documentation.

Another consideration: is 'eeprom_0' a valid name? Alias properties
should include only characters from [0-9a-z-]. May we need to fix it?

Thanks,
Stefano