Topics

Contribution code for our platform

cheryl.su@...
 

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

Henrik Brix Andersen
 

Hi Cheryl,

That sounds very interesting. Looking forward to seeing your contribution!

Best regards,
Brix
--
Henrik Brix Andersen

On 15 Jun 2020, at 09.14, cheryl.su@... 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

Kumar Gala
 

On Jun 15, 2020, at 2:14 AM, cheryl.su@... 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!
There shouldn’t be an issue as long as you are willing to support the code associated with your SoC. Do you expect documentation to be public at some point?

Are you able to share any specific details of the SoC like a block diagram?

Do you guys have a HAL for drivers? If so what kinda of license are these drivers under?

- k

cheryl.su@...
 
Edited

thanks for your reply.
We will offer more our chip's information in the furture, and we are preparing some documents for public release.
Currently, we offer basic information (ex.support feature, hardwares, .... ) in the index.rst, and one board's photo.

And excuese me, does the HAL means the driver porting under the driver folder?
if it is. We have. We have already completed some feature such as interrupt, timer, uart.....and we will submit at the same time.

License will follow zephyr (
 Apache 2.0 license )

BR,