[yocto] [meta-realtime][PATCH] add sched_deadline reckpies-kernel for 3.8 kernel

Bruce Ashfield bruce.ashfield at windriver.com
Thu Mar 14 23:44:35 PDT 2013


On 13-03-14 11:36 PM, Insop Song wrote:
> On Thu, Mar 14, 2013 at 11:13 PM, Bruce Ashfield
> <bruce.ashfield at gmail.com> wrote:
>
>
>>
>> Hmm. One of the arbiters is me .. if it doesn't work this time, let me know
>> and I'll check the list membership.
>
> I've just signed up and got a confirmation email.
>
>
>>>
>>> I was do some testing on "make localmodconfig", which will gets me the
>>> using module build .config.
>>> So let me me ask you this before I send out an updated patch.
>>>
>>> I ran "lsmod > /tmp/lsmod" on my qemux86
>>> On dev host, run "make LSMOD=/tmp/lsmod localmodconfig" to get this
>>> localmodconfig_qemux86.cfg file, which has less module configurations.
>>>
>>> Then I use this in bbappend file like below:
>>>
>>> ---
>>> SRC_URI = "git://git.yoctoproject.org/linux-yocto-3.8.git;protocol=git;bareclone=1;branch=${KBRANCH},${KMETA};name=machine,meta
>>> \
>>>          file://localmodconfig_qemux86.cfg \
>>>          "
>>> ----
>>>
>>> what do you think?
>>
>> We want to track the modules and policies of the main qemu BSP,
>> not override them all here. Extra layers should be only changing board
>> functionality that is specific to their functionality, not the base board
>> configuration.
>>
>> If you think there are modules that are enabled that shouldn't be, we
>> can address that by looking at the base policy and deciding if that
>> base policy is wrong.
>>
>> Cheers,
>>
>
> I see, let me follow up the current patch update and do some more look
> on qemu bsp and deal with a separate patch.
>
> Here are the update patches 2/2.
>
> And let me know if you want to see in different ways of patch
> delivery? since, I haven't set up my gmail smtp set up yet (due to
> application specific athentication), so I manually copy and paste and
> attach the files.

Are you trying to send via git send-email ? The following is the
way that I'd relay through gmail:

   > git send-email --smtp-server smtp.gmail.com --smtp-user 
bruce.ashfield at gmail.com --smtp-pass <paswd> --smtp-ssl ~/rr/

And to generate the patches and introductory email, look at
the oe-core scripts/create-pull-request.

That's the best and easiest way to send patches.

> ------
>
>
> Subject: [meta-realtime][PATCH 2/2] remove edf.cfg and follow up review
>   feedback
>
> ---
>   recipes-kernel/linux/linux-yocto/edf.cfg      |    4 ----
>   recipes-kernel/linux/linux-yocto_3.8.bbappend |    5 -----
>   2 files changed, 9 deletions(-)
>   delete mode 100644 recipes-kernel/linux/linux-yocto/edf.cfg

This looks good. I'll stage it locally and do a quick test build.

Cheers,

Bruce

>
> diff --git a/recipes-kernel/linux/linux-yocto/edf.cfg
> b/recipes-kernel/linux/linux-yocto/edf.cfg
> deleted file mode 100644
> index ccf004f..0000000
> --- a/recipes-kernel/linux/linux-yocto/edf.cfg
> +++ /dev/null
> @@ -1,4 +0,0 @@
> -CONFIG_CGROUPS=y
> -CONFIG_CGROUP_SCHED=y
> -CONFIG_DEADLINE_GROUP_SCHED=y
> -
> diff --git a/recipes-kernel/linux/linux-yocto_3.8.bbappend
> b/recipes-kernel/linux/linux-yocto_3.8.bbappend
> index c6a969f..175ab91 100644
> --- a/recipes-kernel/linux/linux-yocto_3.8.bbappend
> +++ b/recipes-kernel/linux/linux-yocto_3.8.bbappend
> @@ -1,13 +1,8 @@
>   FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}:"
> -COMPATIBLE_MACHINE_qemux86 = "qemux86"
> -COMPATIBLE_MACHINE_fri2 = "fri2"
>
>   KBRANCH_qemux86 = "standard/edf"
>   KBRANCH_fri2 = "standard/edf"
>
> -KMACHINE_qemux86 = "qemux86"
> -KMACHINE_fri2 = "fri2"
> -
>   SRCREV_machine_qemux86 = "62d98f6b12f91cc7419b88dfa2e0abe077c94f9f"
>   SRCREV_machine_fri2 = "62d98f6b12f91cc7419b88dfa2e0abe077c94f9f"
>
>
>
> _______________________________________________
> yocto mailing list
> yocto at yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
>




More information about the yocto mailing list