Hello @all,
as part of my bachelor thesis, I'm in the process of creating a custom
Linux OS
for the taskit Stamp9G20http://www.taskit.de/en/products/stamp9g20/index.htm(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
On Tue, Jun 26, 2012 at 3:19 PM, Bruce Ashfield
bruce.ashfi...@windriver.com 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
On Fri, Jun 29, 2012 at 3:47 PM, Bruce Ashfield
bruce.ashfi...@windriver.com wrote:
On 12-06-29 09:34 AM, Markus Hubig wrote:
I guess the config variables inside features_not_found.txt are the one
I need to include into
the stamp9g20.cfg, stamp9g20-non_hardware.cfg files? (Ok except
Hello @all, hello Bruce!
https://bitbucket.org/imko/meta-stamp9g20
here you can find my first attempt of a BSP for the taskit stamp9g20 and
portuxg20 Board. Until now there is only the kernel part. Please have a look
and give comments.
Thanks, Markus
Hello @all,
now that I have found out that the variable PRINC stands for
increment the PR-variable
how do I use it?
Version 1, found here:
http://www.yoctoproject.org/docs/current/dev-manual/dev-manual.html#using-bbappend-files
PRINC = 1
Version 2, found here:
Hello @all,
I'm working on a bsp vor the taskit stamp9g20 cpu module.
I have a bbappend file for the linux-yocto_3.2 kernel which was ones working
but now (after updating the denzil branch from 7.0 to 7.0.1) I get a strange
error while building the kernel.
I managed to track the problem down to
Hi @all,
I'm having some trouble building a BSP supporting two different machines.
The machines in question are the Stamp9g20 and PortuxG20 from taskit. These
machines are just slightly different course the PortuxG20 is basically just
a small SBC built around the Stamp9G20.
You can have a look
On Thu, Aug 09, 2012 at 10:48:30AM -0400, Bruce Ashfield wrote:
On Thu, Aug 9, 2012 at 10:46 AM, Markus Hubig mhu...@imko.de wrote:
snip
Comparing the output of bitbake -e linux-yocto for both MACHINE settings
I notice that for stamp9g20 KMACHINE is stamp9g20 but for portuxg20 it's
common
On Fri, Aug 10, 2012 at 12:50:00PM -0400, Bruce Ashfield wrote:
On Fri, Aug 10, 2012 at 11:01 AM, Markus Hubig mhu...@imko.de wrote:
On Thu, Aug 09, 2012 at 03:10:36PM -0400, Bruce Ashfield wrote:
On 12-08-09 01:24 PM, Bruce Ashfield wrote:
On 12-08-09 12:32 PM, Markus Hubig wrote:
On Thu
Hi @all,
I have a customized Yocto-Linux Recipe in my BSP, and now I'm seeing that
the UBOOT_ENTRYPOINT and UBOOT_LOADADDRESS settings in my ${MACHINE}.conf
is not honored in the resulting uImage.
The relevant part of kernel.bbclass is in kernel_do_deploy():
| if test x${KERNEL_IMAGETYPE} =
Hello @all,
because I need the commit 'dcadeda' I switched from denzil to 1.3_M3.
Now I get a strage error while do_kernel_config:
| configme --reconfig --output .../linux-portuxg20-standard-build standard
stamp9g20
| [INFO] Configuring target/machine combo: standard/stamp9g20
| [INFO]
On Thu, Aug 23, 2012 at 12:26:30PM -0400, Bruce Ashfield wrote:
On 12-08-23 12:18 PM, Markus Hubig wrote:
On Thu, Aug 23, 2012 at 09:31:15AM -0400, Bruce Ashfield wrote:
On 12-08-23 09:24 AM, Markus Hubig wrote:
snipp
Surprisingly if I remove the *.cfg files from the SRC_URI
On Fri, Aug 24, 2012 at 11:39:10AM +0100, Paul Eggleton wrote:
On Friday 24 August 2012 12:05:41 Markus Hubig wrote:
First: tasks are packages without content.
| rpm -qpl task-core-boot-1.0-r9.stamp9g20.rpm
| (contains no files)
... so why do they need some license information
+ Adds native support for systemd in addition to sysvinit.
* Splits the huge recipe into an inc and a small bb file.
* Avoids the installation of the sysvinit files with systemd.
Signed-off-by: Markus Hubig mhu...@imko.de
---
.../openssh/openssh-6.2p2/init | 92
14 matches
Mail list logo
