On Sat, Mar 16, 2013 at 10:01 PM, Khem Raj wrote:
>
> On Mar 15, 2013, at 4:47 AM, Insop Song wrote:
>
>> +SRCREV = "${AUTOREV}"
>
> IMO find a good revision and send that one here. you can use AUTOREV
> internally for your
> development thats all fine
Hi Khem,
Thank you for the review.
I've
YS= "i586-poky-linux"
MACHINE = "qemux86"
DISTRO= "poky"
DISTRO_VERSION= "1.3+snapshot-20130316"
TUNE_FEATURES = "m32 i586"
TARGET_FPU= ""
meta
meta-yocto
meta-yocto-bsp= "master:2381e46e77c8d33
On Mar 15, 2013, at 4:47 AM, Insop Song wrote:
> +SRCREV = "${AUTOREV}"
IMO find a good revision and send that one here. you can use AUTOREV internally
for your
development thats all fine
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yo
On 13-03-16 6:16 AM, Insop Song wrote:
meta-realtime layer for testing sched_deadline and other real-time applications
Add rt-app, schedtool, define core-image-realtime, and append recipies-kernel
This looks good to me now, I still think we'll have some confusion
between the core "rt" images
On 16 March 2013 01:16, Insop Song wrote:
> So at this point, I will wait to see if any one is seen this recently.
The autobuilder appears to be hitting this still, but as several
oe-core maintainers are still travelling after a conference you may
have to wait until Monday.
(writing this from Se
This mail was sent out by Package Report System.
It will list all the recipes which can't check upstream version by script, and
will show how long it is since their last mannual version check.
You can check the detail information at
http://packages.yoctoproject.org/manuallychkinfo
PackageName
This mail was sent out by Package Report System.
This message list those recipes which need to be upgraded. If maintainers
believe some of them needn't to upgrade this time, they can fill in
RECIPE_NO_UPDATE_REASON_pn-"xxx" in upstream_tracking files to ignore this
recipe remainder until newer u
hello,
I'm preety new with linux embedded and especially with Yocyo Project wich
by the way i think it's awesome. I managed to build a
core-image-sato-quemux86, it runs ok within qemu, but now i want to boot
this image from a USB memory stick, and i don't know how to do it, and wich
files from /bui
*applications tested
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@qemux86:~# rt-app -t 10:35000:d -D 1
[rt-app] [0] Using SCHED_DEADLINE policy:
[rt-app] [0] starting thread with
meta-realtime layer for testing sched_deadline and other real-time applications
Add rt-app, schedtool, define core-image-realtime, and append recipies-kernel
*applications tested are shown below:
1. rt-app
- "rt-app" is a test application that starts multiple periodic threads
in order to simul
On Fri, Mar 15, 2013 at 7:46 AM, Bruce Ashfield
wrote:
> On 13-03-15 04:47 AM, Insop Song wrote:
>>
>> ---
>> recipes-extended/images/core-image-realtime.bb |1 +
>> recipes-tools/schedtool-dl/schedtool-dl.bb | 23
>> +++
>> 2 files changed, 24 insertions(+)
>>
On Fri, Mar 15, 2013 at 8:58 AM, Darren Hart wrote:
>
> Check this image, I think you'll find that rootwait is missing for this
> image.
>
yes, no rootwait for "sda" type generation.
Regards,
Insop
___
yocto mailing list
yocto@yoctoproject.org
https:/
Wither further more testing, even at
"e609afe4d747059480b406602cab90b7c36a0572", I still get the neard
error.
I suspect my sstate or working files, since this error comes at
package generation.
So I did "-c cleansstate" "-c cleanall" then run it with Richard fix
as my master head (7803f5f98cf4d12d
13 matches
Mail list logo
