|
Re: About the U-Boot policy
Hello Daniel,
Sorry we missed you!
Thank you for resuming the conversation.
Chris: Agreed.
Chris: Ideally yes, but currently I don't think all of the reference boards are in mainline u-boot, and
Hello Daniel,
Sorry we missed you!
Thank you for resuming the conversation.
Chris: Agreed.
Chris: Ideally yes, but currently I don't think all of the reference boards are in mainline u-boot, and
|
By
Chris Paterson
·
#371
·
|
|
[PATCH 6/6] ARM: shmobile: r8a7745: basic SoC support
From: Sergei Shtylyov <sergei.shtylyov@...>
Add minimal support for the RZ/G1E (R8A7745) SoC.
Signed-off-by: Sergei Shtylyov <sergei.shtylyov@...>
Reviewed-by: Geert
From: Sergei Shtylyov <sergei.shtylyov@...>
Add minimal support for the RZ/G1E (R8A7745) SoC.
Signed-off-by: Sergei Shtylyov <sergei.shtylyov@...>
Reviewed-by: Geert
|
By
Biju Das <biju.das@...>
·
#370
·
|
|
[PATCH 5/6] ARM: shmobile: Consolidate R8A7743 and R8A779[234] machine definitions
From: Laurent Pinchart <laurent.pinchart+renesas@...>
The four SoCs use identical machine operations, consolidate them into
two machine definitions in a single file.
Signed-off-by:
From: Laurent Pinchart <laurent.pinchart+renesas@...>
The four SoCs use identical machine operations, consolidate them into
two machine definitions in a single file.
Signed-off-by:
|
By
Biju Das <biju.das@...>
·
#369
·
|
|
[PATCH 4/6] ARM: shmobile: r8a7743: basic SoC support
From: Sergei Shtylyov <sergei.shtylyov@...>
Add minimal support for the RZ/G1M (R8A7743) SoC.
Based on the original (and large) patch by Dmitry
From: Sergei Shtylyov <sergei.shtylyov@...>
Add minimal support for the RZ/G1M (R8A7743) SoC.
Based on the original (and large) patch by Dmitry
|
By
Biju Das <biju.das@...>
·
#368
·
|
|
[PATCH 3/6] sh-sci: document R8A7743/5 support
From: Sergei Shtylyov <sergei.shtylyov@...>
Renesas RZ/G SoC also have the SCIF, SCIFA, SCIFB, and HSCIF ports and
they seem compatible with the R-Car gen2 SoC in this
From: Sergei Shtylyov <sergei.shtylyov@...>
Renesas RZ/G SoC also have the SCIF, SCIFA, SCIFB, and HSCIF ports and
they seem compatible with the R-Car gen2 SoC in this
|
By
Biju Das <biju.das@...>
·
#367
·
|
|
[PATCH 2/6] DT: irqchip: renesas-irqc: document R8A7743/5 support
From: Sergei Shtylyov <sergei.shtylyov@...>
Renesas RZ/G SoC have the R-Car gen2 compatible IRQC interrupt controllers.
Document RZ/G1[ME] (also known as R8A774[35]) SoC
From: Sergei Shtylyov <sergei.shtylyov@...>
Renesas RZ/G SoC have the R-Car gen2 compatible IRQC interrupt controllers.
Document RZ/G1[ME] (also known as R8A774[35]) SoC
|
By
Biju Das <biju.das@...>
·
#366
·
|
|
[PATCH 1/6] sh_eth: add R8A7743/5 support
From: Sergei Shtylyov <sergei.shtylyov@...>
Add support for the first two members of the Renesas RZ/G family, RZ/G1M/E
(also known as R8A7743/5). The Ether core is the same as in the
From: Sergei Shtylyov <sergei.shtylyov@...>
Add support for the first two members of the Renesas RZ/G family, RZ/G1M/E
(also known as R8A7743/5). The Ether core is the same as in the
|
By
Biju Das <biju.das@...>
·
#365
·
|
|
[PATCH 0/6] Basic SoC support for r8a7743/r8a7745
This series aims to add basic SoC support for
r8a7743/r8a7745. All the patches in this series
are cherry-picked from the upstream kernel.
This series has been tested against linux-cip tag
This series aims to add basic SoC support for
r8a7743/r8a7745. All the patches in this series
are cherry-picked from the upstream kernel.
This series has been tested against linux-cip tag
|
By
Biju Das <biju.das@...>
·
#364
·
|
|
Re: Project-X (minimal root filesystem) : rewrite and renesas iwg20m board support
Err, right, that's what I meant.
Yes, I'm sure. I've just written the doc for a product SDK, and that
uses no further settings as well,
Err, right, that's what I meant.
Yes, I'm sure. I've just written the doc for a product SDK, and that
uses no further settings as well,
|
By
Jan Kiszka
·
#363
·
|
|
Re: Project-X (minimal root filesystem) : rewrite and renesas iwg20m board support
By
Daniel Sangorrin <daniel.sangorrin@...>
·
#362
·
|
|
Re: Project-X (minimal root filesystem) : rewrite and renesas iwg20m board support
We should probably suggest to call "USER_ID=$(id -u) docker run ..." -
it there a way to achieve this in an easier way? Still learning all this
docker stuff.
Hmm, they should, I'm using them for
We should probably suggest to call "USER_ID=$(id -u) docker run ..." -
it there a way to achieve this in an easier way? Still learning all this
docker stuff.
Hmm, they should, I'm using them for
|
By
Jan Kiszka
·
#361
·
|
|
Re: Project-X (minimal root filesystem) : rewrite and renesas iwg20m board support
Hi Jan,
By
Daniel Sangorrin <daniel.sangorrin@...>
·
#360
·
|
|
Re: Project-X (minimal root filesystem) : rewrite and renesas iwg20m board support
Looks good. You should just set version to 0.10 and use yesterday's
release. You can pull the corresponding docker image from
https://hub.docker.com/r/kasproject/, and there should be a pip package
as
Looks good. You should just set version to 0.10 and use yesterday's
release. You can pull the corresponding docker image from
https://hub.docker.com/r/kasproject/, and there should be a pip package
as
|
By
Jan Kiszka
·
#359
·
|
|
About the U-Boot policy
Hi all,
# Chris, I wanted to discuss about the U-Boot policy last night during the online meeting but somehow I missed the URL change.
We have had some discussions about U-boot for a while but I
Hi all,
# Chris, I wanted to discuss about the U-Boot policy last night during the online meeting but somehow I missed the URL change.
We have had some discussions about U-boot for a while but I
|
By
Daniel Sangorrin <daniel.sangorrin@...>
·
#358
·
|
|
Re: Project-X (minimal root filesystem) : rewrite and renesas iwg20m board support
Hi Jan,
By
Daniel Sangorrin <daniel.sangorrin@...>
·
#357
·
|
|
Re: Distribution of binaries: support to Renesas board in B@D
Hello Agustin,
As long as the binaries don't include Renesas' proprietary libraries for graphics or multimedia [1] we are happy for CIP to distribute them as per option 1) above.
For the Kernel,
Hello Agustin,
As long as the binaries don't include Renesas' proprietary libraries for graphics or multimedia [1] we are happy for CIP to distribute them as per option 1) above.
For the Kernel,
|
By
Chris Paterson
·
#356
·
|
|
Re: Renesas dev CIP repository announcement
Hello Yoshi-san,
Agreed. We intend to follow the proper process when backporting to the actual CIP Kernel.
The repository above is just a quick release to allow users to get the iWave RZ/G1M board
Hello Yoshi-san,
Agreed. We intend to follow the proper process when backporting to the actual CIP Kernel.
The repository above is just a quick release to allow users to get the iWave RZ/G1M board
|
By
Chris Paterson
·
#355
·
|
|
Re: Project-X (minimal root filesystem) for renesas board
I agree with you. But I have a consideration for current status for renesas-cip repository.
I think the current repository is under development. It looks Renesas's upstreaming effort for CIP. We can
I agree with you. But I have a consideration for current status for renesas-cip repository.
I think the current repository is under development. It looks Renesas's upstreaming effort for CIP. We can
|
By
Yoshitake Kobayashi
·
#354
·
|
|
Re: Renesas dev CIP repository announcement
Hi Chris and all,
I had looked the repository and have a suggestion.
When you backport patches from upstream, could you add the following line in commit message?
(cherry picked from commit
Hi Chris and all,
I had looked the repository and have a suggestion.
When you backport patches from upstream, could you add the following line in commit message?
(cherry picked from commit
|
By
Yoshitake Kobayashi
·
#353
·
|
|
Kernel maintenance and CIP testing report weeks 25 to 27
Hi,
Kernel maintenance
1. We have a new CIP kernel v4.4.75cip6 As anecdote, the kernel includes two patches that fix two regressions introduced by LTS patches. These fixes will be part of the next
Hi,
Kernel maintenance
1. We have a new CIP kernel v4.4.75cip6 As anecdote, the kernel includes two patches that fix two regressions introduced by LTS patches. These fixes will be part of the next
|
By
Agustin Benito Bethencourt <agustin.benito@...>
·
#352
·
|