ter installing on Linux, launch the "MonoTool GUI Server" from the
application menu to start the server.
I tried clicking on the above link in Medora and it just hangs. Is your
version
of Monotools-server available somewhere? I would greatly appreciate any help
you can offer. Thanks,
Bruce
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
/2012-July/026938.html
These may already be coordinated, but I do see some common threads and
it would be nice to make sure everything will work together and that we
aren't duplicating effort!
Cheers,
Bruce
2) Binary package pool can be a minimal/partial sstate-cache, as complete
sstate-cac
On 12-11-21 11:29 AM, Venkata ramana gollamudi wrote:
Reply inline
-Original Message-
From: Bruce Ashfield [mailto:bruce.ashfi...@windriver.com]
Sent: Tuesday, November 20, 2012 8:53 PM
To: Venkata ramana gollamudi
Cc: yocto@yoctoproject.org; Sanil kumar; Hatle, Mark
Subject: Re
o-3.4/tree/meta/cfg/kernel-cache/bsp/beagleboard/beagleboard-preempt-rt.scc?h=meta
And when you build the linux-yocto-rt kernel with that board, that
description should be found, and it enables all the base options already.
If you look in your build, what does the file 'linux/meta/top_tgt'
On 12-11-28 01:07 AM, Yu Pan wrote:
Hi Bruce,
Thanks for commenting :-)
You shouldn't have needed to do this part, since the board already has
a preempt-rt BSP description:
http://git.yoctoproject.org/__cgit/cgit.cgi/linux-yocto-3.4/__tree/meta/cfg/kernel-cache/__bsp/beagle
On 12-11-28 01:07 AM, Yu Pan wrote:
Hi Bruce,
Thanks for commenting :-)
You shouldn't have needed to do this part, since the board already has
a preempt-rt BSP description:
http://git.yoctoproject.org/__cgit/cgit.cgi/linux-yocto-3.4/__tree/meta/cfg/kernel-cache/__bsp/beagle
rip -s -R .comment vmlinux-foo.bin
and also for the record, we have this logged in bug 3515, and we'll
make this the default for the build.
Cheers,
Bruce
Kinds regards, Lisandro.
___
yocto mailing list
yocto@yoctopr
ngeley, etc),
so this makes me think that the difference really is only 32 vs 64 bit.
Cheers,
Bruce
___
linux-yocto mailing list
linux-yo...@yoctoproject.org
https://lists.yoctoproject.org/listinfo/linux-yocto
parts organized is taking a bit longer than expected
or than we would like.
Cheers,
Bruce
Also, try to ensure that you don't put both the meta-layers in your
bblayers.conf file
while building, and ensure that you set machine as follows in your local.conf
file
MACHINE ?= "zynq-zc702&
RI directly can also help here, and I've already had this
in consideration for 1.4.
Cheers,
Bruce
> > My SRCREV is set to "AUTOREV", in which case bitbake prints the
SHA1
> > corresponding to the branch parameter in the git fetcher -
extremely
On 12-12-05 01:15 PM, Philip Balister wrote:
On 12/05/2012 06:46 AM, Bruce Ashfield wrote:
On 12-12-05 09:42 AM, Elvis Dowson wrote:
Hi,
On Dec 5, 2012, at 5:21 PM, Andreas Schweigstill
wrote:
I have also tried to build a kernel and root filesystem for Zynq but
the kernel
gets stuck when
On 12-12-04 01:11 PM, kishore.k.bo...@intel.com wrote:
From: Kishore Bodke
Hi,
Resending the patch for enabling the 32-bit support for
rangeley machine by resuing the existing rangeley branch.
Please pull them into linux-yocto-3.4/meta.
merged and pushed.
Bruce
Thanks
Kishore.
The
gt;
> Thanks, I was hoping that was the case.
>
> I wonder why this isn't working then - I think I've done it as shown in
> the dev manual...
>
Is it something other than the bbappends ? i.e. are you sure you have all
the required
dependencies for CONFIG_HID_AP
On 12-12-09 5:48 AM, Chris Tapp wrote:
On 9 Dec 2012, at 04:47, Bruce Ashfield wrote:
On Sat, Dec 8, 2012 at 7:54 PM, Chris Tapp mailto:opensou...@keylevel.com>> wrote:
On 9 Dec 2012, at 00:11, Chris Larson wrote:
On Sat, Dec 8, 2012 at 5:07 PM, Chris Tapp
mailto:o
phase
and drop into the devshell you may not have KBUILT_OUTPUT set to the
build directory, and end up dropping files in the source dir .. which
causes you
mrproper and build issue.
I have a local append to devshell that sets:
d.setVar("KBUILD_OUTPUT", "${B}")
To mak
ome
sections that I can update and get you new output and remove some of the
TODOs and questions.
I'll try and get to that ASAP so you'll have them in lots of time for
release.
Cheers,
Bruce
Linux Kernel Development with the Yocto Project
Table of Contents
=
IN
iminates the possibility of overriding
the variable. IMO, all of these should be ?= which lets there
be a useful default, but can still be [completely] overridden
by the user.
I'd agree that if we were shooting for consistency, I'd go with
?= and not the +=.
Cheers,
Bruce
_
On 12-12-18 10:45 AM, Marco C. wrote:
2012/12/9 Bruce Ashfield :
As Chris said, this way should still work, and it does work here for me.
There's
one thing that you may notice with kernel's that have split source/build
dirs
(like linux-yocto), is that once you have gone through the
ere because it isn't specific to the kern-tools, what
you see
there is a small wrapper on top of the kernel.bbclass defconfig handling,
with
the same end result. So standard yocto/oe-core docs apply here.
Cheers,
Bruce
>
> rday
>
> --
>
>
/tmp/deploy/image folder (file date time is new)
>
Have you looked in:
/tmp/work/xxx-poky-linux/linux-yocto-xxx/linux
That's your source directory. The linux-yocto recipes build with split
source and object directories.
Cheers,
Bruce
> every “bitbake core-image-minimal” build fi
On Sun, Dec 23, 2012 at 11:10 PM, Bruce Ashfield
wrote:
>
>
>
> On Sun, Dec 23, 2012 at 12:26 PM, Robert P. J. Day
> wrote:
>
>>
>> poking around kern-tools for purpose of documenting some stuff and
>> ran across this in "up
leton for
linux-yocto-custom.bb and you can apply fragments to any upstream git tree
of your choosing. It would of course be better if we get more contributions
to the
main linux-yocto meta data (yocto-kernel-cache and the linux-yocto meta
branch), but
that's completely voluntary.
Cheers,
ity to point at a local git tree, and
turns on
AUTOREV. Something that I always use, and something that anyone else
doing local work could use as well (not that they can't just create their
own
bbappend to do the same thing, but it doesn't hu
nything linux-yocto or kern-tools, since they are both
areas that I develop and maintain :)
So send them to me, I'll queue them and send changes out with my yocto
1.4 pull requests.
Cheers,
Bruce
>
> diff --git a/tools/updateme b/tools/updateme
> index 5998820..56c034a 100755
>
On Tue, Dec 25, 2012 at 2:28 PM, Robert P. J. Day wrote:
> On Tue, 25 Dec 2012, Bruce Ashfield wrote:
>
> > I'm pretty sure if you dig in your email archives, you'll see me
> > asking you to cc' me directly on anything linux-yocto or kern-tools,
> > since
you tried putting
# CONFIG_UNION_FS is not set
in your defconfig ? That should disable it.
Bruce
Could someone give me some help about where to go from here?
Thanks,
Brian
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.or
On 13-01-02 04:11 PM, Brian Smucker wrote:
On 1/2/2013 10:06 AM, Bruce Ashfield wrote:
> On 12-12-24 02:59 PM, Brian Smucker wrote:
>> Hi,
>>
>
> Catching up on email from the holidays. Did you ever get an answer
> to this ?
Not yet, resumed my quest today.
>
On Wed, Jan 2, 2013 at 4:47 PM, Brian Smucker wrote:
> On 1/2/2013 1:12 PM, Bruce Ashfield wrote:
>
>> On 13-01-02 04:11 PM, Brian Smucker wrote:
>>
>>> On 1/2/2013 10:06 AM, Bruce Ashfield wrote:
>>> > On 12-12-24 02:59 PM, Brian Smucker wrote:
>>&
thing.
Bruce
Brian
On 1/2/2013 2:15 PM, Bruce Ashfield wrote:
On Wed, Jan 2, 2013 at 4:47 PM, Brian Smucker mailto:b...@bsmucker.eu.org>> wrote:
On 1/2/2013 1:12 PM, Bruce Ashfield wrote:
On 13-01-02 04:11 PM, Brian Smucker wrote:
On 1/2/2013 10:06 AM, Bruce As
l missing, but may be addressed in yocto 1.4,
when I find the bug numbers, I'll have a better idea.
Cheers,
Bruce
On Jan 15, 2013, at 11:09 AM, Brian Lloyd mailto:bll...@familyhonor.net>> wrote:
Or better yet, now that it is past initial, use
http://www.yoctoproject.org/
d would be centered around recipes.
Cheers,
Bruce
Brian
On Tue, 2013-01-15 at 16:52 +, Patrick Turley wrote:
I used the meta-toolchain-sdk recipe to produce an SDK, and I installed it.
Here's an interesting line from the environment setup script:
export LDFLAGS="-Wl,-O1
On 13-01-15 01:26 PM, Patrick Turley wrote:
On Jan 15, 2013, at 12:00 PM, Bruce Ashfield
wrote:
On 13-01-15 12:54 PM, Patrick Turley wrote:
Thank you for directing me toward that documentation. As it happens, I
have already read that, and it doesn't apply.
There are ways to do this,
On 13-01-22 03:28 PM, Patrick Turley wrote:
On Jan 16, 2013, at 11:11 AM, Darren Hart wrote:
On 01/15/2013 10:38 AM, Bruce Ashfield wrote:
I finally found the entries that I was recalling earlier. They are:
https://bugzilla.yoctoproject.org/show_bug.cgi?id=241
https
On 13-01-21 06:19 PM, Kamble, Nitin A wrote:
Hi Bruce,
I have created a branch for emgd-1.16 kernel driver for the v3.4
kernel repo over here.
http://git.yoctoproject.org/cgit/cgit.cgi/linux-yocto-2.6.37-contrib/log/?h=nitin/emgd-1.16
It consists of mainly following 2 commits on top of the
intact.
merged. and pushed. SRCREV updates to follow, but you can test it locally
before I do the updates.
Bruce
Thanks,
Nitin
The following changes since commit c0b3904d60830e24b3930b0fa606a48b2758d979:
meta: add config fragment for gma600 graphics driver (2013-01-18 23:07:15
-0500
On 13-01-21 06:19 PM, Kamble, Nitin A wrote:
Hi Bruce,
I have created a branch for emgd-1.16 kernel driver for the v3.4
kernel repo over here.
http://git.yoctoproject.org/cgit/cgit.cgi/linux-yocto-2.6.37-contrib/log/?h=nitin/emgd-1.16
It consists of mainly following 2 commits on top of the
intact.
Ack'd. I'll merge this shortly, once I get emgd pulled in .. which I'm
doing now, but being throttled by the servers.
Bruce
Thanks,
Nitin
The following changes since commit c0b3904d60830e24b3930b0fa606a48b2758d979:
meta: add config fragment for gma600 graphics dri
On 13-01-22 9:26 PM, Patrick Turley wrote:
On Jan 22, 2013, at 2:34 PM, Bruce Ashfield
wrote:
On 13-01-22 03:28 PM, Patrick Turley wrote:
One problem I ran into … When I tried to execute "make scripts," I got a whole bunch of
config questions that I *think* should have been answe
On 13-01-23 12:14 AM, Patrick Turley wrote:
On Jan 22, 2013, at 10:43 PM, Bruce Ashfield
wrote:
On 13-01-22 9:26 PM, Patrick Turley wrote:
If I just hold down the "Enter" key, I believe all the defaults are taken, and
I eventually *do* get hostprogs that execute, but I don't
On 13-01-23 12:34 AM, Patrick Turley wrote:
On Jan 22, 2013, at 11:17 PM, Bruce Ashfield
wrote:
On 13-01-23 12:14 AM, Patrick Turley wrote:
On Jan 22, 2013, at 10:43 PM, Bruce Ashfield
wrote:
On 13-01-22 9:26 PM, Patrick Turley wrote:
If I just hold down the "Enter" key, I b
7
https://bugzilla.yoctoproject.org/show_bug.cgi?id=2686
as well as other bitbake/build system generic items (that I can't find at
the moment).
I already have some items in progress for 3517, and they'll be out shortly
for
inclusion in yocto 1.4.
Cheers,
Bruce
> Checking the &qu
On 13-01-24 02:58 PM, John Mehaffey wrote:
On Wed, Jan 23, 2013 at 7:17 AM, Patrick Turley
mailto:patricktur...@gamestop.com>> wrote:
On Jan 23, 2013, at 7:48 AM, Bruce Ashfield
mailto:bruce.ashfi...@windriver.com>>
wrote:
> On 13-01-23 12:34 AM, Patri
r, but the repo will still be present and
accessible.
Cheers,
Bruce
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
rectly in the bb file,
but not when referenced in an include or scc file?
Keeping the question isolated to just the patch on the SRC_URI is a
good idea to make sure we are talking about the simplest case.
Which type of recipe isn't having the patch applied, the mainline one ?
The linux-yocto
On 13-01-28 01:34 PM, stephen.lawre...@renesas.com wrote:
Bruce Ashfield wrote on 28/01/2013
18:01:57:
[snip]
I suspect the kernel fragment issue is down to the fact that a yocto
kernel recipe is not being used,
i.e. it relies on the yocto kernel meta data mechanism?
I can confirm this part
On 13-01-28 01:35 PM, Bruce Ashfield wrote:
On 13-01-28 01:34 PM, stephen.lawre...@renesas.com wrote:
Bruce Ashfield wrote on 28/01/2013
18:01:57:
[snip]
I suspect the kernel fragment issue is down to the fact that a yocto
kernel recipe is not being used,
i.e. it relies on the yocto kernel
On 13-01-29 06:24 AM, stephen.lawre...@renesas.com wrote:
Bruce Ashfield wrote on 28/01/2013
18:56:02:
Why is the SRC_URI containing the additional patches applied when
referenced directly in the bb file,
but not when referenced in an include or scc file?
Keeping the question isolated to
ping a use case such as this down the road.
As to whether or not work is planned in the areas of images and
preferred providers, Richard would know.
Cheers,
Bruce
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org
On 13-01-23 10:17 AM, Patrick Turley wrote:
On Jan 23, 2013, at 7:48 AM, Bruce Ashfield
wrote:
On 13-01-23 12:34 AM, Patrick Turley wrote:
On Jan 22, 2013, at 11:17 PM, Bruce Ashfield
wrote:
On 13-01-23 12:14 AM, Patrick Turley wrote:
On Jan 22, 2013, at 10:43 PM, Bruce Ashfield
On 13-02-01 7:48 PM, Patrick Turley wrote:
On Jan 31, 2013, at 10:50 PM, Bruce Ashfield
wrote:
On 13-01-23 10:17 AM, Patrick Turley wrote:
On Jan 23, 2013, at 7:48 AM, Bruce Ashfield
wrote:
On 13-01-23 12:34 AM, Patrick Turley wrote:
On Jan 22, 2013, at 11:17 PM, Bruce Ashfield
ig AND get the build
infrastructure both CROSS_COMPILE and ARCH are required, just as bitbake
was providing during the original build.
The trick is to still generate modules that will work against the running
kernel .. but that's another story :)
Cheers,
Bruce
Brian
On Sat, 2013-02-02 at 00:48
ht, native utilities never
use the prefix. In fact, in 12 years I've only run into one mix up
between target and native .o's in a kernel build.
Cheers,
Bruce
I do know make scripts does create items intended to run in the final
environment.
Since I build for i386 on an x64 these d
the version to uniquely identify the tree (and my no
spaces comment!).
Maybe someone knows of a better way for command line switching of the
version ?
Cheers,
Bruce
>
>
> Well, kind of, you still would have to know the minor version number.
>
> Cheers,
> Rudi
>
>
> ___
myself. A matter of taste and habits I suppose.
I quick survey shows roughly:
../meta]> find . -name '*.bb' | xargs grep PV | grep SRCPV | wc -l
87
Almost 90 other recipes with some variant of SRCPV in their version string.
So unless I'm mistaken .. they'd all suffer the
-yocto-3.4/meta branch.
Ack'd. I'll merge and push this out on Monday.
Cheers,
Bruce
Thanks
Kishore.
The following changes since commit f697e099bc76d5df3a307a5bc0cc25021dd6dfe0:
meta: bump to v3.4.28, rt-40 (2013-02-04 00:14:21 -0500)
are available in the git repository a
image via MACHINE_ESSENTIAL_EXTRA_RRECOMMENDS.
Cheers,
Bruce
didn’t seem to do anything. I set ‘module_autoload_uio = “uio”’ in
local.conf, which also seemed to do nothing. Same for setting it in
linux-yocto_3.4.bbappend (some patches indicate that it used to be set
in that file). I don’t know what else to
will allow you some more
flexibility in handling modifications to the kernel.
Cheers,
Bruce
Thanks Rudy in advance,
Satya
On Thu, Feb 28, 2013 at 9:31 PM, Rudolf Streif
mailto:rstr...@linuxfoundation.org>> wrote:
Hi Satya,
You will first need a kernel recipe, l
't a surprise. He'll do his normal -stable releases for
3.8 and drop them once 3.9 arrives, which is also expected.
Cheers,
Bruce
http://www.kroah.com/log/linux/3.8-is_not_longterm_stable.html
___
yocto mailing list
yocto@yoctoproject.org
On 13-03-01 02:15 PM, Rudolf Streif wrote:
Bruce,
On Fri, Mar 1, 2013 at 9:29 AM, Bruce Ashfield
mailto:bruce.ashfi...@windriver.com>> wrote:
But note, Greg is talking specifically about LTSI, we don't
expect more than one LTSI per year, and we are already locked into
t
f the emgd branch is just
the git merge of a locally staged branch in the linux-yocto repository.
That commit you reference shouldn't be in the emgd branch, or any
branch if a clean linux-yocto-3.8 tree is being used.
Cheers,
Bruce
So something is getting tied in a knot when the reposit
On 13-03-05 12:56 PM, Kamble, Nitin A wrote:
-Original Message-
From: Bruce Ashfield [mailto:bruce.ashfi...@windriver.com]
Sent: Tuesday, March 05, 2013 9:50 AM
To: Kamble, Nitin A
Cc: linux-yo...@yoctoproject.org
Subject: Re: v3.8 kernel recipes in meta-intel
On 13-03-05 12:35 PM
ELC a few weeks ago (I've added
him to the cc as well), and rather than hiding sched_deadline
kernel support in a custom kernel layer, I'd like to try and get
more eyes on it via linux-yocto .. so if we can all coordinate our
efforts here, that would be much better.
Cheers,
Bruce
With t
On 13-03-06 11:24 PM, Juri Lelli wrote:
Hi,
On 03/06/2013 08:00 PM, Bruce Ashfield wrote:
On 13-03-05 1:54 AM, Insop Song wrote:
Hi,
I am preparing a new meta layer for testing and promoting a
sched_deadline scheduler, called "meta-dl". I am planning to add
scheduler testing
On 13-03-07 12:05 AM, Insop Song wrote:
Bruce,
That's very good. I will bring linux-yocto-3.8 kernel to meta-dl.
(https://github.com/insop/meta-dl/tree/linux-yocto-3.8)
I have another suggestion to offer here, one I've been wanting to
do for a bit.
I've added Darren Hart to th
On 13-03-07 03:26 AM, Insop Song wrote:
Hi Bruce,
One more question on 3.8 kernel.
Is "meta/recipes-kernel/linux/linux-yocto_3.8.bb" added soon as well in 1.4?
It's in master as of a few days ago. So it's available and
ready for use.
Cheers,
Bruce
I am using 1.4_M4.f
On 13-03-07 12:05 AM, Insop Song wrote:
Bruce,
That's very good. I will bring linux-yocto-3.8 kernel to meta-dl.
(https://github.com/insop/meta-dl/tree/linux-yocto-3.8)
The purposes of meta-dl are the following three:
1. easy to use sched_deadline by providing recipes-kernel that inc
On 13-03-07 4:43 PM, Insop Song wrote:
Hi Bruce,
What do you have in your "defconfig" ? I'm about to push patches that
will make enabling sched_dealine a KERNEL_FEATURE option, which makes
it even easier to use.
Here is my defconfg
https://github.com/insop/meta-dl/blob/sche
aying .. getting those examples
will both help the approach and perhaps help get it merged into the
mainline kernel.
I've been looking application descriptions when I was in Ericsson, and
provided cases to Thomas and Juri.
I am interested in this as well, and include them in easy-to test/vali
t;.
Nothing comes to mind. It all depends on what target you are using, and
if you are using the 'defconfig' that you mentioned earlier. Switching
to the linux-yocto policy and BSP fragments will likely fix your problem.
Bruce
Thank you,
Insop
On Thu, Mar 7, 2013 at 6:05 AM,
n above definition
resulting dtb files will show up in deploy_dir
Thanks Khem, I had meant to reply to this myself .. and then managed
to forget!
Bruce
HTH
-Khem
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
On 13-03-08 08:27 AM, Insop Song wrote:
On Thu, Mar 7, 2013 at 6:04 AM, Bruce Ashfield
wrote:
On 13-03-07 12:05 AM, Insop Song wrote:
Bruce,
That's very good. I will bring linux-yocto-3.8 kernel to meta-dl.
(https://github.com/insop/meta-dl/tree/linux-yocto-3.8)
I have another sugge
/modules? Or is there some other mechanism that I should use. I
tried going through the module.bbclass but must admit I lost it
somewhere in the middle ;) Any guidance would be appreciated.
module_autoload_, in your module recipe, will
trigger the load on boot.
Cheers,
Bruce
Hans
On 13-03-08 12:03 PM, Darren Hart wrote:
On 03/07/2013 06:04 AM, Bruce Ashfield wrote:
On 13-03-07 12:05 AM, Insop Song wrote:
Bruce,
That's very good. I will bring linux-yocto-3.8 kernel to meta-dl.
(https://github.com/insop/meta-dl/tree/linux-yocto-3.8)
I have another suggesti
On 13-03-08 12:40 PM, Hans Beckérus wrote:
8 mar 2013 kl. 18:12 skrev Bruce Ashfield :
On 13-03-08 07:08 AM, Hans Beckérus wrote:
Hi. I have built some custom kernel modules (.ko) using a .bb that
inherits from the module.bbclass. There is one main kernel module and
the rest are dependent
eta-realtime that I'd like
to have created shortly.
Cheers,
Bruce
With the help of hands-on kernel lab (thank you Tom and Darren), I am
able to make kernel with sched_deadline enabled.
Now, I am having some trouble of adding testing tools to this meta-dl,
and hope I can get some help from
7; % basename, True)
if modconf:
name = '%s/etc/modprobe.d/%s.conf' % (dvar, basename)
f = open(name, 'w')
f.write("%s\n" % modconf)
f.close()
Cheers,
Bruce
I do not think that the mandatory module that is loaded
r the years for yet more custom ways to get
things done.
So that's my summary, as you can see, it's a long standing, evolving
and complex story .. and not something that likely has an 'out of the
box' solution at the moment.
Cheers,
Bruce
I 0tried changing the kernel’s Pre
On Sat, Mar 9, 2013 at 12:12 PM, Vin Shelton wrote:
> On Fri, Mar 8, 2013 at 10:28 PM, Bruce Ashfield
> wrote:
>> On 13-03-08 5:36 PM, David Mulder wrote:
>>> I’m running a 10us control loop by (under vxWorks) setting one thread’s
>>> priority to max and not yiel
:s
> etc. will interfere. But significantly less then the rt-throttling :)
Absolutely! And as long as you really know what you are doing, you
won't kill the
system .. turning off the throttling definitely gives a bit more rope
to that end as
well
On 13-03-09 5:32 AM, Insop Song wrote:
On Fri, Mar 8, 2013 at 3:35 PM, Bruce Ashfield
wrote:
On 13-03-08 12:01 PM, Darren Hart wrote:
On 03/04/2013 08:04 PM, Insop Song wrote:
Hi,
I am preparing a new meta layer for testing and promoting a
sched_deadline scheduler, called "meta-d
On 13-03-11 09:28 AM, Hans Beckérus wrote:
On Sat, Mar 9, 2013 at 12:45 AM, Bruce Ashfield
mailto:bruce.ashfi...@windriver.com>> wrote:
On 13-03-08 2:00 PM, Hans Beckerus wrote:
On 2013-03-08 7:12, Eric Bénard wrote:
Hi Hans,
Le Fri, 8 Mar 2013 13
On 13-03-11 09:46 AM, Eric Bénard wrote:
Hi Bruce,
Le Mon, 11 Mar 2013 09:37:44 -0400,
Bruce Ashfield a écrit :
Can you post your exact changes where we can see them ? You need to put
the module_autload variable in a .conf file, whether that be your
local.conf, your machine.conf or you distro
On 13-03-10 11:32 PM, Insop Song wrote:
On Sun, Mar 10, 2013 at 8:28 PM, Bruce Ashfield
Expect that the yocto project hosted meta-realtime will appear in a
week or so. I'm doing the legwork at the moment, but with some travel
in the upcoming week, the initial push will be delayed by a few
On Mon, Mar 11, 2013 at 12:07 PM, Insop Song wrote:
> On Mon, Mar 11, 2013 at 7:34 AM, Bruce Ashfield
> wrote:
>>
>> As an example, I have a schedtool recipe that uses the
>> git://gitorious.org/sched_deadline/schedtool-dl.git
>> repository with a 4 patch series to
te with it
from Linux.
remoteproc/rpmsg can solve some of the issues that I mention, but
it is far from out of the box.
That's why there's more interest in running a single task with
exclusive CPU in userspace. The work and scaffolding required to
get an AMP system up and running is non
avoid page faults, etc.
If you check out the preempt-rt wiki page on kernel.org, a lot of the
information there applies to making sure that your prioritized thread
gets the most run time that it can.
As we progress with the meta-realtime layer, scripts for the above,
system configuration, services and wil
On 13-03-14 12:52 PM, Insop Song wrote:
Hi Bruce,
This is for adding rt-app, please let me know what you think.
For next patch, I will add schedtool_dl
This patch looks ok, what are the differences from your original
layer ? I've already imported changes from there, so I'd just
li
On 13-03-14 12:52 PM, Insop Song wrote:
Hi Bruce,
This is for adding rt-app, please let me know what you think.
For next patch, I will add schedtool_dl
Reading this more closely, can you split this into two patches ?
We need to review this in chunks, patch 1 for the rt-app (it
looks fine
On 13-03-14 10:09 PM, Insop Song wrote:
Hi Bruce,
I've added recipes-kernel to use edf branch and cfg.
FYI: your email keeps bouncing from the linux-yocto mailing list,
check to be sure you signed up with your gmail account, I keep
approving them for now :)
- tested on qe
On Thu, Mar 14, 2013 at 10:59 PM, Insop Song wrote:
> On Thu, Mar 14, 2013 at 10:15 PM, Bruce Ashfield
> wrote:
>
>>
>> FYI: your email keeps bouncing from the linux-yocto mailing list,
>> check to be sure you signed up with your gmail account, I keep
>> appr
On Thu, Mar 14, 2013 at 10:09 PM, Insop Song wrote:
> Hi Bruce,
>
> I've added recipes-kernel to use edf branch and cfg.
I was just merging your changes, and realized that gmail may have dropped
your schedtool-dl recipe.
Can you resend it with your updated series ? I have ano
On 13-03-14 11:36 PM, Insop Song wrote:
On Thu, Mar 14, 2013 at 11:13 PM, Bruce Ashfield
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
On 13-03-14 11:44 PM, Bruce Ashfield wrote:
On 13-03-14 11:36 PM, Insop Song wrote:
On Thu, Mar 14, 2013 at 11:13 PM, Bruce Ashfield
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 sign
override this dependency if kernel image files are
# not wanted in images as standard
RDEPENDS_kernel-base ?= "kernel-image"
You'll still get your kernel modules installed after making this change.
Bruce
Or do we need to write some post installer for our rootfs that mounts
the ima
inherit from
kernel.bbclass it worked as expected.
Interesting. Are you working out of yocto/oe-core master ? The linux
yocto kernel support should always fail if the kernel source dir
isn't a git repo (or convert it into one) and not impact the main
yocto/oe-core tree.
Cheers,
On 13-03-15 07:36 AM, Hans Beckérus wrote:
On Fri, Mar 15, 2013 at 3:20 PM, Bruce Ashfield
mailto:bruce.ashfi...@windriver.com>> wrote:
On 13-03-15 06:33 AM, Hans Beckérus wrote:
Hi. In an effort to shrink our rootfs by some major numbers we
found two
low-h
s and to do that,
we need a well defined SRCREV.
So one more version of the series and we should be good (you can
drop the image addition as part of that) .. sorry for all the
iterations, the first merges always take the longest.
Cheers,
Bruce
+
+S = "${WORKDIR}/git"
+
+do_compile() {
tem is converted
to a git repository before the build starts, allow all the tool extensions
to work with configs that for one reason or another can't use a git
backed tree.
I just tested it here, and it worked, using the latest code in master.
Cheers,
Bruce
_
ack anymore.
I'll merge, do a quick test and push this out on Monday.
Cheers,
Bruce
*applications tested are shown below:
1. rt-app
- "rt-app" is a test application that starts multiple periodic threads
in order to simulate a real-time periodic load
- run example
root@qe
art of the question. Simply rebuild the kernel yourself
and the timeout will be removed. All of the configuration and layers
used to build the kernel you downloaded are available with the meta-intel
releases, minus the layer that adds the timeout configuration.
Cheers,
Bruce
address that is gi
1 - 100 of 1424 matches
Mail list logo
