I have created the UDS-session blueprints (blueprints to schedule the UDS sessions) as discussed in the meeting this morning. Take a look at the sessions specially the ownership and make sure you agree, you will have to run the session at UDS if you are the assignee (owner).
As it turned out, each major Technical Requirement will have one session, with the exception of k1 where k1.1 (fix arm/linus interface) will have 5 daily sessions. So, most of the sessions cover multiple topics, you may need have to co-ordinate with others to run your session.
https://wiki.linaro.org/WorkingGroups/Kernel/Cycle11.11SessionsSetup
Paul, you need to approve all these blueprints in order to start scheduling them.
Grant, You have registered sessions for boot architecture and DT, please send me the blueprints links so I can add them to this table.
Regards, Mounir
Mounir,
Would you mind re-naming:
linaro-kernel-o-android
to
linaro-android-kernel-o
Thanks!
-Zach
On 25 April 2011 15:24, Mounir Bsaibes mounir.bsaibes@linaro.org wrote:
I have created the UDS-session blueprints (blueprints to schedule the UDS sessions) as discussed in the meeting this morning. Take a look at the sessions specially the ownership and make sure you agree, you will have to run the session at UDS if you are the assignee (owner).
As it turned out, each major Technical Requirement will have one session, with the exception of k1 where k1.1 (fix arm/linus interface) will have 5 daily sessions. So, most of the sessions cover multiple topics, you may need have to co-ordinate with others to run your session.
https://wiki.linaro.org/WorkingGroups/Kernel/Cycle11.11SessionsSetup
Paul, you need to approve all these blueprints in order to start scheduling them.
Grant, You have registered sessions for boot architecture and DT, please send me the blueprints links so I can add them to this table.
Regards, Mounir
linaro-kernel mailing list linaro-kernel@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-kernel
Also,
Do you think a real-time session would be useful?
-Zach
On 26 April 2011 09:07, Zach Pfeffer zach.pfeffer@linaro.org wrote:
Mounir,
Would you mind re-naming:
linaro-kernel-o-android
to
linaro-android-kernel-o
Thanks!
-Zach
On 25 April 2011 15:24, Mounir Bsaibes mounir.bsaibes@linaro.org wrote:
I have created the UDS-session blueprints (blueprints to schedule the UDS sessions) as discussed in the meeting this morning. Take a look at the sessions specially the ownership and make sure you agree, you will have to run the session at UDS if you are the assignee (owner).
As it turned out, each major Technical Requirement will have one session, with the exception of k1 where k1.1 (fix arm/linus interface) will have 5 daily sessions. So, most of the sessions cover multiple topics, you may need have to co-ordinate with others to run your session.
https://wiki.linaro.org/WorkingGroups/Kernel/Cycle11.11SessionsSetup
Paul, you need to approve all these blueprints in order to start scheduling them.
Grant, You have registered sessions for boot architecture and DT, please send me the blueprints links so I can add them to this table.
Regards, Mounir
linaro-kernel mailing list linaro-kernel@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-kernel
On Tue, Apr 26, 2011 at 9:09 AM, Zach Pfeffer zach.pfeffer@linaro.orgwrote:
Also,
Do you think a real-time session would be useful?
I would defer this to Deepak, Do we have an owner that can lead the session? Mounir
-Zach
On 26 April 2011 09:07, Zach Pfeffer zach.pfeffer@linaro.org wrote:
Mounir,
Would you mind re-naming:
linaro-kernel-o-android
to
linaro-android-kernel-o
Thanks!
-Zach
On 25 April 2011 15:24, Mounir Bsaibes mounir.bsaibes@linaro.org
wrote:
I have created the UDS-session blueprints (blueprints to schedule the
UDS
sessions) as discussed in the meeting this morning. Take a look at the sessions specially the ownership and make sure you agree, you will have to run the session at UDS if you
are
the assignee (owner).
As it turned out, each major Technical Requirement will have one
session,
with the exception of k1 where k1.1 (fix arm/linus interface) will have 5 daily sessions. So,
most
of the sessions cover multiple topics, you may need have to co-ordinate with others to run
your
session.
https://wiki.linaro.org/WorkingGroups/Kernel/Cycle11.11SessionsSetup
Paul, you need to approve all these blueprints in order to start scheduling
them.
Grant, You have registered sessions for boot architecture and DT, please send
me
the blueprints links so I can add them to this table.
Regards, Mounir
linaro-kernel mailing list linaro-kernel@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-kernel
On Tue, Apr 26, 2011 at 9:07 AM, Zach Pfeffer zach.pfeffer@linaro.orgwrote:
Mounir,
Would you mind re-naming:
linaro-kernel-o-android
to
linaro-android-kernel-o
Zach, I thought the prefix is used to point to which track the session is under. Is there a track for linaro-android-kernel? In general this should be ok, but let see if that does not mess up any tool. Copying Jorge to see what he says.
Thanks!
-Zach
On 25 April 2011 15:24, Mounir Bsaibes mounir.bsaibes@linaro.org wrote:
I have created the UDS-session blueprints (blueprints to schedule the UDS sessions) as discussed in the meeting this morning. Take a look at the sessions specially the ownership and make sure you agree, you will have to run the session at UDS if you
are
the assignee (owner).
As it turned out, each major Technical Requirement will have one session, with the exception of k1 where k1.1 (fix arm/linus interface) will have 5 daily sessions. So,
most
of the sessions cover multiple topics, you may need have to co-ordinate with others to run
your
session.
https://wiki.linaro.org/WorkingGroups/Kernel/Cycle11.11SessionsSetup
Paul, you need to approve all these blueprints in order to start scheduling
them.
Grant, You have registered sessions for boot architecture and DT, please send me the blueprints links so I can add them to this table.
Regards, Mounir
linaro-kernel mailing list linaro-kernel@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-kernel
On Tue, Apr 26, 2011 at 10:27 AM, Mounir Bsaibes mounir.bsaibes@linaro.org wrote:
Zach, I thought the prefix is used to point to which track the session is under. Is there a track for linaro-android-kernel? In general this should be ok, but let see if that does not mess up any tool. Copying Jorge to see what he says.
It depends, we have both a kernel track and an android track. Is the session a linaro-kernel session that happens to be about android or a session in linaro-android that happens to be about the kernel? (Either way would work, I would name it based on which track would take ownership of the work.)
On Tue, Apr 26, 2011 at 9:32 AM, jorge.castro@gmail.com < jorge.castro@gmail.com> wrote:
On Tue, Apr 26, 2011 at 10:27 AM, Mounir Bsaibes mounir.bsaibes@linaro.org wrote:
Zach, I thought the prefix is used to point to which track the session is
under.
Is there a track for linaro-android-kernel? In general this should be ok, but let see if that does not mess up any
tool.
Copying Jorge to see what he says.
It depends, we have both a kernel track and an android track. Is the session a linaro-kernel session that happens to be about android or a session in linaro-android that happens to be about the kernel? (Either way would work, I would name it based on which track would take ownership of the work.)
can we use linaro-andorid-kernel as Zach suggesting? or we have to use either linaro-kernel or linaro-android? thanks, Mounir
On 04/26/2011 08:45 AM, Mounir Bsaibes wrote:
On Tue, Apr 26, 2011 at 9:32 AM, jorge.castro@gmail.com < jorge.castro@gmail.com> wrote:
On Tue, Apr 26, 2011 at 10:27 AM, Mounir Bsaibes mounir.bsaibes@linaro.org wrote:
Zach, I thought the prefix is used to point to which track the session is
under.
Is there a track for linaro-android-kernel? In general this should be ok, but let see if that does not mess up any
tool.
Copying Jorge to see what he says.
It depends, we have both a kernel track and an android track. Is the session a linaro-kernel session that happens to be about android or a session in linaro-android that happens to be about the kernel? (Either way would work, I would name it based on which track would take ownership of the work.)
can we use linaro-andorid-kernel as Zach suggesting? or we have to use either linaro-kernel or linaro-android?
Hi Mounir,
I could be mistaken and somebody correct me if I'm misinformed. I think the answer is no, the track shouldn't be named linaro-android-kernel-o-...
I'm getting my information from:
https://wiki.linaro.org/Internal/Events/2011-05-LDS/planning/UDSBP
Which says they have to follow this convention:
---- linaro-$trackname-o-$title
That means MOST specs for UDS-O should start with
linaro-android-o linaro-graphics-o linaro-kernel-o linaro-multimedia-o linaro-platforms-o linaro-power-management-o linaro-toolchain-o
If you have something that you can't classify in the above name-space, feel free to toss it in "linaro-other-o", though this should be rare. If you're naming convention is a mess and you haven't talked to Jorge or Joey, we will brutally rename things to make them fit in their neat little place, so if you have questions on naming just ping them. ----
I understood that the above naming convention was important for the schedule display system.
cheers, Matt
thanks, Mounir
linaro-kernel mailing list linaro-kernel@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-kernel
On Tue, Apr 26, 2011 at 10:47 AM, Matt Waddel matt.waddel@canonical.comwrote:
On 04/26/2011 08:45 AM, Mounir Bsaibes wrote:
On Tue, Apr 26, 2011 at 9:32 AM, jorge.castro@gmail.com < jorge.castro@gmail.com> wrote:
On Tue, Apr 26, 2011 at 10:27 AM, Mounir Bsaibes mounir.bsaibes@linaro.org wrote:
Zach, I thought the prefix is used to point to which track the session is
under.
Is there a track for linaro-android-kernel? In general this should be ok, but let see if that does not mess up any
tool.
Copying Jorge to see what he says.
It depends, we have both a kernel track and an android track. Is the session a linaro-kernel session that happens to be about android or a session in linaro-android that happens to be about the kernel? (Either way would work, I would name it based on which track would take ownership of the work.)
can we use linaro-andorid-kernel as Zach suggesting? or we have to use either linaro-kernel or linaro-android?
Hi Mounir,
I could be mistaken and somebody correct me if I'm misinformed. I think the answer is no, the track shouldn't be named linaro-android-kernel-o-...
I'm getting my information from:
https://wiki.linaro.org/Internal/Events/2011-05-LDS/planning/UDSBP
Which says they have to follow this convention:
linaro-$trackname-o-$title
That means MOST specs for UDS-O should start with
linaro-android-o linaro-graphics-o linaro-kernel-o linaro-multimedia-o linaro-platforms-o linaro-power-management-o linaro-toolchain-o
If you have something that you can't classify in the above name-space, feel free to toss it in "linaro-other-o", though this should be rare. If you're naming convention is a mess and you haven't talked to Jorge or Joey, we will brutally rename things to make them fit in their neat little place, so if you have questions on naming just ping them.
I understood that the above naming convention was important for the schedule display system.
Matt, I think you are right, that is why I raised the question. But Jorge said it is fine to use linaro-android-kernel-o ... I am not sure how to handle, really. Zach, how important it is to change the name? Thanks, Mounir
cheers, Matt
thanks, Mounir
linaro-kernel mailing list linaro-kernel@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-kernel
Matt, I think you are right, that is why I raised the question. But Jorge said it is fine to use linaro-android-kernel-o ... I am not sure how to handle, really. Zach, how important it is to change the name?
Alexander had suggested it to help group Android related things together so people would know at a glance what all the Android related sessions were. If the name can't change than that's okay.
I'd say leave it today.... linaro-android-kernel-o is a new track! I think it's best to do this:
linaro-android-o-kernel-$topic linaro-android-o-userspace-$topic
etc... just prefix the topic with the sub-track
On Wed, Apr 27, 2011 at 10:24 PM, Zach Pfeffer zach.pfeffer@linaro.org wrote:
Matt, I think you are right, that is why I raised the question. But Jorge said it is fine to use linaro-android-kernel-o ... I am not sure how to handle, really. Zach, how important it is to change the name?
Alexander had suggested it to help group Android related things together so people would know at a glance what all the Android related sessions were. If the name can't change than that's okay.
On Thu, Apr 28, 2011 at 3:42 PM, Joey Stanford joey.stanford@linaro.org wrote:
I'd say leave it today.... linaro-android-kernel-o is a new track! I think it's best to do this:
linaro-android-o-kernel-$topic linaro-android-o-userspace-$topic
etc... just prefix the topic with the sub-track
yes, keep the prefix fixed and just add your marks stuff afterwards!!
Thanks!
Hi Mounir,
Looking at the TRs...
K2.1-K2.4: Yes, should combine sessions. One session for K2.1, K2.3 & K2.4 (linaro-kernel-o-devicetree). A second session for K2.2 (linaro-kernel-o-devicetree-howto)
K3.2, K3.5, K3.6: discuss in linaro-kernel-o-bootarchitecture session K3.1: (as already indicated) linaro-kernel-o-uefi session K3.3: Not planning to schedule a session; this is a low priority. But if someone else wants to take it on then I support it K3.4: No session planned, the scope of this task is known and it will probably show up as a task in a blueprint for 11.11
K5.3: Should be discussed as part of linaro-kernel-o-uefi session?
g.
On Mon, Apr 25, 2011 at 2:24 PM, Mounir Bsaibes mounir.bsaibes@linaro.org wrote:
I have created the UDS-session blueprints (blueprints to schedule the UDS sessions) as discussed in the meeting this morning. Take a look at the sessions specially the ownership and make sure you agree, you will have to run the session at UDS if you are the assignee (owner).
As it turned out, each major Technical Requirement will have one session, with the exception of k1 where k1.1 (fix arm/linus interface) will have 5 daily sessions. So, most of the sessions cover multiple topics, you may need have to co-ordinate with others to run your session.
https://wiki.linaro.org/WorkingGroups/Kernel/Cycle11.11SessionsSetup
Paul, you need to approve all these blueprints in order to start scheduling them.
Grant, You have registered sessions for boot architecture and DT, please send me the blueprints links so I can add them to this table.
Regards, Mounir
linaro-kernel mailing list linaro-kernel@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-kernel
K2.1-K2.4: Yes, should combine sessions. One session for K2.1, K2.3 & K2.4 (linaro-kernel-o-devicetree). A second session for K2.2 (linaro-kernel-o-devicetree-howto)
I've got an Android flavored version of linaro-kernel-o-devicetree:
https://blueprints.launchpad.net/linaro-android/+spec/linaro-android-o-platf...
Would you like to cover Android in linaro-kernel-o-devicetree?
K3.2, K3.5, K3.6: discuss in linaro-kernel-o-bootarchitecture session
I've got a couple of boot sessions:
https://blueprints.launchpad.net/linaro-android/+spec/linaro-android-o-fastb... https://blueprints.launchpad.net/linaro-android/+spec/linaro-android-o-multi...
Would you like to combine these into linaro-kernel-o-bootarchitecture?
On Sun, May 1, 2011 at 12:24 PM, Zach Pfeffer zach.pfeffer@linaro.org wrote:
K2.1-K2.4: Yes, should combine sessions. One session for K2.1, K2.3 & K2.4 (linaro-kernel-o-devicetree). A second session for K2.2 (linaro-kernel-o-devicetree-howto)
I've got an Android flavored version of linaro-kernel-o-devicetree:
https://blueprints.launchpad.net/linaro-android/+spec/linaro-android-o-platf...
Would you like to cover Android in linaro-kernel-o-devicetree?
Yes
K3.2, K3.5, K3.6: discuss in linaro-kernel-o-bootarchitecture session
I've got a couple of boot sessions:
https://blueprints.launchpad.net/linaro-android/+spec/linaro-android-o-fastb... https://blueprints.launchpad.net/linaro-android/+spec/linaro-android-o-multi...
Would you like to combine these into linaro-kernel-o-bootarchitecture?
Yes, with the option of scheduling a follow-on session if there ends up being too much to discuss.
Okay. I'll mark these superseded and register for them.
On 1 May 2011 13:29, Grant Likely grant.likely@secretlab.ca wrote:
On Sun, May 1, 2011 at 12:24 PM, Zach Pfeffer zach.pfeffer@linaro.org wrote:
K2.1-K2.4: Yes, should combine sessions. One session for K2.1, K2.3 & K2.4 (linaro-kernel-o-devicetree). A second session for K2.2 (linaro-kernel-o-devicetree-howto)
I've got an Android flavored version of linaro-kernel-o-devicetree:
https://blueprints.launchpad.net/linaro-android/+spec/linaro-android-o-platf...
Would you like to cover Android in linaro-kernel-o-devicetree?
Yes
K3.2, K3.5, K3.6: discuss in linaro-kernel-o-bootarchitecture session
I've got a couple of boot sessions:
https://blueprints.launchpad.net/linaro-android/+spec/linaro-android-o-fastb... https://blueprints.launchpad.net/linaro-android/+spec/linaro-android-o-multi...
Would you like to combine these into linaro-kernel-o-bootarchitecture?
Yes, with the option of scheduling a follow-on session if there ends up being too much to discuss.
-- Grant Likely, B.Sc., P.Eng. Secret Lab Technologies Ltd.
Hi Mounir,
K7 Improve Linux Kernel Storage Performance
This session covers 11 sub items. Some of the items are really small other low prio, and some big like "K7.1 flash remapping". The session is schedule for 1 hour I presume. It is difficult to estimate the time needed each subject. I think 2 hours would be sufficient for all. Could this be one 2 hours session rather than two 1 hour session?
K7.2 Optimize Kernel/User Buffer Handling Low K7.5 Implement eMMC High Priority Interrupt Low K7.7 SDIO Cache Management TBD These above are low prio and have no drafter. I can add just empty blueprints for these just to be a place holder for any comments and feedback from the session. Since they are low prio they most likely want be done in 11.11.
K7.8 SDXC Controller Support medium K7.9 eSATA Support medium K7.11 USB Mass Storage medium There are no assignee/drafter for these, and the prio is medium. I can prepare a basic blueprint for k7.11 and k7.8 (if here is no one else) but I prefer to not be the assignee. K7.9 is an unknown subject to me. Can anyone fill in on this one? Otherwise I add an empty blueprint for this one as well.
Regards, Per
On 25 April 2011 22:24, Mounir Bsaibes mounir.bsaibes@linaro.org wrote:
I have created the UDS-session blueprints (blueprints to schedule the UDS sessions) as discussed in the meeting this morning. Take a look at the sessions specially the ownership and make sure you agree, you will have to run the session at UDS if you are the assignee (owner).
As it turned out, each major Technical Requirement will have one session, with the exception of k1 where k1.1 (fix arm/linus interface) will have 5 daily sessions. So, most of the sessions cover multiple topics, you may need have to co-ordinate with others to run your session.
https://wiki.linaro.org/WorkingGroups/Kernel/Cycle11.11SessionsSetup
Paul, you need to approve all these blueprints in order to start scheduling them.
Grant, You have registered sessions for boot architecture and DT, please send me the blueprints links so I can add them to this table.
Regards, Mounir
linaro-kernel mailing list linaro-kernel@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-kernel
K7 Improve Linux Kernel Storage Performance
Based on the discussion during the kernel meeting I propose the following changes. Remove: K7.2 - Optimize Kernel/User Buffer Handling K7.5 - Implement eMMC High Priority Interrupt K7.7 - SDIO Cache Management K7.8 - SDXC Controller Support K7.9 - eSATA Support
/Per
On 2 May 2011 11:20, Per Forlin per.forlin@linaro.org wrote:
Hi Mounir,
K7 Improve Linux Kernel Storage Performance
This session covers 11 sub items. Some of the items are really small other low prio, and some big like "K7.1 flash remapping". The session is schedule for 1 hour I presume. It is difficult to estimate the time needed each subject. I think 2 hours would be sufficient for all. Could this be one 2 hours session rather than two 1 hour session?
K7.2 Optimize Kernel/User Buffer Handling Low K7.5 Implement eMMC High Priority Interrupt Low K7.7 SDIO Cache Management TBD These above are low prio and have no drafter. I can add just empty blueprints for these just to be a place holder for any comments and feedback from the session. Since they are low prio they most likely want be done in 11.11.
K7.8 SDXC Controller Support medium K7.9 eSATA Support medium K7.11 USB Mass Storage medium There are no assignee/drafter for these, and the prio is medium. I can prepare a basic blueprint for k7.11 and k7.8 (if here is no one else) but I prefer to not be the assignee. K7.9 is an unknown subject to me. Can anyone fill in on this one? Otherwise I add an empty blueprint for this one as well.
Regards, Per
On 25 April 2011 22:24, Mounir Bsaibes mounir.bsaibes@linaro.org wrote:
I have created the UDS-session blueprints (blueprints to schedule the UDS sessions) as discussed in the meeting this morning. Take a look at the sessions specially the ownership and make sure you agree, you will have to run the session at UDS if you are the assignee (owner).
As it turned out, each major Technical Requirement will have one session, with the exception of k1 where k1.1 (fix arm/linus interface) will have 5 daily sessions. So, most of the sessions cover multiple topics, you may need have to co-ordinate with others to run your session.
https://wiki.linaro.org/WorkingGroups/Kernel/Cycle11.11SessionsSetup
Paul, you need to approve all these blueprints in order to start scheduling them.
Grant, You have registered sessions for boot architecture and DT, please send me the blueprints links so I can add them to this table.
Regards, Mounir
linaro-kernel mailing list linaro-kernel@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-kernel
On Mon, May 2, 2011 at 11:35 AM, Per Forlin per.forlin@linaro.org wrote:
K7 Improve Linux Kernel Storage Performance
Based on the discussion during the kernel meeting I propose the following changes. Remove: K7.2 - Optimize Kernel/User Buffer Handling K7.5 - Implement eMMC High Priority Interrupt K7.7 - SDIO Cache Management K7.8 - SDXC Controller Support K7.9 - eSATA Support
With this we are left with K7.11 Separate data/control USB buffering, optimize USB buffer types to find a drafter for Mounir
/Per
On 2 May 2011 11:20, Per Forlin per.forlin@linaro.org wrote:
Hi Mounir,
K7 Improve Linux Kernel Storage Performance
This session covers 11 sub items. Some of the items are really small other low prio, and some big like "K7.1 flash remapping". The session is schedule for 1 hour I presume. It is difficult to estimate the time needed each subject. I think 2 hours would be sufficient for all. Could this be one 2 hours session rather than two 1 hour session?
K7.2 Optimize Kernel/User Buffer Handling Low K7.5 Implement eMMC High Priority Interrupt Low K7.7 SDIO Cache Management TBD These above are low prio and have no drafter. I can add just empty blueprints for these just to be a place holder for any comments and feedback from the session. Since they are low prio they most likely want be done in 11.11.
K7.8 SDXC Controller Support medium K7.9 eSATA Support medium K7.11 USB Mass Storage medium There are no assignee/drafter for these, and the prio is medium. I can prepare a basic blueprint for k7.11 and k7.8 (if here is no one else) but I prefer to not be the assignee. K7.9 is an unknown subject to me. Can anyone fill in on this one? Otherwise I add an empty blueprint for this one as well.
Regards, Per
On 25 April 2011 22:24, Mounir Bsaibes mounir.bsaibes@linaro.org
wrote:
I have created the UDS-session blueprints (blueprints to schedule the
UDS
sessions) as discussed in the meeting this morning. Take a look at the sessions specially the ownership and make sure you agree, you will have to run the session at UDS if you
are
the assignee (owner).
As it turned out, each major Technical Requirement will have one
session,
with the exception of k1 where k1.1 (fix arm/linus interface) will have 5 daily sessions. So,
most
of the sessions cover multiple topics, you may need have to co-ordinate with others to run
your
session.
https://wiki.linaro.org/WorkingGroups/Kernel/Cycle11.11SessionsSetup
Paul, you need to approve all these blueprints in order to start scheduling
them.
Grant, You have registered sessions for boot architecture and DT, please send
me
the blueprints links so I can add them to this table.
Regards, Mounir
linaro-kernel mailing list linaro-kernel@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-kernel
linaro-kernel@lists.linaro.org
-
Alexander Sack -
Grant Likely -
Joey Stanford -
jorge.castro＠gmail.com -
Matt Waddel -
Mounir Bsaibes -
Per Forlin -
Zach Pfeffer