[yocto] Re-Build virtual/kernel
Hello All, I'm use yocto to create a linux for imx28, with meta-fsl-arm and meta-openembedded. Until now, every thing is ok, I Have a core-image-minimal-imx28evk.sdcard that working in the machine. My problem is that when I try to add some things in the kernel configuration, I feel like the system build dont generate a new uImage file or the thing that I selected in the Kernel dont be atached in the core-image-minimal-imx28evk.sdcard! What I did is: *...tmp/deploy/images$ ls * *-rw-r--r-- 1 raul raul 2511696 2012-08-15 16:23 uImage-2.6.35.3-r24-imx28evk-20120815191927.bin* *lrwxrwxrwx 1 raul raul47 2012-08-15 16:23 uImage-imx28evk.bin -> uImage-2.6.35.3-r24-imx28evk-20120815191927.bin* then: *bitbake -c menuconfig virtual/kernel* *bitbake -c patch virtual/kernel* *bitbake -c compile virtual/kernel* *bitbake virtual/kernel* and I'm looking again: *...tmp/deploy/images$ ls * *-rw-r--r-- 1 raul raul 2511696 2012-08-15 16:23 uImage-2.6.35.3-r24-imx28evk-20120815191927.bin* *lrwxrwxrwx 1 raul raul47 2012-08-15 16:23 uImage-imx28evk.bin -> uImage-2.6.35.3-r24-imx28evk-20120815191927.bin* Some One can explain to me what is the correct way to re-build the virtual/kenel target? Thanks for all Help! -- *Raul Rosetto Muñoz* ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Terminology Question for Kernels
On 12-08-15 04:29 PM, Rifenbark, Scott M wrote: Hi, Need some opinions here What is the best way to generically refer to one of our kernels in the source repository area. Right now, they are all grouped under the heading "Yocto Linux Kernel." They are individually named linux-yocto-. In the kernel manual, we refer to them collectively as a "Yocto Project Kernel." I would like to have a single way to reference these kernels we deliver. I don't have a strong opinion. So either Yocto Linux Kernel or Yocto Project Kernel seem fine to me, we could be more precise, but I'd rather keep it simple. Cheers, Bruce Thanks, Scott *Scott Rifenbark*** Intel Corporation Yocto Project Documentation 503.712.2702 503.341.0418 (cell) ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] [PATCH 1/3] - Code clean-up & refactoring on Yocto-BSP pages & wizards
---
.../sdk/remotetools/wizards/bsp/MainPage.java | 261 +++-
.../remotetools/wizards/bsp/PropertiesPage.java| 26 +-
.../remotetools/wizards/bsp/YoctoBSPWizard.java| 33 +--
3 files changed, 152 insertions(+), 168 deletions(-)
diff --git
a/plugins/org.yocto.sdk.remotetools/src/org/yocto/sdk/remotetools/wizards/bsp/MainPage.java
b/plugins/org.yocto.sdk.remotetools/src/org/yocto/sdk/remotetools/wizards/bsp/MainPage.java
index d80dd75..b729ad1 100644
---
a/plugins/org.yocto.sdk.remotetools/src/org/yocto/sdk/remotetools/wizards/bsp/MainPage.java
+++
b/plugins/org.yocto.sdk.remotetools/src/org/yocto/sdk/remotetools/wizards/bsp/MainPage.java
@@ -20,24 +20,21 @@ import org.eclipse.core.runtime.IStatus;
import org.eclipse.core.runtime.Status;
import org.eclipse.jface.wizard.WizardPage;
import org.eclipse.swt.SWT;
-import org.eclipse.swt.widgets.Event;
import org.eclipse.swt.events.ModifyEvent;
import org.eclipse.swt.events.ModifyListener;
import org.eclipse.swt.events.SelectionAdapter;
import org.eclipse.swt.events.SelectionEvent;
import org.eclipse.swt.layout.GridData;
import org.eclipse.swt.layout.GridLayout;
-import org.eclipse.swt.widgets.Widget;
import org.eclipse.swt.widgets.Button;
import org.eclipse.swt.widgets.Combo;
import org.eclipse.swt.widgets.Composite;
import org.eclipse.swt.widgets.Control;
import org.eclipse.swt.widgets.DirectoryDialog;
-
+import org.eclipse.swt.widgets.Event;
import org.eclipse.swt.widgets.Label;
import org.eclipse.swt.widgets.Text;
-
-
+import org.eclipse.swt.widgets.Widget;
import org.yocto.sdk.remotetools.YoctoBspElement;
/**
@@ -47,10 +44,7 @@ import org.yocto.sdk.remotetools.YoctoBspElement;
* @author jzhang
*/
public class MainPage extends WizardPage {
- public static final String PAGE_NAME = "Main";
- private static final String META_DATA_LOC = "MetadataLoc";
- private static final String BSP_OUT_LOC = "BspOutLoc";
- private static final String BUILD_DIR_LOC = "BuilddirLoc";
+ public static final String PAGE_NAME = "Main";
private static final String KARCH_CMD = "yocto-bsp list karch";
private static final String QARCH_CMD = "yocto-bsp list qemu property
qemuarch";
private static final String BSP_SCRIPT = "yocto-bsp";
@@ -59,27 +53,31 @@ public class MainPage extends WizardPage {
private static final String PROPERTIES_FILE = "/tmp/properties.json";
private Button btnMetadataLoc;
- private Button btnBspOutLoc;
- private Button btnBuilddirLoc;
private Text textMetadataLoc;
+ private Label labelMetadata;
+
+ private Button btnBspOutputLoc;
+ private Text textBspOutputLoc;
+ private Label labelBspOutput;
+
+ private Button btnBuildLoc;
+ private Text textBuildLoc;
+ private Label labelBuildLoc;
+
private Text textBspName;
- private Text textBspOutLoc;
- private Text textBuilddirLoc;
- private Combo karchCombo;
- private Combo qarchCombo;
- private Label metadata_label;
- private Label builddir_label;
- private Label bspname_label;
- private Label bspout_label;
- private Label karch_label;
- private Label qarch_label;
+ private Label labelBspName;
+
+ private Combo comboKArch;
+ private Label labelKArch;
+
+ private Combo comboQArch;
+ private Label labelQArch;
private YoctoBspElement bspElem;
public MainPage(YoctoBspElement element) {
super(PAGE_NAME, "yocto-bsp main page", null);
- //setTitle("Yocto-bsp main page");
setMessage("Enter the required fields(with *) to create new
Yocto Project BSP!");
this.bspElem = element;
}
@@ -91,74 +89,98 @@ public class MainPage extends WizardPage {
GridLayout layout = new GridLayout(2, false);
composite.setLayout(layout);
- gd.horizontalSpan= 2;
+ gd.horizontalSpan = 2;
composite.setLayoutData(gd);
- metadata_label = new Label(composite, SWT.NONE);
- metadata_label.setText("Meta_data location*: ");
+ labelMetadata = new Label(composite, SWT.NONE);
+ labelMetadata.setText("Meta_data location*: ");
Composite textContainer = new Composite(composite, SWT.NONE);
textContainer.setLayout(new GridLayout(2, false));
textContainer.setLayoutData(new GridData(SWT.FILL, SWT.CENTER,
true, false));
- textMetadataLoc =
(Text)addTextControl(textContainer,META_DATA_LOC, "");
+ textMetadataLoc = (Text)addTextControl(textContainer, "");
textMetadataLoc.setEnabled(false);
textMetadataLoc.addModifyListener(new ModifyListener() {
public void modifyTex
[yocto] [PATCH 2/3] [PATCH]Fixed bug 2922 - Yocto-BSP main page checks for build/output location generate error pop-up on properties pages
checks for build location :
- if no location is specified, use metadataLocation/build
- if a directory is specified
- if it does not exist -> create it under metadataLocation
- if it does exist -> oe-init-build-env - create conf/ hierachy
- skip if already there
- collect error output for build directory creation
- checks for output location :
- if the output directory already exists -> show error & disable
next(the yocto-bsp script will fail if the directory already exists)
Signed-off-by: Ioana Grigoropol
---
.../sdk/remotetools/wizards/bsp/MainPage.java | 96 +---
1 file changed, 64 insertions(+), 32 deletions(-)
diff --git
a/plugins/org.yocto.sdk.remotetools/src/org/yocto/sdk/remotetools/wizards/bsp/MainPage.java
b/plugins/org.yocto.sdk.remotetools/src/org/yocto/sdk/remotetools/wizards/bsp/MainPage.java
index b729ad1..e5a21d1 100644
---
a/plugins/org.yocto.sdk.remotetools/src/org/yocto/sdk/remotetools/wizards/bsp/MainPage.java
+++
b/plugins/org.yocto.sdk.remotetools/src/org/yocto/sdk/remotetools/wizards/bsp/MainPage.java
@@ -251,28 +251,33 @@ public class MainPage extends WizardPage {
labelQArch.setEnabled(false);
comboQArch.setEnabled(false);
}
+} else if (widget == textBuildLoc){
+status = checkBuildDir();
}
-
-checkBuildDir();
-
-String build_dir = textBuildLoc.getText();
-String output_dir = textBspOutputLoc.getText();
-String bsp_name = textBspName.getText();
-if (!output_dir.isEmpty() && output_dir.matches(build_dir)) {
-status = new Status(IStatus.ERROR, "not_used", 0,
-"You've set BSP output directory the
same as build directory, please leave output directory empty for this
scenario!", null);
-}
+String buildDir = textBuildLoc.getText();
+String outputDir = textBspOutputLoc.getText();
+String bspName = textBspName.getText();
-if (build_dir.startsWith(metadataLoc) && output_dir.isEmpty()
&& !bsp_name.isEmpty()) {
-String bsp_dir_str = metadataLoc + "/meta-" + bsp_name;
-File bsp_dir = new File(bsp_dir_str);
-if (bsp_dir.exists()) {
+if (!outputDir.isEmpty()){
+if (outputDir.matches(buildDir)) {
+status = new Status(IStatus.ERROR, "not_used",
0,
+"You've set BSP output
directory the same as build directory, please leave output directory empty for
this scenario!", null);
+} else {
+File outputDirectory = new File(outputDir);
+if (outputDirectory.exists()){
+ status = new Status(IStatus.ERROR,
"not_used", 0,
+"Your BSP output
directory points to an exiting directory!", null);
+}
+}
+} else if (buildDir.startsWith(metadataLoc) &&
!bspName.isEmpty()) {
+String bspDirStr = metadataLoc + "/meta-" + bspName;
+File bspDir = new File(bspDirStr);
+if (bspDir.exists()) {
status = new Status(IStatus.ERROR, "not_used",
0,
-"Your BSP with name: " +
bsp_name + " already exist under directory: " + bsp_dir_str + ", please change
your bsp name!", null);
+"Your BSP with name: " +
bspName + " already exist under directory: " + bspDirStr + ", please change
your bsp name!", null);
}
}
-validatePage();
if (status.getSeverity() == IStatus.ERROR)
setErrorMessage(status.getMessage());
@@ -281,25 +286,52 @@ public class MainPage extends WizardPage {
canFlipToNextPage();
}
- private void checkBuildDir() {
- String metadata_dir = textMetadataLoc.getText();
- String builddir_str = textBuildLoc.getText();
+ private Status checkBuildDir() {
+
+ String metadataLoc = textMetadataLoc.getText();
+ String buildLoc = textBuildLoc.getText();
+
+ if (buildLoc.isEmpty()) {
+buildLoc = metadataLoc + "/build";
+return cre
[yocto] [PATCH 3/3] [PATCH] Processes that execute shell commands block the Yocto-BSP interface
- send processes that execute shell commands in the background and show
progress dialog
- retrieve status of the background executions & items collected
Signed-off-by: Ioana Grigoropol
---
.../sdk/remotetools/wizards/bsp/MainPage.java |1 -
.../remotetools/wizards/bsp/PropertiesPage.java| 196
2 files changed, 123 insertions(+), 74 deletions(-)
diff --git
a/plugins/org.yocto.sdk.remotetools/src/org/yocto/sdk/remotetools/wizards/bsp/MainPage.java
b/plugins/org.yocto.sdk.remotetools/src/org/yocto/sdk/remotetools/wizards/bsp/MainPage.java
index e5a21d1..bd80ed4 100644
---
a/plugins/org.yocto.sdk.remotetools/src/org/yocto/sdk/remotetools/wizards/bsp/MainPage.java
+++
b/plugins/org.yocto.sdk.remotetools/src/org/yocto/sdk/remotetools/wizards/bsp/MainPage.java
@@ -313,7 +313,6 @@ public class MainPage extends WizardPage {
// system.property usually points to the location from where
eclipse was started
String createBuildDirCmd = "cd " + metadataDir + ";source " +
metadataDir + "/oe-init-build-env " + buildLoc;
- System.out.println(createBuildDirCmd);
try {
ProcessBuilder builder = new ProcessBuilder(new
String[] {"sh", "-c", createBuildDirCmd});
Process proc = builder.start();
diff --git
a/plugins/org.yocto.sdk.remotetools/src/org/yocto/sdk/remotetools/wizards/bsp/PropertiesPage.java
b/plugins/org.yocto.sdk.remotetools/src/org/yocto/sdk/remotetools/wizards/bsp/PropertiesPage.java
index 4661b37..38af7b9 100644
---
a/plugins/org.yocto.sdk.remotetools/src/org/yocto/sdk/remotetools/wizards/bsp/PropertiesPage.java
+++
b/plugins/org.yocto.sdk.remotetools/src/org/yocto/sdk/remotetools/wizards/bsp/PropertiesPage.java
@@ -11,7 +11,6 @@
package org.yocto.sdk.remotetools.wizards.bsp;
import java.io.BufferedReader;
-import java.io.InputStream;
import java.io.InputStreamReader;
import java.util.ArrayList;
import java.util.Enumeration;
@@ -19,7 +18,10 @@ import java.util.HashSet;
import java.util.Hashtable;
import java.util.Iterator;
+import org.eclipse.core.runtime.IProgressMonitor;
import org.eclipse.jface.dialogs.MessageDialog;
+import org.eclipse.jface.dialogs.ProgressMonitorDialog;
+import org.eclipse.jface.operation.IRunnableWithProgress;
import org.eclipse.jface.wizard.WizardPage;
import org.eclipse.swt.SWT;
import org.eclipse.swt.custom.ScrolledComposite;
@@ -59,6 +61,9 @@ public class PropertiesPage extends WizardPage {
private static final String NEW_KBRANCH_NAME = "new_kbranch";
private static final String QARCH_NAME = "qemuarch";
+ private static final String KERNEL_CHOICES = "choices";
+ private static final String KERNEL_BRANCHES = "branches";
+
private Hashtable propertyControlMap;
HashSet properties;
private Composite composite;
@@ -81,9 +86,8 @@ public class PropertiesPage extends WizardPage {
}
public void onEnterPage(YoctoBspElement element) {
- String[] values;
if (!element.getValidPropertiesFile()) {
- setErrorMessage("There's no valid properties file
created, please choose \"Back\" to reselect kernel architectur!");
+ setErrorMessage("There's no valid properties file
created, please choose \"Back\" to reselect kernel architecture!");
return;
}
@@ -131,9 +135,7 @@ public class PropertiesPage extends WizardPage {
newButton.setSelection(true);
existingButton.setSelection(false);
- values = getValues(KERNEL_CHOICE);
- if (values != null)
- kcCombo.setItems(values);
+ updateKernelValues(KERNEL_CHOICES, KERNEL_CHOICE);
}
try {
@@ -194,10 +196,9 @@ public class PropertiesPage extends WizardPage {
new Label (choiceContainer,
SWT.NONE).setText(name+":");
Combo combo = new
Combo(choiceContainer, SWT.BORDER | SWT.READ_ONLY);
combo.setLayout(new
FillLayout());
-
- values = getValues(name);
- if (values != null)
- combo.setItems(values);
+
+
updateKernelValues(KERNEL_CHOICES, name);
+
propertyControlMap.put(propElem, (Control)combo);
[yocto] [PATCH] psplash: use correct blue offset value for BGR888
Author: Aws Ismail
Date: Thu Aug 16 11:06:13 2012 -0400
Use correct blue offset value for BGR888
fs->blue_offset should be compared to 16 instead
of 8 in order to detect BGR.
Credit goes to Ulrich Feichter
for detecting this.
Signed-off-by: Aws Ismail
---
psplash-fb.c |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/psplash-fb.c b/psplash-fb.c
index 71740cd..f65d67e 100644
--- a/psplash-fb.c
+++ b/psplash-fb.c
@@ -185,7 +185,7 @@ psplash_fb_new (int angle)
fb->rgbmode = RGB888;
} else if (fb->red_offset == 0 && fb->red_length == 8 &&
fb->green_offset == 8 && fb->green_length == 8 &&
- fb->blue_offset == 8 && fb->blue_length == 8) {
+ fb->blue_offset == 16 && fb->blue_length == 8) {
fb->rgbmode = BGR888;
} else {
fb->rgbmode = GENERIC;
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
[yocto] Minutes: Yocto Project Technical Team Meeting - Tuesday, August 14, 2012 8:00 AM-9:00 AM (UTC-08:00) Pacific Time (US & Canada).
Attendees: Mark, Jessica, Ross, Beth, Saul, Kevin, MichaelH, JeffP, Nitin, Dave, LaurentiuS, Paul, Richard, ScottR, ChrisL, Bogdan, LaurentiuP, Bruce, Sean, Song Agenda: * Opens collection - 5 min (Song) * Yocto 1.3 status - 10 min (Song/team) https://wiki.yoctoproject.org/wiki/Yocto_Project_v1.3_Status -QA(Laurentiu): tested on the master last week. Have some bugs opened. No issue on qemu, HOB is clear, ADT has more issue. Most of the issues are in core build system. Will start testing on RC1 this week. Beth: which build did you test? Laurentiu: used some partial build and master. As long as we know the commit, we can start testing. - Release (Beth): ab/1.3 status . ab, one of ab's is not working well, will work on this today. There is a bug last week caused problem, has been corrected, will push that out to AB today. . 1.3 M3 is building on a new RC. So far so good, no major issues. - Status wiki page updated. Got CCB approval for high items we moved from M3 to future milestones. - Bug trend: open above-medium bugs are going up. There is a steeper uptick this week, that is due to our priority change to use new settings. Would like to ask the team/community to focus more on bug fixing. If anyone in the community has any free cycle, please try to help fix any bug you can help. * SWAT team rotation: Paul -> Jessica - 4 new members joined: LaurentiuP, LaurentiuS, MihaiL, StefanS * Opens - 10 min Richard: Bitbake console UI change - heads-up, this is about knotty and knotty-2, the idea is to fix that and make it a default. We talked about it in 1.2. Now we would like to make into 1.3. Plan is to get this in by the end of the week. * Team sharing - 20 min Michael: last week moved all public ip's to new spaces, which gave us better protection. Had to work on wired hours. 4am. Working with Beth to fix abs, documented how and why, trying to make more things automatic. Collaborating with laurentiuP on bug statistics. Updated all the kernels for service oriented machines. Bugzilla has issues with some queries. Coming week, solving AB scripts and IRC bugs. Saul: take the next batch in the next 24 hours, running a little behind on this. Has been dealing with issues with 1.3 release. Paul: worked on swat tasks last week, diagnosing issues. This week back to general bug fixing. Will send out an RFC for reworking some task recipes to make them more useful. If you have any suggestions, please let me know. Feedback we got: existing task recipes are not very useful. So will do some analysis and see what's missing. One obvious thing is that Obsolete tasks will be pulled out. Sean: a couple of guys in mentor are working on this. In a process integrating different things into Yocto.. Will collaborate more on this. ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] The +Yocto Project is seeking beta testers...
You received this message because Jeff Osier-Mixon shared it with yocto@yoctoproject.org. "The +Yocto Project is seeking beta testers for version 1.3. Please see the link for details." Accept the invitation to view the full post: https://plus.google.com/_/notifications/ngemlink?&emid=CLiSo7P46rECFcSWcAod5CIAAA&path=%2F115685581526580635799%2Fposts%2FTZjz3ktkx1M%3Fgpinv%3DAMIXal_c-x7nc7KevGuf63oikBWKmNZMGvloiCYqTAPBARrEc47wHpjrj_nd3H9aD2bIVzuJMCfbpl9c8RlwClQl09lSPSbOPM3d9wVjHVp2Un0VhDdxDIE&dt=1345078637940&uob=8 Google+ makes sharing on the web more like sharing in real life. Learn more: http://www.google.com/+/learnmore/ You received this message because Jeff Osier-Mixon shared it with yocto@yoctoproject.org. Click here to unsubscribe from these emails: https://plus.google.com/_/notifications/ngemlink?&emid=CLiSo7P46rECFcSWcAod5CIAAA&path=%2F_%2Fnonplus%2Femailsettings%3Fgpinv%3DAMIXal_c-x7nc7KevGuf63oikBWKmNZMGvloiCYqTAPBARrEc47wHpjrj_nd3H9aD2bIVzuJMCfbpl9c8RlwClQl09lSPSbOPM3d9wVjHVp2Un0VhDdxDIE%26est%3DADH5u8W9vx6MUt5Ei4PHmW4oTei8eLGjbtEtZ76yZor15IX9LZCukxV8E6YU31Px_yifscF3QWfZfhm4erMVAgdHjZh4alEn_AxnoIO1JjeAH6_7rtu7NzjNtC_7ndN6rr9nfCM9DuR2K7di7E4MHnQlyDMFokBh7w&dt=1345078637940&uob=8 ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] IMX 6 quad core development kit
Hi, Any suggestions for an IMX 6 quad core development kit? Has Yocto been tested on the IMX 6 ARM processor? Best regards, Elvis Dowson ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [PATCH 1/1] run-postinsts does not run any scripts
On 07/09/2012 05:19 AM, Kenneth Solbjerg wrote:
Hi
Sorry for any mistakes, but this is my first patch...
On my system (core-image-base, .deb package files), run-postinsts does
not run any scripts due to a failed test in run-postinsts.awk.
As dpkg is not actually installed on target, opkg is identified as the
pkgdir and that is not right...
Index:
poky-denzil-7.0/meta/recipes-devtools/dpkg/run-postinsts/run-postinsts.awk
===
---
poky-denzil-7.0.orig/meta/recipes-devtools/dpkg/run-postinsts/run-postinsts.awk
2012-07-05
13:00:23.026519188 +0200
+++ poky-denzil-7.0/meta/recipes-devtools/dpkg/run-postinsts/run-postinsts.awk
2012-07-05
13:00:48.054519384 +0200
@@ -7,7 +7,7 @@
#
BEGIN {
- rc=system("test -d /usr/dpkg/info/")
+ rc=system("test -d /var/lib/dpkg/info/")
if (rc==0)
pkgdir="/var/lib/dpkg/info"
else
Merged into OE-Core
Thanks
Sau!
--
Med venlig hilsen / Best regards
Kenneth Solbjerg
Software Specialist
Move Innovation
Web : http://www.moveinnovation.dk
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] IMX 6 quad core development kit
On Thu, Aug 16, 2012 at 12:33 PM, Elvis Dowson wrote: > Hi, >Any suggestions for an IMX 6 quad core development kit? Has Yocto been > tested on the IMX 6 ARM processor? https://github.com/Freescale/meta-fsl-arm has one imx6 board - not sure beyond that. Perhaps ping their mailing list: http://groups.google.com/group/meta-fsl-arm -M > > Best regards, > > Elvis Dowson > ___ > yocto mailing list > yocto@yoctoproject.org > https://lists.yoctoproject.org/listinfo/yocto ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Re-Build virtual/kernel
On Thu, Aug 16, 2012 at 7:11 AM, Raul Rosetto Munoz wrote: > Hello All, > > I'm use yocto to create a linux for imx28, with meta-fsl-arm and > meta-openembedded. > > Until now, every thing is ok, I Have a core-image-minimal-imx28evk.sdcard > that working in the machine. > > My problem is that when I try to add some things in the kernel > configuration, I feel like the system build dont generate a new uImage file > or the thing that I selected in the Kernel dont be atached in the > core-image-minimal-imx28evk.sdcard! > > What I did is: > > ...tmp/deploy/images$ ls > -rw-r--r-- 1 raul raul 2511696 2012-08-15 16:23 > uImage-2.6.35.3-r24-imx28evk-20120815191927.bin > lrwxrwxrwx 1 raul raul47 2012-08-15 16:23 uImage-imx28evk.bin -> > uImage-2.6.35.3-r24-imx28evk-20120815191927.bin > > then: > > bitbake -c menuconfig virtual/kernel > bitbake -c patch virtual/kernel > bitbake -c compile virtual/kernel > bitbake virtual/kernel Try bitbake -c compile virtual/kernel -f -M > > and I'm looking again: > > ...tmp/deploy/images$ ls > -rw-r--r-- 1 raul raul 2511696 2012-08-15 16:23 > uImage-2.6.35.3-r24-imx28evk-20120815191927.bin > lrwxrwxrwx 1 raul raul47 2012-08-15 16:23 uImage-imx28evk.bin -> > uImage-2.6.35.3-r24-imx28evk-20120815191927.bin > > Some One can explain to me what is the correct way to re-build the > virtual/kenel target? > > Thanks for all Help! > > -- > Raul Rosetto Muñoz > > ___ > yocto mailing list > yocto@yoctoproject.org > https://lists.yoctoproject.org/listinfo/yocto > ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] [PATCH 0/1][meta-intel] Cover letter to upgrade meta-cedartrail pvr driver to v1.0.2
From: Rahul Saxena Cover letter to upgrade meta-cedartrail pvr driver to v1.0.2 This update of the driver enables support for B3 stepping of Cedarview processor and also support for DP/eDP ports. Signed-off-by: Rahul Saxena -- The following changes since commit 2552a046878e4352595f6e081ad371538cceda10: meta-n450: explicitly specify KBRANCH we expect to use (2012-07-12 16:32:58 -0500) are available in the git repository at: git://git.pokylinux.org/meta-intel-contrib denzelv102checkin15augOK http://git.pokylinux.org/cgit.cgi/meta-intel-contrib/log/?h=denzelv102checkin15augOK Rahul Saxena (1): meta-cedartrail: update PVR graphics driver to version 1.0.2 meta-cedartrail/README |2 +- meta-cedartrail/conf/machine/cedartrail.conf |2 +- .../xorg-driver/cdv-pvr-driver.inc | 37 - .../xorg-driver/cdv-pvr-driver_1.0.2.bb| 143 .../xorg-driver/cdv-pvr-driver_1.0.bb | 99 -- .../recipes-kernel/linux/linux-yocto_3.0.bbappend |6 +- 6 files changed, 148 insertions(+), 141 deletions(-) delete mode 100644 meta-cedartrail/recipes-graphics/xorg-driver/cdv-pvr-driver.inc create mode 100644 meta-cedartrail/recipes-graphics/xorg-driver/cdv-pvr-driver_1.0.2.bb delete mode 100644 meta-cedartrail/recipes-graphics/xorg-driver/cdv-pvr-driver_1.0.bb -- 1.7.4.1 ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] [PATCH 1/1] meta-cedartrail: update PVR graphics driver to version 1.0.2
From: Rahul Saxena
This update of the driver enables support for B3 stepping of Cedarview
processor and also support for DP/eDP ports.
Signed-off-by: Rahul Saxena
---
meta-cedartrail/README |2 +-
meta-cedartrail/conf/machine/cedartrail.conf |2 +-
.../xorg-driver/cdv-pvr-driver.inc | 37 -
.../xorg-driver/cdv-pvr-driver_1.0.2.bb| 143
.../xorg-driver/cdv-pvr-driver_1.0.bb | 99 --
.../recipes-kernel/linux/linux-yocto_3.0.bbappend |6 +-
6 files changed, 148 insertions(+), 141 deletions(-)
delete mode 100644
meta-cedartrail/recipes-graphics/xorg-driver/cdv-pvr-driver.inc
create mode 100644
meta-cedartrail/recipes-graphics/xorg-driver/cdv-pvr-driver_1.0.2.bb
delete mode 100644
meta-cedartrail/recipes-graphics/xorg-driver/cdv-pvr-driver_1.0.bb
diff --git a/meta-cedartrail/README b/meta-cedartrail/README
index 493e831..715cad9 100755
--- a/meta-cedartrail/README
+++ b/meta-cedartrail/README
@@ -61,7 +61,7 @@ Power VR Graphics user-space driver binaries are covered by a
"Intel Free Distribution Binary License". The build of this driver
can be enabled by adding the following line to the local.conf file:
-LICENSE_FLAGS_WHITELIST += "license_cdv-pvr-driver_1.0"
+LICENSE_FLAGS_WHITELIST += "license_cdv-pvr-driver_1.0.2"
To enable the layer that does not support Power VR graphics
add the following to the local.conf file:
diff --git a/meta-cedartrail/conf/machine/cedartrail.conf
b/meta-cedartrail/conf/machine/cedartrail.conf
index dbd7d95..f00219e 100644
--- a/meta-cedartrail/conf/machine/cedartrail.conf
+++ b/meta-cedartrail/conf/machine/cedartrail.conf
@@ -19,4 +19,4 @@ PREFERRED_VERSION_xf86-input-evdev ?= "2.6.0"
SYSLINUX_OPTS = "serial 0 115200"
SERIAL_CONSOLE = "115200 ttyS0"
-APPEND += "console=ttyS0,115200 console=tty0"
+APPEND += "console=ttyS0,115200 console=tty0 vmalloc=256MB"
diff --git a/meta-cedartrail/recipes-graphics/xorg-driver/cdv-pvr-driver.inc
b/meta-cedartrail/recipes-graphics/xorg-driver/cdv-pvr-driver.inc
deleted file mode 100644
index 787c1fb..000
--- a/meta-cedartrail/recipes-graphics/xorg-driver/cdv-pvr-driver.inc
+++ /dev/null
@@ -1,37 +0,0 @@
-SUMMARY = "Cedartrail PowerVR Graphics Driver version [Gold] 1.0 binaries"
-DESCRIPTION = "2D, 3D and Media user space driver for Cedartrail platform \
-The binaries are covered by the Intel Free Distribution Binary License. \
-The user must make himself/herself aware of the Licensing terms \
-before enabling build of the Cedartrail PowerVR Graphics Driver via \
-this recipe. Please see the README in meta-cedartrail for instructions \
-for enabling the build of the driver "
-
-LICENSE_FLAGS = "license_${PN}_${PV}"
-LICENSE = "Intel Free Distribution Binary License"
-
-LIC_FILES_CHKSUM = " \
-
file://${S}/usr/share/doc/psb-video-cdv-0.16/license.txt;md5=b14d99f8d4ed664e9ce95057f0bb5b65
\
-
file://${S}/usr/share/doc/pvr-bin-cdv-1.7.788837_10/license.txt;md5=b14d99f8d4ed664e9ce95057f0bb5b65"
-
-INC_PR = "r1"
-
-DEPENDS = "rpm-native"
-
-FILES_${PN} += "${libdir}/dri ${libdir}/pvr/cdv/dri ${libdir}/pvr/cdv
${libdir}/xorg/modules/drivers"
-FILES_${PN}-dev += "${libdir}/dri ${libdir}/pvr/cdv/dri
${libdir}/xorg/modules/drivers"
-FILES_${PN}-dbg += "${libdir}/xorg/modules/drivers/.debug ${libdir}/dri/.debug
${libdir}/pvr/cdv/dri/.debug"
-
-FILES_${PN} += "${base_libdir}/firmware"
-FILES_${PN} += "${sysconfdir}/X11/xorg.conf.d"
-
-FILES_${PN} += "${libdir}/lib*.so"
-FILES_${PN}-dev += "${libdir}/lib*.so"
-FILES_${PN}-dbg += "${libdir}/.debug"
-
-FILES_${PN} += "${libdir}/pvr/cdv/xorg/modules/drivers"
-
-FILES_${PN} += "${datadir}/doc/psb-video-cdv-0.16/license.txt"
-FILES_${PN} += "${datadir}/doc/pvr-bin-cdv-1.7.788837_10/license.txt"
-
-
-
diff --git
a/meta-cedartrail/recipes-graphics/xorg-driver/cdv-pvr-driver_1.0.2.bb
b/meta-cedartrail/recipes-graphics/xorg-driver/cdv-pvr-driver_1.0.2.bb
new file mode 100644
index 000..047a7fd
--- /dev/null
+++ b/meta-cedartrail/recipes-graphics/xorg-driver/cdv-pvr-driver_1.0.2.bb
@@ -0,0 +1,143 @@
+SUMMARY = "Cedartrail PowerVR Graphics Driver version 1.0.2 binaries"
+DESCRIPTION = "2D, 3D and Media user space driver for Cedartrail platform \
+The binaries are covered by the Intel Free Distribution Binary License. \
+The user must make himself/herself aware of the Licensing terms \
+before enabling build of the Cedartrail PowerVR Graphics Driver via \
+this recipe. Please see the README in meta-cedartrail for instructions \
+for enabling the build of the driver "
+
+LICENSE_FLAGS = "license_${PN}_${PV}"
+LICENSE = "Intel Free Distribution Binary License"
+LIC_FILES_CHKSUM = " \
+
file://${S}/usr/share/doc/psb-video-cdv-${PSB-VIDEO-REV}/license.txt;md5=b14d99f8d4ed664e9ce95057f0bb5b65
\
+
file://${S}/usr/share/doc/pvr-bin-cdv-${PVR-BIN-REV_N}/license.txt;md5=b14d99f8d4ed664e9ce95057f0bb5b65"
+
+DEPENDS = "r
Re: [yocto] [PATCH 0/1][meta-intel] Cover letter to upgrade meta-cedartrail pvr driver to v1.0.2
The patch is for denzil branch of meta-intel. Thanks Rahul -Original Message- From: yocto-boun...@yoctoproject.org [mailto:yocto-boun...@yoctoproject.org] On Behalf Of rahul.sax...@intel.com Sent: Thursday, August 16, 2012 11:36 AM To: yocto@yoctoproject.org; Zanussi, Tom; bruce.ashfi...@windriver.com; Bodke, Kishore K Subject: [yocto] [PATCH 0/1][meta-intel] Cover letter to upgrade meta-cedartrail pvr driver to v1.0.2 From: Rahul Saxena Cover letter to upgrade meta-cedartrail pvr driver to v1.0.2 This update of the driver enables support for B3 stepping of Cedarview processor and also support for DP/eDP ports. Signed-off-by: Rahul Saxena -- The following changes since commit 2552a046878e4352595f6e081ad371538cceda10: meta-n450: explicitly specify KBRANCH we expect to use (2012-07-12 16:32:58 -0500) are available in the git repository at: git://git.pokylinux.org/meta-intel-contrib denzelv102checkin15augOK http://git.pokylinux.org/cgit.cgi/meta-intel-contrib/log/?h=denzelv102checkin15augOK Rahul Saxena (1): meta-cedartrail: update PVR graphics driver to version 1.0.2 meta-cedartrail/README |2 +- meta-cedartrail/conf/machine/cedartrail.conf |2 +- .../xorg-driver/cdv-pvr-driver.inc | 37 - .../xorg-driver/cdv-pvr-driver_1.0.2.bb| 143 .../xorg-driver/cdv-pvr-driver_1.0.bb | 99 -- .../recipes-kernel/linux/linux-yocto_3.0.bbappend |6 +- 6 files changed, 148 insertions(+), 141 deletions(-) delete mode 100644 meta-cedartrail/recipes-graphics/xorg-driver/cdv-pvr-driver.inc create mode 100644 meta-cedartrail/recipes-graphics/xorg-driver/cdv-pvr-driver_1.0.2.bb delete mode 100644 meta-cedartrail/recipes-graphics/xorg-driver/cdv-pvr-driver_1.0.bb -- 1.7.4.1 ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Re-Build virtual/kernel
I did all de comands with -c and do not work! Some one no some thing that I can try to update de uImage file? Thanks for the sugestion. 2012/8/16 McClintock Matthew-B29882 > On Thu, Aug 16, 2012 at 7:11 AM, Raul Rosetto Munoz > wrote: > > Hello All, > > > > I'm use yocto to create a linux for imx28, with meta-fsl-arm and > > meta-openembedded. > > > > Until now, every thing is ok, I Have a core-image-minimal-imx28evk.sdcard > > that working in the machine. > > > > My problem is that when I try to add some things in the kernel > > configuration, I feel like the system build dont generate a new uImage > file > > or the thing that I selected in the Kernel dont be atached in the > > core-image-minimal-imx28evk.sdcard! > > > > What I did is: > > > > ...tmp/deploy/images$ ls > > -rw-r--r-- 1 raul raul 2511696 2012-08-15 16:23 > > uImage-2.6.35.3-r24-imx28evk-20120815191927.bin > > lrwxrwxrwx 1 raul raul47 2012-08-15 16:23 uImage-imx28evk.bin -> > > uImage-2.6.35.3-r24-imx28evk-20120815191927.bin > > > > then: > > > > bitbake -c menuconfig virtual/kernel > > bitbake -c patch virtual/kernel > > bitbake -c compile virtual/kernel > > bitbake virtual/kernel > > Try > > bitbake -c compile virtual/kernel -f > > -M > > > > > and I'm looking again: > > > > ...tmp/deploy/images$ ls > > -rw-r--r-- 1 raul raul 2511696 2012-08-15 16:23 > > uImage-2.6.35.3-r24-imx28evk-20120815191927.bin > > lrwxrwxrwx 1 raul raul47 2012-08-15 16:23 uImage-imx28evk.bin -> > > uImage-2.6.35.3-r24-imx28evk-20120815191927.bin > > > > Some One can explain to me what is the correct way to re-build the > > virtual/kenel target? > > > > Thanks for all Help! > > > > -- > > Raul Rosetto Muñoz > > > > ___ > > yocto mailing list > > yocto@yoctoproject.org > > https://lists.yoctoproject.org/listinfo/yocto > > > -- *Raul Rosetto Muñoz* ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Re-Build virtual/kernel
What about the -f? -M On Thu, Aug 16, 2012 at 2:02 PM, Raul Rosetto Munoz wrote: > I did all de comands with -c and do not work! > > Some one no some thing that I can try to update de uImage file? > > Thanks for the sugestion. > > > > 2012/8/16 McClintock Matthew-B29882 >> >> On Thu, Aug 16, 2012 at 7:11 AM, Raul Rosetto Munoz >> wrote: >> > Hello All, >> > >> > I'm use yocto to create a linux for imx28, with meta-fsl-arm and >> > meta-openembedded. >> > >> > Until now, every thing is ok, I Have a >> > core-image-minimal-imx28evk.sdcard >> > that working in the machine. >> > >> > My problem is that when I try to add some things in the kernel >> > configuration, I feel like the system build dont generate a new uImage >> > file >> > or the thing that I selected in the Kernel dont be atached in the >> > core-image-minimal-imx28evk.sdcard! >> > >> > What I did is: >> > >> > ...tmp/deploy/images$ ls >> > -rw-r--r-- 1 raul raul 2511696 2012-08-15 16:23 >> > uImage-2.6.35.3-r24-imx28evk-20120815191927.bin >> > lrwxrwxrwx 1 raul raul47 2012-08-15 16:23 uImage-imx28evk.bin >> > -> >> > uImage-2.6.35.3-r24-imx28evk-20120815191927.bin >> > >> > then: >> > >> > bitbake -c menuconfig virtual/kernel >> > bitbake -c patch virtual/kernel >> > bitbake -c compile virtual/kernel >> > bitbake virtual/kernel >> >> Try >> >> bitbake -c compile virtual/kernel -f >> >> -M >> >> > >> > and I'm looking again: >> > >> > ...tmp/deploy/images$ ls >> > -rw-r--r-- 1 raul raul 2511696 2012-08-15 16:23 >> > uImage-2.6.35.3-r24-imx28evk-20120815191927.bin >> > lrwxrwxrwx 1 raul raul47 2012-08-15 16:23 uImage-imx28evk.bin >> > -> >> > uImage-2.6.35.3-r24-imx28evk-20120815191927.bin >> > >> > Some One can explain to me what is the correct way to re-build the >> > virtual/kenel target? >> > >> > Thanks for all Help! >> > >> > -- >> > Raul Rosetto Muñoz >> > >> > ___ >> > yocto mailing list >> > yocto@yoctoproject.org >> > https://lists.yoctoproject.org/listinfo/yocto >> > > > > > > -- > Raul Rosetto Muñoz > > ___ > yocto mailing list > yocto@yoctoproject.org > https://lists.yoctoproject.org/listinfo/yocto > ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Re-Build virtual/kernel
don't work. 2012/8/16 McClintock Matthew-B29882 > What about the -f? > > -M > > On Thu, Aug 16, 2012 at 2:02 PM, Raul Rosetto Munoz > wrote: > > I did all de comands with -c and do not work! > > > > Some one no some thing that I can try to update de uImage file? > > > > Thanks for the sugestion. > > > > > > > > 2012/8/16 McClintock Matthew-B29882 > >> > >> On Thu, Aug 16, 2012 at 7:11 AM, Raul Rosetto Munoz > >> wrote: > >> > Hello All, > >> > > >> > I'm use yocto to create a linux for imx28, with meta-fsl-arm and > >> > meta-openembedded. > >> > > >> > Until now, every thing is ok, I Have a > >> > core-image-minimal-imx28evk.sdcard > >> > that working in the machine. > >> > > >> > My problem is that when I try to add some things in the kernel > >> > configuration, I feel like the system build dont generate a new uImage > >> > file > >> > or the thing that I selected in the Kernel dont be atached in the > >> > core-image-minimal-imx28evk.sdcard! > >> > > >> > What I did is: > >> > > >> > ...tmp/deploy/images$ ls > >> > -rw-r--r-- 1 raul raul 2511696 2012-08-15 16:23 > >> > uImage-2.6.35.3-r24-imx28evk-20120815191927.bin > >> > lrwxrwxrwx 1 raul raul47 2012-08-15 16:23 uImage-imx28evk.bin > >> > -> > >> > uImage-2.6.35.3-r24-imx28evk-20120815191927.bin > >> > > >> > then: > >> > > >> > bitbake -c menuconfig virtual/kernel > >> > bitbake -c patch virtual/kernel > >> > bitbake -c compile virtual/kernel > >> > bitbake virtual/kernel > >> > >> Try > >> > >> bitbake -c compile virtual/kernel -f > >> > >> -M > >> > >> > > >> > and I'm looking again: > >> > > >> > ...tmp/deploy/images$ ls > >> > -rw-r--r-- 1 raul raul 2511696 2012-08-15 16:23 > >> > uImage-2.6.35.3-r24-imx28evk-20120815191927.bin > >> > lrwxrwxrwx 1 raul raul47 2012-08-15 16:23 uImage-imx28evk.bin > >> > -> > >> > uImage-2.6.35.3-r24-imx28evk-20120815191927.bin > >> > > >> > Some One can explain to me what is the correct way to re-build the > >> > virtual/kenel target? > >> > > >> > Thanks for all Help! > >> > > >> > -- > >> > Raul Rosetto Muñoz > >> > > >> > ___ > >> > yocto mailing list > >> > yocto@yoctoproject.org > >> > https://lists.yoctoproject.org/listinfo/yocto > >> > > > > > > > > > > > -- > > Raul Rosetto Muñoz > > > > ___ > > yocto mailing list > > yocto@yoctoproject.org > > https://lists.yoctoproject.org/listinfo/yocto > > > -- *Raul Rosetto Muñoz* ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Re-Build virtual/kernel
You have to also run a target that deploy's the kernel or at least run the deploy command manuall bitbake core-image-minimal or bitbake virtual/kernel -c deploy -M On Thu, Aug 16, 2012 at 2:11 PM, Raul Rosetto Munoz wrote: > don't work. > > > > > 2012/8/16 McClintock Matthew-B29882 >> >> What about the -f? >> >> -M >> >> On Thu, Aug 16, 2012 at 2:02 PM, Raul Rosetto Munoz >> wrote: >> > I did all de comands with -c and do not work! >> > >> > Some one no some thing that I can try to update de uImage file? >> > >> > Thanks for the sugestion. >> > >> > >> > >> > 2012/8/16 McClintock Matthew-B29882 >> >> >> >> On Thu, Aug 16, 2012 at 7:11 AM, Raul Rosetto Munoz >> >> wrote: >> >> > Hello All, >> >> > >> >> > I'm use yocto to create a linux for imx28, with meta-fsl-arm and >> >> > meta-openembedded. >> >> > >> >> > Until now, every thing is ok, I Have a >> >> > core-image-minimal-imx28evk.sdcard >> >> > that working in the machine. >> >> > >> >> > My problem is that when I try to add some things in the kernel >> >> > configuration, I feel like the system build dont generate a new >> >> > uImage >> >> > file >> >> > or the thing that I selected in the Kernel dont be atached in the >> >> > core-image-minimal-imx28evk.sdcard! >> >> > >> >> > What I did is: >> >> > >> >> > ...tmp/deploy/images$ ls >> >> > -rw-r--r-- 1 raul raul 2511696 2012-08-15 16:23 >> >> > uImage-2.6.35.3-r24-imx28evk-20120815191927.bin >> >> > lrwxrwxrwx 1 raul raul47 2012-08-15 16:23 >> >> > uImage-imx28evk.bin >> >> > -> >> >> > uImage-2.6.35.3-r24-imx28evk-20120815191927.bin >> >> > >> >> > then: >> >> > >> >> > bitbake -c menuconfig virtual/kernel >> >> > bitbake -c patch virtual/kernel >> >> > bitbake -c compile virtual/kernel >> >> > bitbake virtual/kernel >> >> >> >> Try >> >> >> >> bitbake -c compile virtual/kernel -f >> >> >> >> -M >> >> >> >> > >> >> > and I'm looking again: >> >> > >> >> > ...tmp/deploy/images$ ls >> >> > -rw-r--r-- 1 raul raul 2511696 2012-08-15 16:23 >> >> > uImage-2.6.35.3-r24-imx28evk-20120815191927.bin >> >> > lrwxrwxrwx 1 raul raul47 2012-08-15 16:23 >> >> > uImage-imx28evk.bin >> >> > -> >> >> > uImage-2.6.35.3-r24-imx28evk-20120815191927.bin >> >> > >> >> > Some One can explain to me what is the correct way to re-build the >> >> > virtual/kenel target? >> >> > >> >> > Thanks for all Help! >> >> > >> >> > -- >> >> > Raul Rosetto Muñoz >> >> > >> >> > ___ >> >> > yocto mailing list >> >> > yocto@yoctoproject.org >> >> > https://lists.yoctoproject.org/listinfo/yocto >> >> > >> > >> > >> > >> > >> > -- >> > Raul Rosetto Muñoz >> > >> > ___ >> > yocto mailing list >> > yocto@yoctoproject.org >> > https://lists.yoctoproject.org/listinfo/yocto >> > > > > > > -- > Raul Rosetto Muñoz > > ___ > yocto mailing list > yocto@yoctoproject.org > https://lists.yoctoproject.org/listinfo/yocto > ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [meta-fsl-ppc][PATCH 2/2] fsl.conf: Let linux-qoriq-sdk-headers-nativesdk provide linux-libc-headers-nativesdk
On Tue, Aug 14, 2012 at 2:26 PM, Khem Raj wrote: > On Tue, Aug 14, 2012 at 12:49 AM, David Nyström > wrote: >> >> Hi, it looks like this was merged to the denzil branch, and >> PREFERRED_PROVIDER_linux-libc-headers-nativesdk was moved back to >> distro.conf. >> Any reason for this ? > > why do you want nativesdk headers to come from BSP its a fsl-ppc bsp I > dont expect it to have something special for SDK hosts which are > usually x86 ? afterall these are for > the SDK host and not for target. Moreover it means that this BSP will > not play in the multi BSP environment something you never want. But, I think we might need them for this warning specifically: NOTE: Resolving any missing task queue dependencies NOTE: multiple providers are available for lib32-linux-libc-headers (lib32-linux-libc-headers, lib32-linux-libc-headers-yocto, lib32-linux-qoriq-sdk-headers) NOTE: consider defining a PREFERRED_PROVIDER entry to match lib32-linux-libc-headers NOTE: multiple providers are available for runtime lib32-linux-libc-headers-dev (lib32-linux-libc-headers, lib32-linux-libc-headers-yocto, lib32-linux-qoriq-sdk-headers) NOTE: consider defining a PREFERRED_PROVIDER entry to match lib32-linux-libc-headers-dev ? -M ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Re-Build virtual/kernel
All the time before loking at tmp/deploy/image/ I did bitbake core-image-minimal. Maybe the .sdcard use the correct uImage and this image is not the uImage in deploy/image path! How can I see the .sdcard using the uImage? Thanks for Help 2012/8/16 McClintock Matthew-B29882 > You have to also run a target that deploy's the kernel or at least run > the deploy command manuall > > bitbake core-image-minimal > > or > > bitbake virtual/kernel -c deploy > > -M > > On Thu, Aug 16, 2012 at 2:11 PM, Raul Rosetto Munoz > wrote: > > don't work. > > > > > > > > > > 2012/8/16 McClintock Matthew-B29882 > >> > >> What about the -f? > >> > >> -M > >> > >> On Thu, Aug 16, 2012 at 2:02 PM, Raul Rosetto Munoz > >> wrote: > >> > I did all de comands with -c and do not work! > >> > > >> > Some one no some thing that I can try to update de uImage file? > >> > > >> > Thanks for the sugestion. > >> > > >> > > >> > > >> > 2012/8/16 McClintock Matthew-B29882 > >> >> > >> >> On Thu, Aug 16, 2012 at 7:11 AM, Raul Rosetto Munoz > >> >> wrote: > >> >> > Hello All, > >> >> > > >> >> > I'm use yocto to create a linux for imx28, with meta-fsl-arm and > >> >> > meta-openembedded. > >> >> > > >> >> > Until now, every thing is ok, I Have a > >> >> > core-image-minimal-imx28evk.sdcard > >> >> > that working in the machine. > >> >> > > >> >> > My problem is that when I try to add some things in the kernel > >> >> > configuration, I feel like the system build dont generate a new > >> >> > uImage > >> >> > file > >> >> > or the thing that I selected in the Kernel dont be atached in the > >> >> > core-image-minimal-imx28evk.sdcard! > >> >> > > >> >> > What I did is: > >> >> > > >> >> > ...tmp/deploy/images$ ls > >> >> > -rw-r--r-- 1 raul raul 2511696 2012-08-15 16:23 > >> >> > uImage-2.6.35.3-r24-imx28evk-20120815191927.bin > >> >> > lrwxrwxrwx 1 raul raul47 2012-08-15 16:23 > >> >> > uImage-imx28evk.bin > >> >> > -> > >> >> > uImage-2.6.35.3-r24-imx28evk-20120815191927.bin > >> >> > > >> >> > then: > >> >> > > >> >> > bitbake -c menuconfig virtual/kernel > >> >> > bitbake -c patch virtual/kernel > >> >> > bitbake -c compile virtual/kernel > >> >> > bitbake virtual/kernel > >> >> > >> >> Try > >> >> > >> >> bitbake -c compile virtual/kernel -f > >> >> > >> >> -M > >> >> > >> >> > > >> >> > and I'm looking again: > >> >> > > >> >> > ...tmp/deploy/images$ ls > >> >> > -rw-r--r-- 1 raul raul 2511696 2012-08-15 16:23 > >> >> > uImage-2.6.35.3-r24-imx28evk-20120815191927.bin > >> >> > lrwxrwxrwx 1 raul raul47 2012-08-15 16:23 > >> >> > uImage-imx28evk.bin > >> >> > -> > >> >> > uImage-2.6.35.3-r24-imx28evk-20120815191927.bin > >> >> > > >> >> > Some One can explain to me what is the correct way to re-build the > >> >> > virtual/kenel target? > >> >> > > >> >> > Thanks for all Help! > >> >> > > >> >> > -- > >> >> > Raul Rosetto Muñoz > >> >> > > >> >> > ___ > >> >> > yocto mailing list > >> >> > yocto@yoctoproject.org > >> >> > https://lists.yoctoproject.org/listinfo/yocto > >> >> > > >> > > >> > > >> > > >> > > >> > -- > >> > Raul Rosetto Muñoz > >> > > >> > ___ > >> > yocto mailing list > >> > yocto@yoctoproject.org > >> > https://lists.yoctoproject.org/listinfo/yocto > >> > > > > > > > > > > > -- > > Raul Rosetto Muñoz > > > > ___ > > yocto mailing list > > yocto@yoctoproject.org > > https://lists.yoctoproject.org/listinfo/yocto > > > -- *Raul Rosetto Muñoz* ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] yocto-bsp create
On 15 Aug 2012, at 21:14, Bruce Ashfield wrote: > On 12-08-15 04:06 PM, Chris Tapp wrote: >> I've been looking at using yocto-bsp to create a BSP. Good job! Looks like >> it's going to be much easier to do it this way :-) > > You really want TomZ to answer, but I'll throw in a few comments > here, since I'm currently reviewing a batch of code from Tom. > >> >> I've got a few questions/comments: >> >> 1) The documentation (7.0.1) says that the machine branch defaults to >> standard/default, but that is not an option that gets presented when I >> created a BSP. Should that be standard/base, standard/default/base, or >> something else? Master shows this as standard/default/common-pc, but that >> still isn't one of the listed options (standard/default/common-pc/base ?). > > For the 3.2 tree, it is standard/default/base, which is a name that we > quickly determined was not optimal, and in the 3.4 kernel tree it is > standard/base. > So the answer is, it depends on the kernel you are using, but the tools > know and have the right defaults. > >> >> 2) What are these machine branches anyway? As in, how do I decide which one >> I should choose? For an ALIX 3D3 system I used >> standard/default/common-pc/base. Is that reasonable? > > They are collections of functionality and configuration. So if you are > working on a new machine that is close to something that is already > in tree, you'd start from the existing machine branch. If you want to > do something new, standard/base, if you want the preempt-rt kernel, > standard/preempt-rt/base, etc. > >> >> 3) I selected core2 as the tune option and then had to change this in the >> created meta-data as I needed i586 tuning and this was not given as a tune >> option. Should all available tunes be offered? >> >> 4) Is there any way to select the kernel CPU (I got MATOM but needed >> MGEODE_LX - easily changed in the.cfg file)? > > AFAIK, no. Since that would imply that all the kernel tunings were parsed > and made available. Adding it to your .cfg is the right thing. If > there is a BSP that already falls into your class, and you inherit > it, you'd get the right tuning by default. > >> >> 5) The created BSP refers to various feature/x/y.scc files. Are these >> documented somewhere so that they can be easily re-used, or am I better off >> simply producing a complete defconfig? A pointer to the documentation for >> the whole kernel meta data structure would also be helpful. > > Tom and I were working on a way to dump these, I'm not sure if that > ever completed. The meta branch of the kernel repo has all the details, > with short descriptions in the .scc files. > > As with anything, documenting a moving source code target is hard, so > I suggest looking at the branch. > > Have a look at the 3.4 kernel tree, meta branch, there's a README with > details about the categories, and contents. Thanks, that's got me going in the right direction. However, I've just recreated the BSP (to use standard/default/base) and I'm now getting an error when I build the kernel: ERROR: Function failed: do_patch (see... /log.do_patch.31458 for further information) ERROR: Logfile of failure stored in: ... /log.do_patch.31458 Log data follows: | ERROR: Function failed: do_patch (see ... /log.do_patch.31458 for further information) | checkpoint is already restored, nothing to do | error: 'refs/heads/standard/default/base' exists; cannot create 'refs/heads/standard/default/base/LX800' | fatal: Failed to lock ref for update: Not a directory | warning: could not find (or was already included): features/dmaengine/dmaengine.scc | warning: could not find (or was already included): features/framebuffer/vesafb.scc | warning: could not find (or was already included): features/intel-e1/intel-e100.scc | warning: could not find (or was already included): features/intel-e1/intel-e1.scc | warning: could not find (or was already included): features/dmaengine/dmaengine.scc | warning: could not find (or was already included): features/serial/8250.scc | warning: could not find (or was already included): features/hpet/hpet.scc | warning: could not find (or was already included): features/ericsson-3g/f5521gw.scc | warning: could not find (or was already included): features/framebuffer/vesafb.scc | warning: could not find (or was already included): cfg/usb-mass-storage.scc | warning: could not find (or was already included): cfg/boot-live.scc | warning: could not find (or was already included): features/power/intel.scc | warning: could not find (or was already included): features/logbuf/size-normal.scc | warning: could not find (or was already included): features/latencytop/latencytop.scc | warning: could not find (or was already included): features/profiling/profiling.scc | warning: could not find (or was already included): user-patches.scc | ./2-LX800-9dbd5e3915bb4ed4d3809d315087c405.sco: line 21: dmaengine_68b329da9893e34099c7d8ad5cb9c940: command not fou
Re: [yocto] [PATCH] routerstationpro: move board off 3.0 and onto the 3.4 kernel
On 07/27/2012 10:10 AM, Paul Gortmaker wrote: The updated patch series to support this target is in place on the BSP specific branch in the 3.4 kernel tree now[1], so we can move it ahead off of the old 3.0 kernel. [1] https://lists.yoctoproject.org/pipermail/linux-yocto/2012-July/23.html Signed-off-by: Paul Gortmaker diff --git a/meta-yocto/conf/machine/routerstationpro.conf b/meta-yocto/conf/machine/routerstationpro.conf index 3c2f56f..adf36a9 100644 --- a/meta-yocto/conf/machine/routerstationpro.conf +++ b/meta-yocto/conf/machine/routerstationpro.conf @@ -10,7 +10,7 @@ KERNEL_IMAGETYPE = "vmlinux" KERNEL_ALT_IMAGETYPE = "vmlinux.bin" PREFERRED_PROVIDER_virtual/kernel ?= "linux-yocto" -PREFERRED_VERSION_linux-yocto ?= "3.0%" +PREFERRED_VERSION_linux-yocto ?= "3.4%" PREFERRED_PROVIDER_virtual/xserver = "xserver-kdrive" XSERVER = "xserver-kdrive-fbdev" diff --git a/meta-yocto/recipes-kernel/linux/linux-yocto_3.4.bbappend b/meta-yocto/recipes-kernel/linux/linux-yocto_3.4.bbappend index 2ff467b..1c8d26a 100644 --- a/meta-yocto/recipes-kernel/linux/linux-yocto_3.4.bbappend +++ b/meta-yocto/recipes-kernel/linux/linux-yocto_3.4.bbappend @@ -4,11 +4,11 @@ KBRANCH_mpc8315e-rdb = "standard/fsl-mpc8315e-rdb" KBRANCH_beagleboard = "standard/beagleboard" SRCREV_machine_atom-pc ?= "a8291fa6f723b0182d2b7033b5d59f412ba7cf72" -SRCREV_machine_routerstationpro ?= "a8291fa6f723b0182d2b7033b5d59f412ba7cf72" +SRCREV_machine_routerstationpro ?= "27019633ccdaa88dc55101615d936d1d74db9a1e" SRCREV_machine_mpc8315e-rdb ?= "47d3076aa7e2a640a1dab8d663529a784709f697" SRCREV_machine_beagleboard ?= "a8291fa6f723b0182d2b7033b5d59f412ba7cf72" COMPATIBLE_MACHINE_mpc8315e-rdb = "mpc8315e-rdb" -# COMPATIBLE_MACHINE_routerstationpro = "routerstationpro" +COMPATIBLE_MACHINE_routerstationpro = "routerstationpro" # COMPATIBLE_MACHINE_beagleboard = "beagleboard" COMPATIBLE_MACHINE_atom-pc = "atom-pc" Yup, this got lost, sorry about that. It will need to be rebased against the patchset that Bruce put up, as I am working with that set also. Also, changes to meta-yocto should go to p...@yoctoproject.org. Sau! ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] yocto-bsp create
On 12-08-16 4:26 PM, Chris Tapp wrote: On 15 Aug 2012, at 21:14, Bruce Ashfield wrote: On 12-08-15 04:06 PM, Chris Tapp wrote: I've been looking at using yocto-bsp to create a BSP. Good job! Looks like it's going to be much easier to do it this way :-) You really want TomZ to answer, but I'll throw in a few comments here, since I'm currently reviewing a batch of code from Tom. I've got a few questions/comments: 1) The documentation (7.0.1) says that the machine branch defaults to standard/default, but that is not an option that gets presented when I created a BSP. Should that be standard/base, standard/default/base, or something else? Master shows this as standard/default/common-pc, but that still isn't one of the listed options (standard/default/common-pc/base ?). For the 3.2 tree, it is standard/default/base, which is a name that we quickly determined was not optimal, and in the 3.4 kernel tree it is standard/base. So the answer is, it depends on the kernel you are using, but the tools know and have the right defaults. 2) What are these machine branches anyway? As in, how do I decide which one I should choose? For an ALIX 3D3 system I used standard/default/common-pc/base. Is that reasonable? They are collections of functionality and configuration. So if you are working on a new machine that is close to something that is already in tree, you'd start from the existing machine branch. If you want to do something new, standard/base, if you want the preempt-rt kernel, standard/preempt-rt/base, etc. 3) I selected core2 as the tune option and then had to change this in the created meta-data as I needed i586 tuning and this was not given as a tune option. Should all available tunes be offered? 4) Is there any way to select the kernel CPU (I got MATOM but needed MGEODE_LX - easily changed in the.cfg file)? AFAIK, no. Since that would imply that all the kernel tunings were parsed and made available. Adding it to your .cfg is the right thing. If there is a BSP that already falls into your class, and you inherit it, you'd get the right tuning by default. 5) The created BSP refers to various feature/x/y.scc files. Are these documented somewhere so that they can be easily re-used, or am I better off simply producing a complete defconfig? A pointer to the documentation for the whole kernel meta data structure would also be helpful. Tom and I were working on a way to dump these, I'm not sure if that ever completed. The meta branch of the kernel repo has all the details, with short descriptions in the .scc files. As with anything, documenting a moving source code target is hard, so I suggest looking at the branch. Have a look at the 3.4 kernel tree, meta branch, there's a README with details about the categories, and contents. Thanks, that's got me going in the right direction. However, I've just recreated the BSP (to use standard/default/base) and I'm now getting an error when I build the kernel: ERROR: Function failed: do_patch (see... /log.do_patch.31458 for further information) ERROR: Logfile of failure stored in: ... /log.do_patch.31458 Log data follows: | ERROR: Function failed: do_patch (see ... /log.do_patch.31458 for further information) | checkpoint is already restored, nothing to do | error: 'refs/heads/standard/default/base' exists; cannot create 'refs/heads/standard/default/base/LX800' | fatal: Failed to lock ref for update: Not a directory | warning: could not find (or was already included): features/dmaengine/dmaengine.scc | warning: could not find (or was already included): features/framebuffer/vesafb.scc | warning: could not find (or was already included): features/intel-e1/intel-e100.scc | warning: could not find (or was already included): features/intel-e1/intel-e1.scc | warning: could not find (or was already included): features/dmaengine/dmaengine.scc | warning: could not find (or was already included): features/serial/8250.scc | warning: could not find (or was already included): features/hpet/hpet.scc | warning: could not find (or was already included): features/ericsson-3g/f5521gw.scc | warning: could not find (or was already included): features/framebuffer/vesafb.scc | warning: could not find (or was already included): cfg/usb-mass-storage.scc | warning: could not find (or was already included): cfg/boot-live.scc | warning: could not find (or was already included): features/power/intel.scc | warning: could not find (or was already included): features/logbuf/size-normal.scc | warning: could not find (or was already included): features/latencytop/latencytop.scc | warning: could not find (or was already included): features/profiling/profiling.scc | warning: could not find (or was already included): user-patches.scc | ./2-LX800-9dbd5e3915bb4ed4d3809d315087c405.sco: line 21: dmaengine_68b329da9893e34099c7d8ad5cb9c940: command not found | ./2-LX800-9dbd5e3915bb4ed4d3809d315087c405.sco: line 33: vesafb_68b329da9893e34099c7d8ad5
Re: [yocto] [PATCH 1/3] - Code clean-up & refactoring on Yocto-BSP pages & wizards
The patch is missing signed-off
-Original Message-
From: yocto-boun...@yoctoproject.org [mailto:yocto-boun...@yoctoproject.org] On
Behalf Of Ioana Grigoropol
Sent: Thursday, August 16, 2012 8:05 AM
To: yocto@yoctoproject.org
Cc: Grigoropol, IoanaX
Subject: [yocto] [PATCH 1/3] - Code clean-up & refactoring on Yocto-BSP pages &
wizards
---
.../sdk/remotetools/wizards/bsp/MainPage.java | 261 +++-
.../remotetools/wizards/bsp/PropertiesPage.java| 26 +-
.../remotetools/wizards/bsp/YoctoBSPWizard.java| 33 +--
3 files changed, 152 insertions(+), 168 deletions(-)
diff --git
a/plugins/org.yocto.sdk.remotetools/src/org/yocto/sdk/remotetools/wizards/bsp/MainPage.java
b/plugins/org.yocto.sdk.remotetools/src/org/yocto/sdk/remotetools/wizards/bsp/MainPage.java
index d80dd75..b729ad1 100644
---
a/plugins/org.yocto.sdk.remotetools/src/org/yocto/sdk/remotetools/wizards/bsp/MainPage.java
+++ b/plugins/org.yocto.sdk.remotetools/src/org/yocto/sdk/remotetools/wi
+++ zards/bsp/MainPage.java
@@ -20,24 +20,21 @@ import org.eclipse.core.runtime.IStatus; import
org.eclipse.core.runtime.Status; import org.eclipse.jface.wizard.WizardPage;
import org.eclipse.swt.SWT;
-import org.eclipse.swt.widgets.Event;
import org.eclipse.swt.events.ModifyEvent;
import org.eclipse.swt.events.ModifyListener;
import org.eclipse.swt.events.SelectionAdapter;
import org.eclipse.swt.events.SelectionEvent;
import org.eclipse.swt.layout.GridData; import
org.eclipse.swt.layout.GridLayout;
-import org.eclipse.swt.widgets.Widget;
import org.eclipse.swt.widgets.Button;
import org.eclipse.swt.widgets.Combo;
import org.eclipse.swt.widgets.Composite;
import org.eclipse.swt.widgets.Control; import
org.eclipse.swt.widgets.DirectoryDialog;
-
+import org.eclipse.swt.widgets.Event;
import org.eclipse.swt.widgets.Label;
import org.eclipse.swt.widgets.Text;
-
-
+import org.eclipse.swt.widgets.Widget;
import org.yocto.sdk.remotetools.YoctoBspElement;
/**
@@ -47,10 +44,7 @@ import org.yocto.sdk.remotetools.YoctoBspElement;
* @author jzhang
*/
public class MainPage extends WizardPage {
- public static final String PAGE_NAME = "Main";
- private static final String META_DATA_LOC = "MetadataLoc";
- private static final String BSP_OUT_LOC = "BspOutLoc";
- private static final String BUILD_DIR_LOC = "BuilddirLoc";
+ public static final String PAGE_NAME = "Main";
private static final String KARCH_CMD = "yocto-bsp list karch";
private static final String QARCH_CMD = "yocto-bsp list qemu property
qemuarch";
private static final String BSP_SCRIPT = "yocto-bsp"; @@ -59,27 +53,31
@@ public class MainPage extends WizardPage {
private static final String PROPERTIES_FILE = "/tmp/properties.json";
private Button btnMetadataLoc;
- private Button btnBspOutLoc;
- private Button btnBuilddirLoc;
private Text textMetadataLoc;
+ private Label labelMetadata;
+
+ private Button btnBspOutputLoc;
+ private Text textBspOutputLoc;
+ private Label labelBspOutput;
+
+ private Button btnBuildLoc;
+ private Text textBuildLoc;
+ private Label labelBuildLoc;
+
private Text textBspName;
- private Text textBspOutLoc;
- private Text textBuilddirLoc;
- private Combo karchCombo;
- private Combo qarchCombo;
- private Label metadata_label;
- private Label builddir_label;
- private Label bspname_label;
- private Label bspout_label;
- private Label karch_label;
- private Label qarch_label;
+ private Label labelBspName;
+
+ private Combo comboKArch;
+ private Label labelKArch;
+
+ private Combo comboQArch;
+ private Label labelQArch;
private YoctoBspElement bspElem;
public MainPage(YoctoBspElement element) {
super(PAGE_NAME, "yocto-bsp main page", null);
- //setTitle("Yocto-bsp main page");
setMessage("Enter the required fields(with *) to create new
Yocto Project BSP!");
this.bspElem = element;
}
@@ -91,74 +89,98 @@ public class MainPage extends WizardPage {
GridLayout layout = new GridLayout(2, false);
composite.setLayout(layout);
- gd.horizontalSpan= 2;
+ gd.horizontalSpan = 2;
composite.setLayoutData(gd);
- metadata_label = new Label(composite, SWT.NONE);
- metadata_label.setText("Meta_data location*: ");
+ labelMetadata = new Label(composite, SWT.NONE);
+ labelMetadata.setText("Meta_data location*: ");
Composite textContainer = new Composite(composite, SWT.NONE);
textContainer.setLayout(new GridLayout(2, false));
textContainer.setLayoutData(new GridData(SWT.FILL, SWT.C
Re: [yocto] [PATCH 2/3] [PATCH]Fixed bug 2922 - Yocto-BSP main page checks for build/output location generate error pop-up on properties pages
The patch is missing signed-off.
Also for the case - if a directory is specified
- if it does not exist -> create it under metadataLocation
It should be if it doesn't exist source oe-init-build-env will create the
directory at the specified location instead of creating it under
metadatalocation. When testing this patch, it created a "h", "ho" and "hom"
directories under my metadatalocation, and in the property page triggered a
traceback. So please fix these issues.
Thanks,
Jessica
-Original Message-
From: yocto-boun...@yoctoproject.org [mailto:yocto-boun...@yoctoproject.org] On
Behalf Of Ioana Grigoropol
Sent: Thursday, August 16, 2012 8:14 AM
To: yocto@yoctoproject.org
Cc: Grigoropol, IoanaX
Subject: [yocto] [PATCH 2/3] [PATCH]Fixed bug 2922 - Yocto-BSP main page checks
for build/output location generate error pop-up on properties pages
checks for build location :
- if no location is specified, use metadataLocation/build
- if a directory is specified
- if it does not exist -> create it under metadataLocation
- if it does exist -> oe-init-build-env - create conf/ hierachy
- skip if already there
- collect error output for build directory creation
- checks for output location :
- if the output directory already exists -> show error & disable
next(the yocto-bsp script will fail if the directory already exists)
Signed-off-by: Ioana Grigoropol
---
.../sdk/remotetools/wizards/bsp/MainPage.java | 96 +---
1 file changed, 64 insertions(+), 32 deletions(-)
diff --git
a/plugins/org.yocto.sdk.remotetools/src/org/yocto/sdk/remotetools/wizards/bsp/MainPage.java
b/plugins/org.yocto.sdk.remotetools/src/org/yocto/sdk/remotetools/wizards/bsp/MainPage.java
index b729ad1..e5a21d1 100644
---
a/plugins/org.yocto.sdk.remotetools/src/org/yocto/sdk/remotetools/wizards/bsp/MainPage.java
+++ b/plugins/org.yocto.sdk.remotetools/src/org/yocto/sdk/remotetools/wi
+++ zards/bsp/MainPage.java
@@ -251,28 +251,33 @@ public class MainPage extends WizardPage {
labelQArch.setEnabled(false);
comboQArch.setEnabled(false);
}
+} else if (widget == textBuildLoc){
+status = checkBuildDir();
}
-
-checkBuildDir();
-
-String build_dir = textBuildLoc.getText();
-String output_dir = textBspOutputLoc.getText();
-String bsp_name = textBspName.getText();
-if (!output_dir.isEmpty() && output_dir.matches(build_dir)) {
-status = new Status(IStatus.ERROR, "not_used", 0,
-"You've set BSP output directory the
same as build directory, please leave output directory empty for this
scenario!", null);
-}
+String buildDir = textBuildLoc.getText();
+String outputDir = textBspOutputLoc.getText();
+String bspName = textBspName.getText();
-if (build_dir.startsWith(metadataLoc) && output_dir.isEmpty()
&& !bsp_name.isEmpty()) {
-String bsp_dir_str = metadataLoc + "/meta-" + bsp_name;
-File bsp_dir = new File(bsp_dir_str);
-if (bsp_dir.exists()) {
+if (!outputDir.isEmpty()){
+if (outputDir.matches(buildDir)) {
+status = new Status(IStatus.ERROR, "not_used",
0,
+"You've set BSP output
directory the same as build directory, please leave output directory empty for
this scenario!", null);
+} else {
+File outputDirectory = new File(outputDir);
+if (outputDirectory.exists()){
+ status = new Status(IStatus.ERROR,
"not_used", 0,
+"Your BSP output
directory points to an exiting directory!", null);
+}
+}
+} else if (buildDir.startsWith(metadataLoc) &&
!bspName.isEmpty()) {
+String bspDirStr = metadataLoc + "/meta-" + bspName;
+File bspDir = new File(bspDirStr);
+if (bspDir.exists()) {
status = new Status(IStatus.ERROR, "not_used",
0,
-"Your BSP with name: " +
bsp_name + " already exist under directory: " + bsp_dir_str + ", please change
your bsp name!", null);
+"Your BSP with name: " +
bspName + " already exist under
+directory: " + bspDirStr + ", please change your bsp name!", null);
}
Re: [yocto] [PATCH 3/3] [PATCH] Processes that execute shell commands block the Yocto-BSP interface
Hi Ioana,
The patch is missing signed-off
Thanks,
Jessica
-Original Message-
From: yocto-boun...@yoctoproject.org [mailto:yocto-boun...@yoctoproject.org] On
Behalf Of Ioana Grigoropol
Sent: Thursday, August 16, 2012 8:14 AM
To: yocto@yoctoproject.org
Cc: Grigoropol, IoanaX
Subject: [yocto] [PATCH 3/3] [PATCH] Processes that execute shell commands
block the Yocto-BSP interface
- send processes that execute shell commands in the background and show
progress dialog
- retrieve status of the background executions & items collected
Signed-off-by: Ioana Grigoropol
---
.../sdk/remotetools/wizards/bsp/MainPage.java |1 -
.../remotetools/wizards/bsp/PropertiesPage.java| 196
2 files changed, 123 insertions(+), 74 deletions(-)
diff --git
a/plugins/org.yocto.sdk.remotetools/src/org/yocto/sdk/remotetools/wizards/bsp/MainPage.java
b/plugins/org.yocto.sdk.remotetools/src/org/yocto/sdk/remotetools/wizards/bsp/MainPage.java
index e5a21d1..bd80ed4 100644
---
a/plugins/org.yocto.sdk.remotetools/src/org/yocto/sdk/remotetools/wizards/bsp/MainPage.java
+++ b/plugins/org.yocto.sdk.remotetools/src/org/yocto/sdk/remotetools/wi
+++ zards/bsp/MainPage.java
@@ -313,7 +313,6 @@ public class MainPage extends WizardPage {
// system.property usually points to the location from where
eclipse was started
String createBuildDirCmd = "cd " + metadataDir + ";source " +
metadataDir + "/oe-init-build-env " + buildLoc;
- System.out.println(createBuildDirCmd);
try {
ProcessBuilder builder = new ProcessBuilder(new
String[] {"sh", "-c", createBuildDirCmd});
Process proc = builder.start();
diff --git
a/plugins/org.yocto.sdk.remotetools/src/org/yocto/sdk/remotetools/wizards/bsp/PropertiesPage.java
b/plugins/org.yocto.sdk.remotetools/src/org/yocto/sdk/remotetools/wizards/bsp/PropertiesPage.java
index 4661b37..38af7b9 100644
---
a/plugins/org.yocto.sdk.remotetools/src/org/yocto/sdk/remotetools/wizards/bsp/PropertiesPage.java
+++ b/plugins/org.yocto.sdk.remotetools/src/org/yocto/sdk/remotetools/wi
+++ zards/bsp/PropertiesPage.java
@@ -11,7 +11,6 @@
package org.yocto.sdk.remotetools.wizards.bsp;
import java.io.BufferedReader;
-import java.io.InputStream;
import java.io.InputStreamReader;
import java.util.ArrayList;
import java.util.Enumeration;
@@ -19,7 +18,10 @@ import java.util.HashSet; import java.util.Hashtable;
import java.util.Iterator;
+import org.eclipse.core.runtime.IProgressMonitor;
import org.eclipse.jface.dialogs.MessageDialog;
+import org.eclipse.jface.dialogs.ProgressMonitorDialog;
+import org.eclipse.jface.operation.IRunnableWithProgress;
import org.eclipse.jface.wizard.WizardPage;
import org.eclipse.swt.SWT;
import org.eclipse.swt.custom.ScrolledComposite;
@@ -59,6 +61,9 @@ public class PropertiesPage extends WizardPage {
private static final String NEW_KBRANCH_NAME = "new_kbranch";
private static final String QARCH_NAME = "qemuarch";
+ private static final String KERNEL_CHOICES = "choices";
+ private static final String KERNEL_BRANCHES = "branches";
+
private Hashtable propertyControlMap;
HashSet properties;
private Composite composite;
@@ -81,9 +86,8 @@ public class PropertiesPage extends WizardPage {
}
public void onEnterPage(YoctoBspElement element) {
- String[] values;
if (!element.getValidPropertiesFile()) {
- setErrorMessage("There's no valid properties file
created, please choose \"Back\" to reselect kernel architectur!");
+ setErrorMessage("There's no valid properties file
created, please
+choose \"Back\" to reselect kernel architecture!");
return;
}
@@ -131,9 +135,7 @@ public class PropertiesPage extends WizardPage {
newButton.setSelection(true);
existingButton.setSelection(false);
- values = getValues(KERNEL_CHOICE);
- if (values != null)
- kcCombo.setItems(values);
+ updateKernelValues(KERNEL_CHOICES, KERNEL_CHOICE);
}
try {
@@ -194,10 +196,9 @@ public class PropertiesPage extends WizardPage {
new Label (choiceContainer,
SWT.NONE).setText(name+":");
Combo combo = new
Combo(choiceContainer, SWT.BORDER | SWT.READ_ONLY);
combo.setLayout(new
FillLayout());
-
- values = getValues(name);
- if (values != null)
- combo.setItems(values);
+
+
[yocto] Toolchain rework, call for testing
Hi All Recently glibc build has been simplified upstream. It has dropped the dependency on libgcc_s and libgcc_eh for building glibc itself. This means that we can simplify our toolchain bootstrap a bit by dropping 1 of the 3 cross gcc build stages. We do not need gcc-cross-intermediate anymore. This should bring some build time reduction and simplify the bootstrap. I have a series of patches which I have tested by building core-image-minimal and meta-toolchain for all supported qemu architectures and also uclibc/eglibc both but it needs a lot more testing therefore I am calling out wider audience for help in testing it out. The branch is http://git.openembedded.org/openembedded-core-contrib/log/?h=kraj/toolchain-rework Thanks -Khem ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [meta-fsl-ppc][PATCH 2/2] fsl.conf: Let linux-qoriq-sdk-headers-nativesdk provide linux-libc-headers-nativesdk
On Thu, Aug 16, 2012 at 12:37 PM, McClintock Matthew-B29882 wrote: > On Tue, Aug 14, 2012 at 2:26 PM, Khem Raj wrote: >> On Tue, Aug 14, 2012 at 12:49 AM, David Nyström >> wrote: >>> >>> Hi, it looks like this was merged to the denzil branch, and >>> PREFERRED_PROVIDER_linux-libc-headers-nativesdk was moved back to >>> distro.conf. >>> Any reason for this ? >> >> why do you want nativesdk headers to come from BSP its a fsl-ppc bsp I >> dont expect it to have something special for SDK hosts which are >> usually x86 ? afterall these are for >> the SDK host and not for target. Moreover it means that this BSP will >> not play in the multi BSP environment something you never want. > > But, I think we might need them for this warning specifically: > > NOTE: Resolving any missing task queue dependencies > NOTE: multiple providers are available for lib32-linux-libc-headers > (lib32-linux-libc-headers, lib32-linux-libc-headers-yocto, > lib32-linux-qoriq-sdk-headers) > NOTE: consider defining a PREFERRED_PROVIDER entry to match > lib32-linux-libc-headers > NOTE: multiple providers are available for runtime > lib32-linux-libc-headers-dev (lib32-linux-libc-headers, > lib32-linux-libc-headers-yocto, lib32-linux-qoriq-sdk-headers) > NOTE: consider defining a PREFERRED_PROVIDER entry to match > lib32-linux-libc-headers-dev > This is a bug in OE-Core, it should have added appropriate defines for multilib case as well in tcmode-default.inc and default-providers.inc > ? > > -M ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Unable to get serial console login prompt - PowerPC 440 Virtex 5 processor
On Tue, Aug 14, 2012 at 7:26 AM, Khem Raj wrote: > > There are differences in eglibc.inc and initrd recipes. Try to see if they > make difference > Also the libgcc one after the above two Elvis Did you try the above ? I have pushed a patch into my contrib tree. http://git.openembedded.org/openembedded-core-contrib/commit/?h=kraj/misc&id=502a61792cdb219c1ee35bb9474b8f0c4b007385 can you try that out and see if it helps with gcc 4.7 ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [meta-fsl-ppc][PATCH 2/2] fsl.conf: Let linux-qoriq-sdk-headers-nativesdk provide linux-libc-headers-nativesdk
On Fri, Aug 17, 2012 at 12:12 AM, Khem Raj wrote: > On Thu, Aug 16, 2012 at 12:37 PM, McClintock Matthew-B29882 > wrote: >> On Tue, Aug 14, 2012 at 2:26 PM, Khem Raj wrote: >>> On Tue, Aug 14, 2012 at 12:49 AM, David Nyström >>> wrote: Hi, it looks like this was merged to the denzil branch, and PREFERRED_PROVIDER_linux-libc-headers-nativesdk was moved back to distro.conf. Any reason for this ? >>> >>> why do you want nativesdk headers to come from BSP its a fsl-ppc bsp I >>> dont expect it to have something special for SDK hosts which are >>> usually x86 ? afterall these are for >>> the SDK host and not for target. Moreover it means that this BSP will >>> not play in the multi BSP environment something you never want. >> >> But, I think we might need them for this warning specifically: >> >> NOTE: Resolving any missing task queue dependencies >> NOTE: multiple providers are available for lib32-linux-libc-headers >> (lib32-linux-libc-headers, lib32-linux-libc-headers-yocto, >> lib32-linux-qoriq-sdk-headers) >> NOTE: consider defining a PREFERRED_PROVIDER entry to match >> lib32-linux-libc-headers >> NOTE: multiple providers are available for runtime >> lib32-linux-libc-headers-dev (lib32-linux-libc-headers, >> lib32-linux-libc-headers-yocto, lib32-linux-qoriq-sdk-headers) >> NOTE: consider defining a PREFERRED_PROVIDER entry to match >> lib32-linux-libc-headers-dev >> > > This is a bug in OE-Core, it should have added appropriate defines for > multilib case as well in > tcmode-default.inc and default-providers.inc And there appears to be a fix for it already: http://patches.openembedded.org/patch/34723/ -M > >> ? >> >> -M > ___ > yocto mailing list > yocto@yoctoproject.org > https://lists.yoctoproject.org/listinfo/yocto ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
