ironically, i'm working on this very example and something in the dev manual doesn't look right. section A.5.2.1: These commands take care of the recipes-bsp recipes: $ rm -rf

The odd thing is not only is the bzImage file is missing, but also is the whole kernel directory that bzImage is supposed to be locate in.

Yeah, normally, assuming you're using an existing kernel branch. But you didn't get a build error for the kernel, so I'm assuming that's the case. Tom

Just to clear up the basics, Prior to following Appendix A verbatim, I did the following 1. install prerequisites from GS guide 2. git clone git://git.yoctoproject.org/poky 3. cd poky 4. git clone

Hi, Hmm, not sure what's going on here - I'm sure this example was verified several times, but just to make sure, what you're doing is going through 'Appendix A. BSP Development Example' verbatim and

I tried to duplicate the Yocto Project Decelopment Manual Appendix A build of a Crownbay NOEMGD image, no changes just dulicate the instructions. This is using the latest Yocto 1.1. I did get a

I've merged this to master, thanks. Richard

i'm sure there's a simple solution for this but i'm building core-image-sato-dev for the beagleboard on my 64-bit ubuntu system and the build eventually fails with *numerous* errors of the

Attendees: Beth, Jessica, Tom, Matthew, Joshua, Mark, Jeff, Bruce, Richard, Saul, Darren, Song   Agenda:   Action items: 1. Song will work with Jiajun to get the QA plan ready for point

Attendees: Beth, Jessica, Tom, Matthew, Joshua, Mark, Jeff, Bruce, Richard, Saul, Darren, Song   Agenda:   Action items: 1. Song will work with Jiajun to get the QA plan ready for point

just noticed that Appendix D of the poky reference manual lists the supported images, and suggests you can see them all with: $ ls meta*/recipes*/images/*.bb but the list in that appendix doesn't

[..] Please pay attention to the above!

Hi Noel, Are you also integrating Freescale xorg driver and related libs? Also Freescale has a large set of patchs for the kernel that are not in mainstream, you can take a look at

* Opens collection - 5 min (Song) * Yocto 1.0.2 and 1.1.1 point release update - 5 min (Josh) * Yocto 1.2 planning and M1 planning - 20 min (team)

Thanks, that's a very good article that may explain some issues I've been seeing. Chris

- Hide quoted text - On Mon, Oct 31, 2011 at 10:26 PM, McClintock Matthew-B29882 <B29882@...> wrote: What commands did you run to generate this rpm? What file is this in? I've run

<miketsukerman@...> wrote: Mike, You need to reply all to include the mailing list. What commands did you run to generate this rpm? What file is this in? Usually the shebang should be updated

Look back in the archives - I think it was Richard that did a fairly extensive study of this and he (whoever it was) found that there were saturation points and trying to get beyond them had a

that's what i would normally use, assuming that having an overly high value for either of those settings can't possibly hurt. if that's the consensus, i can adjust the references to say 2x

I agree the manual and local.conf files should match. The issue seems to be that the perfect values are subjective. Things like memory, disk speed, chipset latency, and of course processor