|
Added some basic content to the wiki
Hi,
in preparation to start reporting about the testing efforts, I have added some content to the wiki to provide context. Please let me know if there is anything wrong or that might be
Hi,
in preparation to start reporting about the testing efforts, I have added some content to the wiki to provide context. Please let me know if there is anything wrong or that might be
|
By
Agustin Benito Bethencourt <agustin.benito@...>
·
#62
·
|
|
Re: Maintenance policies and early considerations IV
Hi,
(2016/09/27 17:29), Agustin Benito Bethencourt wrote:
We (our company members) agree.
We think CIP doesn't need to kepp the kernel API/ABI.
Best regards,
Hidehiro Kawai
Hitachi, Ltd. Research
Hi,
(2016/09/27 17:29), Agustin Benito Bethencourt wrote:
We (our company members) agree.
We think CIP doesn't need to kepp the kernel API/ABI.
Best regards,
Hidehiro Kawai
Hitachi, Ltd. Research
|
By
Hidehiro Kawai
·
#61
·
|
|
Re: Maintenance policies and early considerations III
Hi,
(2016/09/22 21:56), Agustin Benito Bethencourt wrote:
I agree on that. CIP don't need to care about out-of-tree drivers.
I think it is important to prepare for zero-day attacks, and the
Hi,
(2016/09/22 21:56), Agustin Benito Bethencourt wrote:
I agree on that. CIP don't need to care about out-of-tree drivers.
I think it is important to prepare for zero-day attacks, and the
|
By
Hidehiro Kawai
·
#60
·
|
|
Re: Maintenance policies and early considerations II
Hi,
(2016/09/22 18:42), Agustin Benito Bethencourt wrote:
Basically, releasing the kernel as source is sufficient. But if we
release it as binary only for the specific reference board, users may be
Hi,
(2016/09/22 18:42), Agustin Benito Bethencourt wrote:
Basically, releasing the kernel as source is sufficient. But if we
release it as binary only for the specific reference board, users may be
|
By
Hidehiro Kawai
·
#59
·
|
|
Re: Maintenance policies and early considerations I
Hi,
I'm sorry for the late response.
(2016/09/22 18:31), Agustin Benito Bethencourt wrote:
Assuming we release new products in every 2 years, 2-3-year release
cycle would be feasible.
Maintaining
Hi,
I'm sorry for the late response.
(2016/09/22 18:31), Agustin Benito Bethencourt wrote:
Assuming we release new products in every 2 years, 2-3-year release
cycle would be feasible.
Maintaining
|
By
Hidehiro Kawai
·
#58
·
|
|
Re: Maintenance policies and early considerations IV
Nit: it's stable_kernel_rules.txt. We should start this way and
augment/adjust rules after discussions as we find potential conflicts.
Sounds reasonable to me in general.
Jan
--
Siemens
Nit: it's stable_kernel_rules.txt. We should start this way and
augment/adjust rules after discussions as we find potential conflicts.
Sounds reasonable to me in general.
Jan
--
Siemens
|
By
Jan Kiszka
·
#57
·
|
|
Re: Maintenance policies and early considerations II
Ack.
Not sure how to read these threads as I didn't manage to follow their
evolution: This aspect of support constraints is still in scope? I think
it will be important in order to keep backporting
Ack.
Not sure how to read these threads as I didn't manage to follow their
evolution: This aspect of support constraints is still in scope? I think
it will be important in order to keep backporting
|
By
Jan Kiszka
·
#56
·
|
|
First CIP kernel will be 4.4
Hi,
At LinuxCon EU, during the CIP talk it was announced that the first CIP kernel will be 4.4
Please find the slides of all the 2016 talks about CIP in our wiki[1].
[1]
Hi,
At LinuxCon EU, during the CIP talk it was announced that the first CIP kernel will be 4.4
Please find the slides of all the 2016 talks about CIP in our wiki[1].
[1]
|
By
Agustin Benito Bethencourt <agustin.benito@...>
·
#55
·
|
|
ELCE talk about embedded systems long term maintenance
Hi,
the slides[1] from the talk "Long-Term Maintenance, or how to (mis-)manage embedded systems for 10+ years" by Jan Luebbe are available.
I assume by next week we will have the video.
[1]
Hi,
the slides[1] from the talk "Long-Term Maintenance, or how to (mis-)manage embedded systems for 10+ years" by Jan Luebbe are available.
I assume by next week we will have the video.
[1]
|
By
Agustin Benito Bethencourt <agustin.benito@...>
·
#54
·
|
|
Re: Maintenance policies and early considerations IV
The first version is what I wrote, and the correction says something I
did not mean to say.
No, you understand me rightly.
Ben.
--
Ben Hutchings
Software Developer, Codethink Ltd.
The first version is what I wrote, and the correction says something I
did not mean to say.
No, you understand me rightly.
Ben.
--
Ben Hutchings
Software Developer, Codethink Ltd.
|
By
Ben Hutchings <ben.hutchings@...>
·
#53
·
|
|
Re: Maintenance policies and early considerations IV
Hi Koguchi-san,
I think you are right. It's my fault, sorry.
Daniel
Hi Koguchi-san,
I think you are right. It's my fault, sorry.
Daniel
|
By
Daniel Sangorrin <daniel.sangorrin@...>
·
#52
·
|
|
Re: Maintenance policies and early considerations IV
Hi Agustin,
Let me understand what you wrote.
Is the correction correct?
I thought you wrote;
* Upstream fixes frequently change the kernel module API and/or ABI and
backporting them in a way that
Hi Agustin,
Let me understand what you wrote.
Is the correction correct?
I thought you wrote;
* Upstream fixes frequently change the kernel module API and/or ABI and
backporting them in a way that
|
By
Takuo Koguchi
·
#51
·
|
|
Re: Public wiki
Hi,
I think it is already there.
Sent from mobile. Please excuse my brevity.
--
Agustín Benito Bethencourt
@toscalix
Hi,
I think it is already there.
Sent from mobile. Please excuse my brevity.
--
Agustín Benito Bethencourt
@toscalix
|
By
Agustín Benito Bethencourt <agustin.benito@...>
·
#50
·
|
|
Re: Public wiki
Hi Agustin,
Here are some links for CIP presentations. Probably the following information is also a candidate contents for CIP wiki.
* Towards Sustainable Systems with the Civil Infrastructure
Hi Agustin,
Here are some links for CIP presentations. Probably the following information is also a candidate contents for CIP wiki.
* Towards Sustainable Systems with the Civil Infrastructure
|
By
Yoshitake Kobayashi
·
#49
·
|
|
Re: Public wiki
Just a remark, the presentation is tomorrow, 10/6
--
Urs Gleim | Siemens AG | Corporate Technology
Just a remark, the presentation is tomorrow, 10/6
--
Urs Gleim | Siemens AG | Corporate Technology
|
By
Urs Gleim
·
#48
·
|
|
Public wiki
Hi,
CIP ha set up a public wiki. It has very little content at this point and there is no policy yet to add editors. We are sorting things
Hi,
CIP ha set up a public wiki. It has very little content at this point and there is no policy yet to add editors. We are sorting things
|
By
Agustin Benito Bethencourt <agustin.benito@...>
·
#47
·
|
|
Re: Maintenance policies and early considerations III
Hi Agustin,
Sorry for the late reply.
I think that one possible guideline for backporting security patches to the CIP kernel
is to look at kernel CVEs [1]. A table (probably only accessible by
Hi Agustin,
Sorry for the late reply.
I think that one possible guideline for backporting security patches to the CIP kernel
is to look at kernel CVEs [1]. A table (probably only accessible by
|
By
Daniel Sangorrin <daniel.sangorrin@...>
·
#46
·
|
|
Re: Maintenance policies and early considerations IV
Hi,
Correction:
Upstream fixes frequently change the kernel module API and/or ABI and backporting them in a way that is difficult and risky - CIP users set their own kernel configurations, so
Hi,
Correction:
Upstream fixes frequently change the kernel module API and/or ABI and backporting them in a way that is difficult and risky - CIP users set their own kernel configurations, so
|
By
Agustin Benito Bethencourt <agustin.benito@...>
·
#45
·
|
|
Re: New IRC channel for
#cip
This is a problem for many companies, actually, but I hope we can still encourage people to participate in IRC, mainly because there are so many established FOSS projects and contributors actively
This is a problem for many companies, actually, but I hope we can still encourage people to participate in IRC, mainly because there are so many established FOSS projects and contributors actively
|
By
Paul Sherwood
·
#44
·
|
|
Re: cip-dev Digest, Vol 4, Issue 14: IRC not Practical
Hi Everyone,
#Alternatives to a Mailing List
Slack has been taking the business world by storm, however, The free version has some serious limitations on it. So I started looking for Slack
Hi Everyone,
#Alternatives to a Mailing List
Slack has been taking the business world by storm, however, The free version has some serious limitations on it. So I started looking for Slack
|
By
Don Brown <don.f.brown@...>
·
#43
·
|