{"action":"created","issue":{"url":"https://api.github.com/repos/ARM-software/tf-issues/issues/588","repository_url":"https://api.github.com/repos/ARM-software/tf-issues","labels_url":"https://api.github.com/repos/ARM-software/tf-issues/issues/588/labels{/name}","comments_url":"https://api.github.com/repos/ARM-software/tf-issues/issues/588/comments","events_url":"https://api.github.com/repos/ARM-software/tf-issues/issues/588/events","html_url":"https://github.com/ARM-software/tf-issues/issues/588","id":324399888,"node_id":"MDU6SXNzdWUzMjQzOTk4ODg=","number":588,"title":"Add support for Renesas R-Car Gen3 SoCs","user":{"login":"fisaksen","id":17474434,"node_id":"MDQ6VXNlcjE3NDc0NDM0","avatar_url":"https://avatars0.githubusercontent.com/u/17474434?v=4","gravatar_id":"","url":"https://api.github.com/users/fisaksen","html_url":"https://github.com/fisaksen","followers_url":"https://api.github.com/users/fisaksen/followers","following_url":"https://api.github.com/users/fisaksen/following{/other_user}","gists_url":"https://api.github.com/users/fisaksen/gists{/gist_id}","starred_url":"https://api.github.com/users/fisaksen/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/fisaksen/subscriptions","organizations_url":"https://api.github.com/users/fisaksen/orgs","repos_url":"https://api.github.com/users/fisaksen/repos","events_url":"https://api.github.com/users/fisaksen/events{/privacy}","received_events_url":"https://api.github.com/users/fisaksen/received_events","type":"User","site_admin":false},"labels":[{"id":74922112,"node_id":"MDU6TGFiZWw3NDkyMjExMg==","url":"https://api.github.com/repos/ARM-software/tf-issues/labels/enhancement","name":"enhancement","color":"84b6eb","default":true}],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":11,"created_at":"2018-05-18T12:55:45Z","updated_at":"2018-07-26T17:32:20Z","closed_at":null,"author_association":"NONE","body":"Add arm-trusted-firmware Renesas Gen3 R-Car family of automotive embedded SoCs. See https://elinux.org/R-Car for details.\r\nThe current arm-trusted-firmare can be found here: \r\n- https://github.com/renesas-rcar/arm-trusted-firmware\r\n- https://github.com/renesas-rcar/optee_os"},"comment":{"url":"https://api.github.com/repos/ARM-software/tf-issues/issues/comments/408174499","html_url":"https://github.com/ARM-software/tf-issues/issues/588#issuecomment-408174499","issue_url":"https://api.github.com/repos/ARM-software/tf-issues/issues/588","id":408174499,"node_id":"MDEyOklzc3VlQ29tbWVudDQwODE3NDQ5OQ==","user":{"login":"danh-arm","id":5684642,"node_id":"MDQ6VXNlcjU2ODQ2NDI=","avatar_url":"https://avatars0.githubusercontent.com/u/5684642?v=4","gravatar_id":"","url":"https://api.github.com/users/danh-arm","html_url":"https://github.com/danh-arm","followers_url":"https://api.github.com/users/danh-arm/followers","following_url":"https://api.github.com/users/danh-arm/following{/other_user}","gists_url":"https://api.github.com/users/danh-arm/gists{/gist_id}","starred_url":"https://api.github.com/users/danh-arm/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/danh-arm/subscriptions","organizations_url":"https://api.github.com/users/danh-arm/orgs","repos_url":"https://api.github.com/users/danh-arm/repos","events_url":"https://api.github.com/users/danh-arm/events{/privacy}","received_events_url":"https://api.github.com/users/danh-arm/received_events","type":"User","site_admin":false},"created_at":"2018-07-26T17:32:20Z","updated_at":"2018-07-26T17:32:20Z","author_association":"CONTRIBUTOR","body":"Hi @ldts\r\n\r\n> yes I do have permission\r\n\r\nOK, good.\r\n\r\n> it would be very helpful to have some forum where some of the design decisions can be discussed early rather than late...\r\n\r\nAs Soby said, it's difficult for Arm to set up an IRC channel but this might be easier after the transition to trusted-firmware.org. However, it's possible to have a conference call to discuss this kind of thing. This can be arranged by email.\r\n\r\n> for instance renesas's ATF does not implement a BL1 but instead performs the EL3 to EL1 transition as the BL2 entry point before continuing with BL2\r\n\r\nIt sounds like the Renesas proprietary Boot ROM expects the next firmware to execute at EL3, and they've created a platform specific solution for this. The latest upstream code has the `BL2_AT_EL3` feature, which should mean the Renesas solution is unnecessary. Search for this in the code and see what you think.\r\n\r\n> ... is BL1 implementation mandatory for aarch64\r\n\r\nNo, we expect some vendors to have their own proprietary Boot ROM (although we'd like them to migrate to TF-A BL1). We have to support existing devices out there.\r\n"}}
{"actor":{"display_login":"danh-arm"}}