IRC logs for #cip for Thursday, 2017-03-16

*** bananadev has joined #cip03:07
donbrowntoscalix: diagram created and emailed - please let me know your feedback03:17
*** bananadev has quit IRC05:11
*** bananadev has joined #cip05:14
*** rajm has joined #cip08:12
*** toscalix has joined #cip08:42
patersoncMornin everyone08:49
patersoncWhat version of u-boot is currently being used with the BBB?08:51
toscalixrajm: ?09:04
* rajm inspects09:05
rajmpatersonc I get U-Boot SPL 2014.04-00014-g47880f509:10
patersoncrajm: Thanks. Is this what came with the board? Or have you updated?09:41
rajmit came with the board09:42
patersoncOkay. Is this the same case for everyone using BBB? Should everyone be making sure we're using the same version for the CIP testing/verification?09:44
rajmgood question - donbrown ?09:48
toscalixpatersonc: since we will have different platforms for testing purposes, we will need to separate what is "SLTS" and what is is not but agreed for testing the platform09:50
toscalixsorry, testing with the platfomr09:50
toscalixplatform09:50
toscalixI assume renesas will use a different U-Boot version09:51
toscalixwe will need to agree on a version to support but I see us using others for testing on the platform. Otherwise we will need to assume a "one system fits all platforms" which is not realistic today09:53
patersoncI agree, and this is why I'm starting the conversation.09:53
patersoncRenesas are indeed using a different version, I'm trying to decide if we should try and upstream support for our board, or just continue using our version.09:54
patersoncI suspect that each vendor will likely just want to use their own (tested) version of u-boot.09:54
patersoncUpstream support in u-boot seems limited.09:54
toscalixIt would make our life easier if it is upstreammed. But we need to assume the limitations09:55
toscalixFor the kernel we have defined Black&white policies, but for other components the situation is not that easy09:56
toscalixwe will need to "adapt" knowing that "upstream first" is a strong policy09:56
patersoncIndeed09:57
patersoncTaking the u-boot case for an example, it seems that the peer-review process isn't as strong as the Kernel, and often patches are accepted that may brake support for legacy devices09:58
patersonc(So I've been told)09:58
toscalixthat is my understanding09:59
toscalixsome projects maintain a u-boot version with limited functionality as the minimum common denominator09:59
patersoncSo perhaps CIP could pick a particular version of u-boot (per CIP Kernel version?), and use that for all of their testing/verification on the project's reference platforms?10:01
toscalixthat would be ideal10:01
toscalixif we can do that....10:01
toscalixright now we have two platforms BBB and renesas, right? If we can use one for both....great10:02
patersoncIt would make the most sense to me, but getting to that common version could be difficult.10:02
toscalixagree10:02
patersoncI think the version on the Renesas board is 2013.01.01 at the moment10:03
toscalixThis is the kind of topic I would like to see in the cip-dev ML I need to investigate a little both versions and the state of them upstream10:05
toscalixI would also like to hear the consumers (Siemens, Toshiba and Hitachi)10:05
toscalixand also U-Boot maintainers10:05
patersoncYep. I'll put some comments into an email on cip-dev. Perhaps we can also discuss in next week's call?10:07
toscalixagree10:16
toscalixI will answer your mail with some links10:35
patersoncThanks10:36
*** kristerman has joined #cip11:08
*** bananadev has quit IRC11:26
patersonctoscalix: Hopefully my ramblings on cip-dev make some sort of sense!12:15
toscalixit does13:17
toscalixpatersonc: I need to think a little my answer. I will do it tomorrow14:16
patersonctoscalix: No rush. Thanks!14:16
*** rajm has quit IRC16:41
*** kristerman has quit IRC18:05
*** CTtpollard has quit IRC18:19
*** toscalix has quit IRC18:34
*** toscalix_ has joined #cip20:29
*** toscalix_ has quit IRC20:30

Generated by irclog2html.py 2.15.3 by Marius Gedminas - find it at mg.pov.lt!