Re: [yocto] [OE-core] bring mipsel support (little endian mode)

On Tue, Jun 26, 2012 at 11:25 PM, Dennis.Yxun wrote: > HI ALL: >   Sorry for crossing post, but I'm quite new here, so if I did > something wrong, please point me the right direction. thanks >   I'm using oe-core, and notice that mipsel support(o32, little > endian mode) is missing (current availa

[yocto] bring mipsel support (little endian mode)

HI ALL: Sorry for crossing post, but I'm quite new here, so if I did something wrong, please point me the right direction. thanks I'm using oe-core, and notice that mipsel support(o32, little endian mode) is missing (current available choose is: qemumips, qemumips64, qemumips64el). So, her

[yocto] 'check_sanity_eventhandler' failed

Hi, We are using poky-denzil-7.0. I am trying to create SDK by running "bitbake -v meta-toolchain-qte" . But it is getting failed at the earlier phase throwing an error "DEBUG: Fetcher accessed the network with the command git ls-remote git:// git.yoctoproject.org/yocto-firewall-test HEAD DEBUG:

[yocto] How to include libstdc++ in an image?

Hi. I am using denzil, trying to build a core-image-minimal with libstdc++ installed. I want to cross-develop in c++, and run the resulting apps on the image. For now, I am using qemu-arm as the machine. I've been able to build and run core-image-minimal out of the box. build the cross tool

Re: [yocto] Yocto Development Manual Appendix B question

Yes I did cleansstate. Sent from my iPhone On Jun 26, 2012, at 4:43 PM, "Rifenbark, Scott M" wrote: > Jim, > > Did you cleansstate before building and using menuconfig? There is a bug > (2256) that prevents configurations made using menuconfig from sticking. > > Scott > > -Original

[yocto] Git fetcher error

I'm trying to use git://github.com/bootc/linux.git in a recipe, but 'do_fetch' is failing. If I fetch manually, then it takes a long, long time to go through 'remote: counting objects' and 'remote: compressing object'. Is this causing a timeout in the fetcher? If so, can I do anything to allow

Re: [yocto] Yocto Development Manual Appendix B question

Yes - looking more closely this is not the bug issue but standard warnings. I got these also. I can put a note in the example explaining the situation. Scott -Original Message- From: Bruce Ashfield [mailto:bruce.ashfi...@gmail.com] Sent: Tuesday, June 26, 2012 1:57 PM To: jfabernathy

Re: [yocto] Yocto Development Manual Appendix B question

On Tue, Jun 26, 2012 at 4:40 PM, jfabernathy wrote: > On 06/26/2012 04:21 PM, Rifenbark, Scott M wrote: >> >> Jim, >> >> Yes - I am still running the very last part of my test.  If that is the >> change then I will make it to the 1.2 version of the manual and publish it >> to the website. >> >> Sc

Re: [yocto] Yocto Development Manual Appendix B question

Jim, Did you cleansstate before building and using menuconfig? There is a bug (2256) that prevents configurations made using menuconfig from sticking. Scott -Original Message- From: jfabernathy [mailto:jfaberna...@gmail.com] Sent: Tuesday, June 26, 2012 1:40 PM To: Rifenbark, Scott M

Re: [yocto] Yocto Development Manual Appendix B question

On 06/26/2012 04:21 PM, Rifenbark, Scott M wrote: Jim, Yes - I am still running the very last part of my test. If that is the change then I will make it to the 1.2 version of the manual and publish it to the website. Scott While I had this working I thought I'd complete the Appendix B exam

[yocto] meta-raspberrypi - Latest kernels won't run (summary)

I've updated the SRCREVs: bootfiles : 542ee2c3a5aea50377b97ec0308eb884900512ca kernel: f679f0534867d64a3672108d73bed5d349728f73 This build ok, but the kernel doesn't boot (screen shows the 'four-colours' kernel boot error). The bootfiles seem to be good as they will work with older kernels

Re: [yocto] How to clean

On Tue, 26 Jun 2012, Stewart, David C wrote: > >From: yocto-boun...@yoctoproject.org [mailto:yocto- > >boun...@yoctoproject.org] On Behalf Of Dallas Clement > >Sent: Tuesday, June 26, 2012 12:21 PM > > > >I'd like to clean all of my build output so that I can rebuild with a > >different toolchain.

Re: [yocto] Yocto Development Manual Appendix B question

Jim, Yes - I am still running the very last part of my test. If that is the change then I will make it to the 1.2 version of the manual and publish it to the website. Scott -Original Message- From: yocto-boun...@yoctoproject.org [mailto:yocto-boun...@yoctoproject.org] On Behalf Of

Re: [yocto] How to clean

On Tue, 26 Jun 2012, Dallas Clement wrote: > I'd like to clean all of my build output so that I can rebuild with a > different toolchain. What is the best way to clean without having to > redownload all of my source packages again? > > I can see that something like this > > $ bitbake -c cleanall

Re: [yocto] How to clean

>From: yocto-boun...@yoctoproject.org [mailto:yocto- >boun...@yoctoproject.org] On Behalf Of Dallas Clement >Sent: Tuesday, June 26, 2012 12:21 PM > >I'd like to clean all of my build output so that I can rebuild with a >different toolchain. What is the best way to clean without having to >redownl

Re: [yocto] How to clean

On Tue, Jun 26, 2012 at 12:21 PM, Dallas Clement wrote: > > > can clean the kernel or an individual package.  I want to clean everything. by default DL_DIR lives outside TMPDIR so you can delete the TMPDIR ___ yocto mailing list yocto@yoctoproject.org h

Re: [yocto] Yocto Development Manual Appendix B question

On 06/26/2012 02:07 PM, Rifenbark, Scott M wrote: When I attempted to rebuild minimal I hit the same error you did Jim regarding kern-tools-native. This would be expected as Bruce pointed out that problem is alive in denzil. I am going to set the poky-extras branch to 'denzil' and retry that

Re: [yocto] Yocto Development Manual Appendix B question

On 06/26/2012 02:07 PM, Rifenbark, Scott M wrote: When I attempted to rebuild minimal I hit the same error you did Jim regarding kern-tools-native. This would be expected as Bruce pointed out that problem is alive in denzil. I am going to set the poky-extras branch to 'denzil' and retry that

[yocto] How to clean

I'd like to clean all of my build output so that I can rebuild with a different toolchain. What is the best way to clean without having to redownload all of my source packages again? I can see that something like this $ bitbake -c cleanall linux-yocto can clean the kernel or an individual packa

[yocto] Minutes: Yocto Project Technical Team Meeting - Tuesday, June 26, 2012 8:00 AM-9:00 AM (UTC-08:00) Pacific Time (US & Canada).

Attendees: LaurentiuP, Jefro, Richard, Bruce, Michael, Ross, Mark, Sean, Jeff, Tom, Darren, Gilbert, Denys, Jessica, ScottR, Saul, Paul, Jim, Ciby, Alex, Song   Gilbert is from mentor Graphics, working with Sean.   Agenda:   * Opens collection - 5 min (Song) * 1.3 M1 release readiness - 10 min (co

Re: [yocto] the current yocto FAQ is pretty much valueless

On 06/26/2012 10:18 AM, Tomas Frydrych wrote: > On 26/06/12 17:53, Robert P. J. Day wrote: >> and if you want major industry players to take yocto seriously, the >> last thing you want to do is answer their heartfelt pleas for >> assistance with, "i'm sorry, that's technically not a yocto questio

Re: [yocto] Yocto Development Manual Appendix B question

When I attempted to rebuild minimal I hit the same error you did Jim regarding kern-tools-native. This would be expected as Bruce pointed out that problem is alive in denzil. I am going to set the poky-extras branch to 'denzil' and retry that part of the example. Scott -Original Message-

Re: [yocto] the current yocto FAQ is pretty much valueless

No, an FAQ should not get you the expertise to create a commercial grade product. Reading the documentation should though. You don't want users to have to study source code. On Tue, Jun 26, 2012 at 1:18 PM, Tomas Frydrych wrote: > On 26/06/12 17:53, Robert P. J. Day wrote: > > and if you want

Re: [yocto] Yocto Development Manual Appendix B question

I am on task 1507 of 1606 of a minimal build (from the example). No issues so far. -Original Message- From: Bruce Ashfield [mailto:bruce.ashfi...@windriver.com] Sent: Tuesday, June 26, 2012 10:42 AM To: Rifenbark, Scott M Cc: jfabernathy; yocto@yoctoproject.org Subject: Re: [yocto] Yoct

Re: [yocto] Yocto Development Manual Appendix B question

On 12-06-26 12:30 PM, Rifenbark, Scott M wrote: I am going to run through the B.1 example verbatim from the "current" version of the manual and see what happens. Fixing the license check was just a matter of me locking the SRCREV for the tools to a value that works for denzil. I just pushed a

Re: [yocto] the current yocto FAQ is pretty much valueless

On 26/06/12 17:53, Robert P. J. Day wrote: > and if you want major industry players to take yocto seriously, the > last thing you want to do is answer their heartfelt pleas for > assistance with, "i'm sorry, that's technically not a yocto question, > you should try another mailing list." That's

Re: [yocto] the current yocto FAQ is pretty much valueless

On Tue, 26 Jun 2012, Paul Eggleton wrote: > On Tuesday 26 June 2012 13:05:21 Robert P. J. Day wrote: > > On Tue, 26 Jun 2012, Paul Eggleton wrote: > > > On Tuesday 26 June 2012 12:51:15 Robert P. J. Day wrote: > > > > ok, that makes sense. but would it also make sense for bitbake to > > > > per

Re: [yocto] the current yocto FAQ is pretty much valueless

On Tue, 26 Jun 2012, Rifenbark, Scott M wrote: > So this situation might lend itself to a nice FAQ question > Something like "How do I isolate site and machine specific > information during a build?" And the solution can tell them how to > use a site.conf file. yes, but it would also need

Re: [yocto] the current yocto FAQ is pretty much valueless

On Tuesday 26 June 2012 13:05:21 Robert P. J. Day wrote: > On Tue, 26 Jun 2012, Paul Eggleton wrote: > > On Tuesday 26 June 2012 12:51:15 Robert P. J. Day wrote: > > > ok, that makes sense. but would it also make sense for bitbake to > > > perhaps support another option that *does* allow persona

Re: [yocto] the current yocto FAQ is pretty much valueless

So this situation might lend itself to a nice FAQ question Something like "How do I isolate site and machine specific information during a build?" And the solution can tell them how to use a site.conf file. Scott -Original Message- From: yocto-boun...@yoctoproject.org [mailto:yocto

Re: [yocto] the current yocto FAQ is pretty much valueless

On Tue, 26 Jun 2012, Paul Eggleton wrote: > On Tuesday 26 June 2012 12:51:15 Robert P. J. Day wrote: > > On Tue, 26 Jun 2012, Paul Eggleton wrote: > > > On Tuesday 26 June 2012 12:26:28 Robert P. J. Day wrote: > > > > i thought that was the technique for centralizing personal config > > > > > >

Re: [yocto] the current yocto FAQ is pretty much valueless

On Tuesday 26 June 2012 12:51:15 Robert P. J. Day wrote: > On Tue, 26 Jun 2012, Paul Eggleton wrote: > > On Tuesday 26 June 2012 12:26:28 Robert P. J. Day wrote: > > > i thought that was the technique for centralizing personal config > > > > > > preferences that you *didn't* want to manually cop

Re: [yocto] the current yocto FAQ is pretty much valueless

On Tue, 26 Jun 2012, Tomas Frydrych wrote: > Kooen's cheeky point is worth keeping in mind though; the Yocto > naming semantics is not very helpful ;-) Specifically most of the > questions being asked on the Yocto list are about Poky, not Yocto, > followed by questions about meta-yocto, not Yocto-

Re: [yocto] the current yocto FAQ is pretty much valueless

On Tue, 26 Jun 2012, Paul Eggleton wrote: > On Tuesday 26 June 2012 12:26:28 Robert P. J. Day wrote: > > i thought that was the technique for centralizing personal config > > preferences that you *didn't* want to manually copy into every > > local.conf file you created. if you add that personal

Re: [yocto] Yocto weekly bug trend charts -- WW25

Thanks for adding the annotation to the WDD chart on how you compute it. :-) >-Original Message- >From: yocto-boun...@yoctoproject.org [mailto:yocto- >boun...@yoctoproject.org] On Behalf Of Xu, Jiajun >Sent: Monday, June 25, 2012 9:33 PM >To: yocto@yoctoproject.org >Subject: [yocto] Yocto

Re: [yocto] the current yocto FAQ is pretty much valueless

On 26/06/12 17:06, Paul Eggleton wrote: > On Tuesday 26 June 2012 08:46:45 Darren Hart wrote: >> On 06/26/2012 03:09 AM, Paul Eggleton wrote: >>> I suggested to Scott R previously that it might be worth having a project >>> FAQ (i.e., what is this project about, what is it intended to be used for >

Re: [yocto] the current yocto FAQ is pretty much valueless

On Tuesday 26 June 2012 12:26:28 Robert P. J. Day wrote: > i thought that was the technique for centralizing personal config > preferences that you *didn't* want to manually copy into every > local.conf file you created. if you add that personal content into > each local.conf, then of course you

Re: [yocto] Yocto Development Manual Appendix B question

I am going to run through the B.1 example verbatim from the "current" version of the manual and see what happens. Scott -Original Message- From: Bruce Ashfield [mailto:bruce.ashfi...@windriver.com] Sent: Tuesday, June 26, 2012 9:28 AM To: Rifenbark, Scott M Cc: jfabernathy; yocto@yoctop

Re: [yocto] Yocto Development Manual Appendix B question

On 12-06-26 12:26 PM, Rifenbark, Scott M wrote: This is a good point. In looking at the example it does not say what branch you should be dealing with for poky-extras. And I'm configuring a test right now and will create a denzil branch, once I see it works. Cheers, Bruce -Original M

Re: [yocto] Yocto Development Manual Appendix B question

This is a good point. In looking at the example it does not say what branch you should be dealing with for poky-extras. -Original Message- From: Bruce Ashfield [mailto:bruce.ashfi...@windriver.com] Sent: Tuesday, June 26, 2012 9:24 AM To: jfabernathy Cc: Rifenbark, Scott M; yocto@yoctop

Re: [yocto] the current yocto FAQ is pretty much valueless

On Tue, 26 Jun 2012, Paul Eggleton wrote: > On Tuesday 26 June 2012 11:45:50 Robert P. J. Day wrote: > > since the ubiquitous reaction to complaining about something is > > always, "don't just whine, do something about it," i'm doing that. > > i've started a personal yocto FAQ, based on question

Re: [yocto] Yocto Development Manual Appendix B question

On 12-06-26 12:11 PM, jfabernathy wrote: On 06/26/2012 12:04 PM, Bruce Ashfield wrote: On 12-06-26 12:00 PM, jfabernathy wrote: On 06/26/2012 10:56 AM, Rifenbark, Scott M wrote: Bruce, Should the example note this? Would it be best to specifically say to uncomment that SRC_URI line? Scott I

Re: [yocto] the current yocto FAQ is pretty much valueless

On Tuesday 26 June 2012 11:45:50 Robert P. J. Day wrote: > since the ubiquitous reaction to complaining about something is > always, "don't just whine, do something about it," i'm doing that. > i've started a personal yocto FAQ, based on questions either i've > asked myself, or colleagues or clie

Re: [yocto] Yocto Development Manual Appendix B question

On 06/26/2012 12:04 PM, Bruce Ashfield wrote: On 12-06-26 12:00 PM, jfabernathy wrote: On 06/26/2012 10:56 AM, Rifenbark, Scott M wrote: Bruce, Should the example note this? Would it be best to specifically say to uncomment that SRC_URI line? Scott I think some text needs to be added. I unco

Re: [yocto] the current yocto FAQ is pretty much valueless

On Tuesday 26 June 2012 08:46:45 Darren Hart wrote: > On 06/26/2012 03:09 AM, Paul Eggleton wrote: > > I suggested to Scott R previously that it might be worth having a project > > FAQ (i.e., what is this project about, what is it intended to be used for > > etc.) and a separate technical FAQ which

Re: [yocto] Yocto Development Manual Appendix B question

On 12-06-26 12:00 PM, jfabernathy wrote: On 06/26/2012 10:56 AM, Rifenbark, Scott M wrote: Bruce, Should the example note this? Would it be best to specifically say to uncomment that SRC_URI line? Scott I think some text needs to be added. I uncommented the SRC_URI line and I still fail build

Re: [yocto] Yocto Development Manual Appendix B question

On 06/26/2012 10:56 AM, Rifenbark, Scott M wrote: Bruce, Should the example note this? Would it be best to specifically say to uncomment that SRC_URI line? Scott I think some text needs to be added. I uncommented the SRC_URI line and I still fail building the image. The failure is related t

Re: [yocto] Yocto Development Manual Appendix B question

On 12-06-26 10:56 AM, Rifenbark, Scott M wrote: Bruce, Should the example note this? Would it be best to specifically say to uncomment that SRC_URI line? It's worth noting, and I can make sure that the comments in the recipes reflect this as well. My comments within the individual bbappends

Re: [yocto] the current yocto FAQ is pretty much valueless

Great! Thanks Robert. -Original Message- From: Robert P. J. Day [mailto:rpj...@crashcourse.ca] Sent: Tuesday, June 26, 2012 8:46 AM To: Rifenbark, Scott M Cc: Koen Kooi; Yocto discussion list Subject: RE: [yocto] the current yocto FAQ is pretty much valueless On Tue, 26 Jun 2012, Rifenb

Re: [yocto] how many meta-toolchain-* targets are there?

On Tue, 26 Jun 2012, Khem Raj wrote: > On Tue, Jun 26, 2012 at 1:15 AM, Robert P. J. Day > wrote: > > > >  something that could be cleared up a bit in the docs ... how many > > toolchain-related targets are there? > > > >  for instance, running bitbake suggests that common targets include > > me

Re: [yocto] the current yocto FAQ is pretty much valueless

On 06/26/2012 03:09 AM, Paul Eggleton wrote: > On Tuesday 26 June 2012 05:09:34 Robert P. J. Day wrote: >> in other words, a *good* FAQ might be: >> >> "how can i use the yocto prebuilt toolchains to save build time?" >> >> a *bad* FAQ would be: >> >> "Does the Yocto Project have a special go

Re: [yocto] how many meta-toolchain-* targets are there?

On Tue, Jun 26, 2012 at 1:15 AM, Robert P. J. Day wrote: > >  something that could be cleared up a bit in the docs ... how many > toolchain-related targets are there? > >  for instance, running bitbake suggests that common targets include > meta-toolchain and meta-toolchain-sdk.  on the other hand

Re: [yocto] the current yocto FAQ is pretty much valueless

On Tue, 26 Jun 2012, Rifenbark, Scott M wrote: > Thanks all - I enjoyed the rant. The obvious point is that the FAQ > needs attention. A good thing to do would be if you have a question > that you would like included in a "good" FAQ, such as the one > mentioned by Robert about how to add a singl

Re: [yocto] BSP for taskit stamp9g20

On 12-06-26 10:56 AM, Markus Hubig wrote: Yhea! My first successful build! Thank you very much! nice! and no problem at all. Cheers, Bruce On Tue, Jun 26, 2012 at 4:00 PM, Bruce Ashfield wrote: On 12-06-26 09:49 AM, Markus Hubig wrote: On Tue, Jun 26, 2012 at 3:19 PM, Bruce Ashfield

Re: [yocto] BSP for taskit stamp9g20

Yhea! My first successful build! Thank you very much! On Tue, Jun 26, 2012 at 4:00 PM, Bruce Ashfield wrote: > On 12-06-26 09:49 AM, Markus Hubig wrote: >> >> On Tue, Jun 26, 2012 at 3:19 PM, Bruce Ashfield >>  wrote: >>> >>> >>> On 12-06-26 07:08 AM, Markus Hubig wrote: AT91SAM9

Re: [yocto] Yocto Development Manual Appendix B question

Bruce, Should the example note this? Would it be best to specifically say to uncomment that SRC_URI line? Scott -Original Message- From: yocto-boun...@yoctoproject.org [mailto:yocto-boun...@yoctoproject.org] On Behalf Of Bruce Ashfield Sent: Tuesday, June 26, 2012 7:54 AM To: jfabern

Re: [yocto] Yocto Development Manual Appendix B question

On 12-06-26 10:52 AM, jfabernathy wrote: In the example in The Developement Manual v1.2 in Appendix B Section B.1.7, it states that you need to put in the statement: KSRC_linux_yocto_3_2 ?="/home/scottrif/linux-yocto-3.2.git" into the appropriate .bbappend file way now in the poky-extra directo

[yocto] Yocto Development Manual Appendix B question

In the example in The Developement Manual v1.2 in Appendix B Section B.1.7, it states that you need to put in the statement: KSRC_linux_yocto_3_2 ?= "/home/scottrif/linux-yocto-3.2.git" into the appropriate .bbappend file way now in the poky-extra directory structure. If I look at that file,

Re: [yocto] the current yocto FAQ is pretty much valueless

Thanks all - I enjoyed the rant. The obvious point is that the FAQ needs attention. A good thing to do would be if you have a question that you would like included in a "good" FAQ, such as the one mentioned by Robert about how to add a single package, put the question up on this list or actual

Re: [yocto] how many meta-toolchain-* targets are there?

toolchain-gmae is exactly the toolchain-sdk. qte is for embedded qt "Robert P. J. Day" 编写： something that could be cleared up a bit in the docs ... how many toolchain-related targets are there? for instance, running bitbake suggests that common targets include meta-toolchain and meta-toolc

Re: [yocto] BSP for taskit stamp9g20

On 12-06-26 09:49 AM, Markus Hubig wrote: On Tue, Jun 26, 2012 at 3:19 PM, Bruce Ashfield wrote: On 12-06-26 07:08 AM, Markus Hubig wrote: AT91SAM9G20 based CPU board). This is when I came across the YoctoProject. Now I'm trying to build a BSP Layer for this Board. There are a lot of docum

[yocto] Fwd: BSP for taskit stamp9g20

On Tue, Jun 26, 2012 at 3:19 PM, Bruce Ashfield wrote: > > On 12-06-26 07:08 AM, Markus Hubig wrote: >> >> AT91SAM9G20 based CPU board). This is when I came across the YoctoProject. >> Now I'm trying to build a BSP Layer for this Board. >> >> There are a lot of documentation out there, but I still

Re: [yocto] BSP for taskit stamp9g20

On 12-06-26 07:08 AM, Markus Hubig wrote: Hello @all, as part of my bachelor thesis, I'm in the process of creating a custom Linux OS for the taskit Stamp9G20 (a small AT91SAM9G20 based CPU board). This is when I came across the YoctoProject

Re: [yocto] the current yocto FAQ is pretty much valueless

Op 26 jun. 2012, om 11:09 heeft Robert P. J. Day het volgende geschreven: > > i mentioned this to scott rifenbark privately a few days ago, but i > figured i might as well antagonize a few people on the list by saying > it publicly -- the yocto FAQ as it stands is pretty much worthless. > > h

[yocto] BSP for taskit stamp9g20

Hello @all, as part of my bachelor thesis, I'm in the process of creating a custom Linux OS for the taskit Stamp9G20(a small AT91SAM9G20 based CPU board). This is when I came across the YoctoProject. Now I'm trying to build a BSP Layer for this

Re: [yocto] the current yocto FAQ is pretty much valueless

On Tue, 26 Jun 2012, Paul Eggleton wrote: > On Tuesday 26 June 2012 05:09:34 Robert P. J. Day wrote: > > in other words, a *good* FAQ might be: > > > > "how can i use the yocto prebuilt toolchains to save build time?" > > > > a *bad* FAQ would be: > > > > "Does the Yocto Project have a special

Re: [yocto] the current yocto FAQ is pretty much valueless

On Tuesday 26 June 2012 05:09:34 Robert P. J. Day wrote: > in other words, a *good* FAQ might be: > > "how can i use the yocto prebuilt toolchains to save build time?" > > a *bad* FAQ would be: > > "Does the Yocto Project have a special governance model, or is it > managed as an open source

Re: [yocto] the current yocto FAQ is pretty much valueless

On 26/06/12 10:09, Robert P. J. Day wrote: > A bad Frequently Asked Questions (FAQ) sheet is one that is composed > not of the questions people actually ask, but of the questions the > FAQ's author wishes people would ask. Perhaps you've seen the type > before: Nice quote, but unfortunately based

Re: [yocto] the current yocto FAQ is pretty much valueless

On 26/06/12 10:09, Robert P. J. Day wrote: snip... in other words, a *good* FAQ might be: "how can i use the yocto prebuilt toolchains to save build time?" a *bad* FAQ would be: "Does the Yocto Project have a special governance model, or is it managed as an open source project?"

[yocto] the current yocto FAQ is pretty much valueless

i mentioned this to scott rifenbark privately a few days ago, but i figured i might as well antagonize a few people on the list by saying it publicly -- the yocto FAQ as it stands is pretty much worthless. https://wiki.yoctoproject.org/wiki/FAQ by way of explanation, i'll reproduce the fir

[yocto] how does one use a prebuilt toolchain from the toolchain/ directory?

it sounds like a trivial question whose answer should be easy to find, but surprisingly, it isn't. if a user wants to save all that toolchain-building time and take advantage of an existing toolchain, what to do? the ADT user's guide *sort of* addresses that, but in a somewhat confusing way:

[yocto] how many meta-toolchain-* targets are there?

something that could be cleared up a bit in the docs ... how many toolchain-related targets are there? for instance, running bitbake suggests that common targets include meta-toolchain and meta-toolchain-sdk. on the other hand, the ADT manual makes no reference to meta-toolchain-sdk but *doe

Re: [yocto] Porting of specific Kernel/Driver into yocto.

Hi Chris, No, /etc/initab does not contain any reference to tty0(wrong typed in last mail). Best Regards, Om Prakash Pal From: Chris Tapp [opensou...@keylevel.com] Sent: Tuesday, June 26, 2012 12:52 PM To: Om Prakash PAL Cc: Khem Raj; yocto@yoctoproject.or

Re: [yocto] Porting of specific Kernel/Driver into yocto.

Hi Chris, No, /etc/initab does not contain any reference to inittab. please find the attched /etc/initab file for more information. Best Regards, Om Prakash Pal => From: Chris Tapp [opensou...@keylevel.com] Sent: Tuesday, Ju

Re: [yocto] Porting of specific Kernel/Driver into yocto.

On 26 Jun 2012, at 06:33, Om Prakash PAL wrote: > Hi khem, > on target, etc/ does not contain securetty. What about /etc/inittab? Does this contain any references to tty0? > Best Regards, > Om Prakash Pal > > From: Khem Raj [raj.k...@gmail.com] > Sent: Mo

Re: [yocto] Selecting gcc version

On 26 Jun 2012, at 02:36, Khem Raj wrote: > On Mon, Jun 25, 2012 at 3:46 PM, Chris Tapp wrote: >> >> >> Well, that proves it's not the compiler. Still fails to boot, even though >> the toolchain that's supposed to work is 4.5.1. Does 32-bit / 64-bit host >> make a difference? > > host shoul