On 14/05/12 19:52, Chris Tapp wrote:
> I'm trying to put a BSP together for an ARM system (Raspberry Pi,
> ARM1176JZF-S CPU).
I got the feeling that there might be multiple OE/RPI efforts going on
at the same time unaware of each other, e.g., I noticed this
meta-raspberrypi layer on github that
The new download mirror is now active. Fetching from
downloads.yoctoproject.org should be reliable once again.
Michael Halstead
Yocto Project / Sys Admin
On 05/14/2012 08:21 PM, Michael Halstead wrote:
>
> We are experiencing download mirror instability that began with a DDOS
> on Friday. Since
Apologies for the massive cross-post, but most users don't read the development
lists :) To avoid 'reply all' mistakes the addressed lists are in BCC. In case
you are wondering which lists: the beagleboard list, the meta-ti list and the
yocto project list.
A minor update to the below: the test
Hi Tomas,
> On 14/05/12 19:52, Chris Tapp wrote:
> > I'm trying to put a BSP together for an ARM system (Raspberry Pi,
> ARM1176JZF-S CPU).
>
> I got the feeling that there might be multiple OE/RPI efforts going on at the
> same time unaware of each other, e.g., I noticed this meta-raspberrypi la
There do seem to be multiple efforts. The Qt on Pi folks are also
putting together a BSP. I'd like to find a way to put everyone
together to make sure effort is not being duplicated. Is there
interest in a meeting of interested parties, perhaps on Thursday?
On Tue, May 15, 2012 at 7:51 AM, John Wi
https://wiki.yoctoproject.org/wiki/Yocto_Project_v1.3_Status#Milestone_1
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
> There do seem to be multiple efforts. The Qt on Pi folks are also putting
> together a BSP. I'd like to find a way to put everyone together to make
sure
> effort is not being duplicated. Is there interest in a meeting of
interested
> parties, perhaps on Thursday?
I have quite a few commitments o
On 12-05-15 05:15 AM, Tomas Frydrych wrote:
On 14/05/12 19:52, Chris Tapp wrote:
I'm trying to put a BSP together for an ARM system (Raspberry Pi, ARM1176JZF-S
CPU).
I got the feeling that there might be multiple OE/RPI efforts going on
at the same time unaware of each other, e.g., I noticed
On 15 May 2012, at 16:44, Bruce Ashfield wrote:
> On 12-05-15 05:15 AM, Tomas Frydrych wrote:
>> On 14/05/12 19:52, Chris Tapp wrote:
>>> I'm trying to put a BSP together for an ARM system (Raspberry Pi,
>>> ARM1176JZF-S CPU).
>>
>> I got the feeling that there might be multiple OE/RPI efforts g
On 15 May 2012, at 16:05, Osier-mixon, Jeffrey wrote:
> There do seem to be multiple efforts. The Qt on Pi folks are also
> putting together a BSP. I'd like to find a way to put everyone
> together to make sure effort is not being duplicated. Is there
> interest in a meeting of interested parties,
Attendees:
Josh, Sean, Jessica, ScottG, Mark, Darren, Denys, Jefro, Beth, Jeff, Matthew,
Laurentiu, Michael, Bruce, Chris Larson, Ciby, Song
Agenda
* Opens collection - 5 min (Song)
* 1.2.1 update - 10 min (ScottG)
- We have 21 bugs fixed for 1.2.1, 23 more remain open. Current RC1 is July
2n
Hi Bruce,
On 15/05/12 16:44, Bruce Ashfield wrote:
> On 12-05-15 05:15 AM, Tomas Frydrych wrote:
>> On 14/05/12 19:52, Chris Tapp wrote:
>>> I'm trying to put a BSP together for an ARM system (Raspberry Pi,
>>> ARM1176JZF-S CPU).
>>
>> I got the feeling that there might be multiple OE/RPI efforts
On 12-05-15 01:36 PM, Tomas Frydrych wrote:
Hi Bruce,
On 15/05/12 16:44, Bruce Ashfield wrote:
On 12-05-15 05:15 AM, Tomas Frydrych wrote:
On 14/05/12 19:52, Chris Tapp wrote:
I'm trying to put a BSP together for an ARM system (Raspberry Pi,
ARM1176JZF-S CPU).
I got the feeling that there m
On 12-05-14 04:11 PM, Wolfgang Denk wrote:
Hi,
we noticed warnings like "No generic license file exists for: GPL in
any provider" for our own linux kernel recipe. The cause wa the use
of an entry
LICENSE = "GPL"
which whould read "GPLv2" instead of "GPL". A scan detected that the
sam
I used poky-denzil-7.0 to build a core-image-minimal for the BeagleBoard.
Now I am looking for a list of everything that went into my image together
with the license information. The logical thing seems to be
${TMPDIR}/deploy/licenses/core-image-minimal-beagleboard-/package.manifest:
base-files
ba
On Tue, May 15, 2012 at 3:38 PM, Rudolf Streif wrote:
> I used poky-denzil-7.0 to build a core-image-minimal for the BeagleBoard.
> Now I am looking for a list of everything that went into my image together
> with the license information. The logical thing seems to be
> ${TMPDIR}/deploy/licenses/c
Thanks for your response, Beth. I am using the default: RPM.
:rjs
On Tue, May 15, 2012 at 3:53 PM, Flanagan, Elizabeth <
elizabeth.flana...@intel.com> wrote:
> On Tue, May 15, 2012 at 3:38 PM, Rudolf Streif
> wrote:
> > I used poky-denzil-7.0 to build a core-image-minimal for the BeagleBoard.
>
Problems:
Moving files between builders requires copying them to localhost and
back (slow) or forwarding your ssh-agent around (poor security).
Different amounts of free local storage mean pokybuild has different
size constraints on different builders which isn't helpful.
Solution:
Beth and I prop
Related to that I have another question. If I use this recipe to create an
image
DESCRIPTION = "A small image with gcc"
IMAGE_INSTALL = "task-core-boot gcc"
LICENSE = "MIT"
inherit core-image
and call it myimage.bb
${TMPDIR}/deploy/icenses will contain a subdirectory named myimage.
However, the
On Tuesday, May 15, 2012, Rudolf Streif wrote:
> I used poky-denzil-7.0 to build a core-image-minimal for the BeagleBoard.
Now I am looking for a list of everything that went into my image together
with the license information. The logical thing seems to be
${TMPDIR}/deploy/licenses/core-image-min
>> I think kernel and uboot are not bundled into image but kernel modules
are why
>> module-init-tools does not appear there might be a bug
Yes, that is technically of course correct. However, the idea of
package.manifest and license.manifest should be to provide a list of
everything that goes in
21 matches
Mail list logo
