On Mon, 2013-04-08 at 11:41 -0400, Robert P. J. Day wrote:
> finally have the time to work my way through the ELC 2013 hands on
> kernel labs described here:
>
> https://www.yoctoproject.org/tools-resources/presentations/working-kernel
>
> since i'll almost certainly use some of them in my next y
The process that you are describing is commonly called "device
provisioning." I have experienced this process from different angles:
working for a company making functional test equipment for electronics
production lines and working for a company providing software for set-top
boxes.
>From this ex
On Mon, 8 Apr 2013, Bruce Ashfield wrote:
> On 13-04-08 5:59 PM, Robert P. J. Day wrote:
> >
> >other than the canonical routerstation pro in the meta-yocto-bsp
> > layer, is there any serious work being put into MIPS machines? a
> > quick google didn't seem to find anything, and the rs pro i
On Mon, 8 Apr 2013, Bruce Ashfield wrote:
> On 13-04-08 5:59 PM, Robert P. J. Day wrote:
> >
> >other than the canonical routerstation pro in the meta-yocto-bsp
> > layer, is there any serious work being put into MIPS machines? a
> > quick google didn't seem to find anything, and the rs pro i
On 13-04-08 5:59 PM, Robert P. J. Day wrote:
other than the canonical routerstation pro in the meta-yocto-bsp
layer, is there any serious work being put into MIPS machines? a
quick google didn't seem to find anything, and the rs pro itself was
end-of-lifed a while back (as i recall), so is t
other than the canonical routerstation pro in the meta-yocto-bsp
layer, is there any serious work being put into MIPS machines? a
quick google didn't seem to find anything, and the rs pro itself was
end-of-lifed a while back (as i recall), so is there something else if
one wants to use yocto on
On Mon, Apr 8, 2013 at 5:49 PM, Sean Liming wrote:
> Is this post-build utility an active
> project for the Yocto Project or is it just getting started?
It's only in the discussion phase right now, hence the "RFC" in the
subject line.
___
yocto mailing
> -Original Message-
> From: Trevor Woerner [mailto:twoer...@gmail.com]
> Sent: Monday, April 08, 2013 1:28 PM
> To: Sean Liming
> Cc: Venkata ramana gollamudi; yocto@yoctoproject.org; Sanil kumar
> Subject: Re: [yocto] RFC: Post build configuration
>
> On Thu, Apr 4, 2013 at 6:42 PM, Sean
Hi Holger,
Using master (and not the SHA advertised in README.md) the build was actually
successful.
Attaching patch.
Signed-off-by: Gianpaolo Macario
---
README.md |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/README.md b/README.md
index b2c84f9..f17a606 100644
--- a
On Thu, Apr 4, 2013 at 6:42 PM, Sean Liming wrote:
> Why post-build instead of pre-build?
The idea is that you have one build, and you are manufacturing 5000 devices.
So you take this one build and load it on each of your identical
devices which you then sell to your customers. But if each devic
Agenda:
* Opens collection - 5 min (Song)
* Yocto Project 1.4 M5 release readiness review - 10 min (CCB/community)
* Yocto 1.4 status - 10 min (Song/team)
https://wiki.yoctoproject.org/wiki/Yocto_Project_v1.4_Status
* SWAT team rotation: Bogdan Marinescu -> Laurentiu Palcu
* Opens - 10 min
* Tea
I tried to rebuild the xf86-input-evdev; however the core-image-sato still
insists on using the default mouse / keyboard drivers instead of evdev. Also no
/dev/input/event* entries exist (only /dev/input/mice and /dev/input/mouse0).
Concerning removing xf86-input-mouse / xf86-input-keyboard fro
On Apr 8, 2013, at 5:47 AM, Paul Eggleton wrote:
> Does installing eglibc-dbg help with this? (Assuming you don't have this
> installed already.)
libc6-dev should be enough. You do not need -dbg one. If it does not work with
-dev
then we have a problem.
___
a bit of inconsistent wording between the kernel hands-on lab1 and
the kernel dev manual (unless i'm misreading).
in lab1, we read:
"This is a bare-bones simple Linux kernel recipe. It inherits all of
the logic for configuring and building the kernel from the
kernel.bbclass (the 'inherit ker
On Mon, 8 Apr 2013, Bruce Ashfield wrote:
> On 13-04-08 12:02 PM, Robert P. J. Day wrote:
> > On Mon, 8 Apr 2013, Bruce Ashfield wrote:
> >
> > > On 13-04-08 11:41 AM, Robert P. J. Day wrote:
> > > >
> > > > finally have the time to work my way through the ELC 2013 hands on
> > > > kernel labs
On 13-04-08 12:02 PM, Robert P. J. Day wrote:
On Mon, 8 Apr 2013, Bruce Ashfield wrote:
On 13-04-08 11:41 AM, Robert P. J. Day wrote:
finally have the time to work my way through the ELC 2013 hands on
kernel labs described here:
https://www.yoctoproject.org/tools-resources/presentations/
On Mon, 8 Apr 2013, Bruce Ashfield wrote:
> On 13-04-08 11:41 AM, Robert P. J. Day wrote:
> >
> >finally have the time to work my way through the ELC 2013 hands on
> > kernel labs described here:
> >
> > https://www.yoctoproject.org/tools-resources/presentations/working-kernel
> >
> > since i'
On 13-04-08 11:41 AM, Robert P. J. Day wrote:
finally have the time to work my way through the ELC 2013 hands on
kernel labs described here:
https://www.yoctoproject.org/tools-resources/presentations/working-kernel
since i'll almost certainly use some of them in my next yocto course,
so the
finally have the time to work my way through the ELC 2013 hands on
kernel labs described here:
https://www.yoctoproject.org/tools-resources/presentations/working-kernel
since i'll almost certainly use some of them in my next yocto course,
so the occasional question for anyone who's already bee
Hello Gianpaolo,
> Hello
>
> I am afraid I discovered a bug against the GENIVI Foton-0.1 Yocto Baseline.
> I followed the instructions at http://git.yoctoproject.org/cgit/cgit.cgi/meta-
> ivi/tree/README.md?h=4.0
>
> I suspect some misalignment between meta-ivi and poky SHA - however I
> believe
Hi Jessica,
I can reproduce this issue following these steps:
- open yocto-bsp menu
- set metadata location
- set build location directory using browse button and without interfering with
the text field at all
- set output location to new directory
- press "Next"
- select a Kernel from the combo
Hello,
I'm trying to generate an image for the FRI2 using the official Intel BSP
provided in the Yocto Project website, in this image I want to include at
least one package manager.
I'm Using poky 8.0 with Hob GUI, from the recipes listed that can be
included in the image I can see Dpkg and Zyppe
Hello
I am afraid I discovered a bug against the GENIVI Foton-0.1 Yocto Baseline.
I followed the instructions at
http://git.yoctoproject.org/cgit/cgit.cgi/meta-ivi/tree/README.md?h=4.0
I suspect some misalignment between meta-ivi and poky SHA - however I believe I
followed what the README.me sa
On 2013-04-08 06:47, Paul Eggleton wrote:
On Monday 08 April 2013 06:30:02 Gary Thomas wrote:
On 2013-04-08 05:03, Gary Thomas wrote:
I'm trying to run GDB to debug code on my target. Whenever I start
it up, I get this warning:
warning: Unable to find libthread_db matching inferior's thre
On Monday 08 April 2013 06:30:02 Gary Thomas wrote:
> On 2013-04-08 05:03, Gary Thomas wrote:
> > I'm trying to run GDB to debug code on my target. Whenever I start
> >
> > it up, I get this warning:
> >warning: Unable to find libthread_db matching inferior's thread
> >library, thread deb
On 13-04-08 04:24 AM, Hongxu Jia wrote:
The following changes since commit 1b534b2f8bbe9b8a773268cfa30a4850346f6f5f:
meta: preempt-rt, inherit standard config (2013-03-25 13:36:42 -0700)
are available in the git repository at:
git://git.pokylinux.org/poky-contrib hongxu/fix-atompc-kernel
Hi Guys,
I have a TSC2007 touchscree for my tegra-harmony board The problem is
calibration of the board Let me explain a bit better. I successfully
compiled a basic X11 image.
On the boot, the Linux penguins appear in the landscape mode on the
display. Is it possible to rotate so that the
On 2013-04-08 05:03, Gary Thomas wrote:
I'm trying to run GDB to debug code on my target. Whenever I start
it up, I get this warning:
warning: Unable to find libthread_db matching inferior's thread library,
thread debugging will not be available.
and indeed, no thread debug commands will wor
On 8 April 2013 13:12, Andreas Enbacka wrote:
> I rebuilt xf86-input-keyboard and xf86-input-mouse (as well as the
> core-image-sato image), and now the mouse / keyboard works ok in X. Thanks
> for the assistance.
>
> I checked the Xorg log file, it seems to add the mouse using the mouse_drv.so
I rebuilt xf86-input-keyboard and xf86-input-mouse (as well as the
core-image-sato image), and now the mouse / keyboard works ok in X. Thanks for
the assistance.
I checked the Xorg log file, it seems to add the mouse using the mouse_drv.so
module, not evdev_drv.so. Do I need to rebuild xf86-inp
I'm trying to run GDB to debug code on my target. Whenever I start
it up, I get this warning:
warning: Unable to find libthread_db matching inferior's thread library,
thread debugging will not be available.
and indeed, no thread debug commands will work.
I've found that the library /usr/lib/l
Thanks again for your assistance. I checked /usr/lib/xorg/modules/input, and
evdev_drv.so is indeed present.
I will try rebuild the specified modules, and see in case it solves the problem
(I have indeed built some atom-pc images previously).
Thanks,
Andreas
-Original Message-
From:
On 8 April 2013 10:50, Andreas Enbacka wrote:
> Thanks for your reply, very much appreciated. I am currently using Poky
> master. I have attached the complete Xorg.0.log; it does not contain any
> mentions of evdev, only mouse, which would imply that evdev does not get
> loaded of some reason.
Ross,
Thanks for your reply, very much appreciated. I am currently using Poky master.
I have attached the complete Xorg.0.log; it does not contain any mentions of
evdev, only mouse, which would imply that evdev does not get loaded of some
reason.
//Andreas
-Original Message-
From: Bu
Hello,
I have a little problem in finding out how does serial communication works
within yocto-project.
I've build a sato image with meta-emenlow bsp and qt4 support, i've done
some qt apps and succeded in making them work on the target machine.
Now i want my qt applicaion to recive some data via s
On 8 April 2013 09:42, Andreas Enbacka wrote:
> I have experienced some problems with getting the USB mouse and keyboard
> detected in the default core-image-sato Yocto image, built for the Intel
> Emenlow machine (with emgd graphics). X launches successfully to the Sato
> desktop, but I get no re
Hello,
I have experienced some problems with getting the USB mouse and keyboard
detected in the default core-image-sato Yocto image, built for the Intel
Emenlow machine (with emgd graphics). X launches successfully to the Sato
desktop, but I get no response from the mouse or keyboard. When I fr
37 matches
Mail list logo
