On Tue, May 29, 2012 at 05:34:13PM +0200, Martin Jansa wrote:
> The following changes since commit 44df9dd3dc411ca1255cb4b23bde7eb71aed4778:
>
> opkg-make-index: disable filelist by default (2012-04-26 11:39:42 +0100)
ping?
>
> are available in the git repository at:
> git://github.com/shr-
On 14 June 2012 23:18, Khem Raj wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On 6/14/2012 5:17 PM, Tyler Jones wrote:
> > I am compiling a distro for my hardware using DEBs for my package
> > management. In meta/classes/package_deb.bbclass I need DPKG_ARCH =
> > "armel" instead of
On 06/15/2012 02:10 PM, Tim Bird wrote:
> On 06/14/2012 12:11 AM, Tomas Frydrych wrote:
>> A system that runs nothing but a shell is really not useful for anything
>> all, everyone using it will be adding some sort of services, so the
>> question of how the extending works (or does not work), nee
On 06/15/2012 02:26 PM, Tomas Frydrych wrote:
>
> On 15/06/12 20:49, Tim Bird wrote:
>> On 06/14/2012 11:31 PM, Tomas Frydrych wrote:
>> IMHO, the whole notion of starting with a big system and
>> subtracting what you don't want in order to create a minimal
>> system is the wrong approach.
>
>
On 06/15/2012 12:05 AM, Thomas Petazzoni wrote:
> Le Fri, 15 Jun 2012 07:31:45 +0100,
> Tomas Frydrych a écrit :
>
>> Hi Darren,
>>
>> On 14/06/12 22:09, Darren Hart wrote:
>>> This solution improves the kick-the-tires
>>> experience with poky-tiny, without pulling in all of init,
>>
>> I thin
On 15/06/12 20:49, Tim Bird wrote:
> On 06/14/2012 11:31 PM, Tomas Frydrych wrote:
> IMHO, the whole notion of starting with a big system and
> subtracting what you don't want in order to create a minimal
> system is the wrong approach.
At no point in this discussion was such an approach advocate
On 06/14/2012 12:11 AM, Tomas Frydrych wrote:
> A system that runs nothing but a shell is really not useful for anything
> all, everyone using it will be adding some sort of services, so the
> question of how the extending works (or does not work), needs to be in
> the forefront of the design. My m
The reorganization at https://bugzilla.yoctoproject.org/ is complete.
Total time offline was 7 minutes. Please report any errors to me via
e-mail or to halstead in #yocto on freenode.
Michael Halstead
Yocto Project / Sys Admin
On 06/15/2012 05:03 AM, Michael Halstead wrote:
> The reorganization
On 15 Jun 2012, at 07:01, Tomas Frydrych wrote:
> Hi,
>
> On 14/06/12 22:42, Chris Tapp wrote:
>> On 14 Jun 2012, at 21:44, Chris Tapp wrote:
>>
>>> The log for do_rootfs is showing: < snip > error: Failed
>>> dependencies: libGL.so.1 is needed by libglut3-7.11-r13.2.armv6
>>> libGL.so.1 is nee
On 06/14/2012 11:31 PM, Tomas Frydrych wrote:
> Hi Darren,
>
> On 14/06/12 22:09, Darren Hart wrote:
>> This solution improves the kick-the-tires
>> experience with poky-tiny, without pulling in all of init,
>
> I think you really should quantify what 'all of init' means, without
> this you are
Tiny ARM board compatible with Arduino shields. Anyone seen one of these in
the wild?
http://www.h-online.com/open/news/item/ARM-board-for-Arduino-shields-1618480.html
--
Jeff Osier-Mixon http://jefro.net/blog
Yocto Project Community Manager @Intel http://yoctoproject.org
__
On 06/15/2012 09:29 AM, Barros Pena, Belen wrote:
> It definitely helps: thanks!
>
> From what you say the following selections impact the image types:
> machine, base image and distro.
>
> I need to give this a bit of thought. I might be back with even more
> questions (I hope that's ok).
Of
It definitely helps: thanks!
>From what you say the following selections impact the image types:
machine, base image and distro.
I need to give this a bit of thought. I might be back with even more
questions (I hope that's ok).
Have a great weekend.
Belen
On 15/06/2012 17:16, "Darren Hart" wr
On 06/15/2012 08:56 AM, Barros Pena, Belen wrote:
> I'll try to explain:
>
> Your answer to my question was that we should allow outputting live images
> when building qemu machines because it could be useful to run those live
> images in the emulator, but the emulator is not currently capable o
I'll try to explain:
Your answer to my question was that we should allow outputting live images
when building qemu machines because it could be useful to run those live
images in the emulator, but the emulator is not currently capable of
running live images (although it probably will in the future
Hi Kai,
I have a question about the image-writer and I was wondering if you could
help.
We are working on the Hob screen we will display after finishing a build.
If the build creates a live image (.iso, .hddimg files), we display a
'Deploy image' option that should launch the image-writer.
There
On 06/15/2012 07:39 AM, Barros Pena, Belen wrote:
> Thanks for clarifying this, Darren. I think right now we need to design
> for what the current emulator can do. When things change, we should
> remember to update Hob.
You suggested that this had a significant impact on the dialog for
selecting i
Thanks for clarifying this, Darren. I think right now we need to design
for what the current emulator can do. When things change, we should
remember to update Hob.
Belen
On 15/06/2012 15:31, "Darren Hart" wrote:
>
>
>On 06/15/2012 06:04 AM, Barros Pena, Belen wrote:
>> Sorry, Darren and Liming:
On 06/15/2012 06:04 AM, Barros Pena, Belen wrote:
> Sorry, Darren and Liming: I have one more question about this. Liming,
> correct me if I am wrong, but you mentioned that the only files that can
> be run on the qemu emulator are ext2 and ext3. But Darren's answer seems
> to suggest that you ca
Hi Juergen,
On 06/15/2012 02:07 AM, Jürgen Messerer wrote:
> Dear Darren
>
> You suggested in Bug 2256 the following:
>
> $ bitbake virtual/kernel -c cleansstate
>
> $ bitbake virtual/kernel -c menuconfig
>
> $ bitbake virtual/kernel -c compile -f; bitbake virtual/kernel
>
> Can you tell me w
Sorry, Darren and Liming: I have one more question about this. Liming,
correct me if I am wrong, but you mentioned that the only files that can
be run on the qemu emulator are ext2 and ext3. But Darren's answer seems
to suggest that you can also run hddimg and iso files in the qemu emulator.
Is th
The reorganization of bugzilla has been refined and the new layout is
available for preview at https://bugzilla.yoctodev.org/. After a quick
review I plan to make this change live on production. Expect a short 5
to 10 minute downtime while the changes go live later today.
I've attached the new lay
as i claw my way through the QEMU stuff in yocto, some pedantic
thoughts on how to make the shell scripts more readable, so more
observations from the "runqemu" script.
* all those multiple "echo" lines would look a lot nicer if replaced
by a single "here document", don't you think?
* ex
Thanks Darren and Liming.
It sounds like we should keep things as they are, and that we'll need a
screen that gives you options to both run and deploy an image when you
have built for qemu selecting image types ext2 or ext3 and live.
Belen
On 14/06/2012 22:13, "Darren Hart" wrote:
>
>
>On 06
Dear Darren
You suggested in Bug 2256 the following:
$ bitbake virtual/kernel -c cleansstate
$ bitbake virtual/kernel -c menuconfig
$ bitbake virtual/kernel -c compile -f; bitbake virtual/kernel
Can you tell me what the difference is between
"bitbake virtual/kernel -c compile -f"
and
"bitbake v
Frans Meulenbroeks wrote:
> a run-all-tests.sh script is somewhat problematic as
> different systems have different packages installed so different tests.
The idea is that the top level run-all script looks in the /opt/ptest directory
and runs all package tests that are installed there. It has no
Le Fri, 15 Jun 2012 07:31:45 +0100,
Tomas Frydrych a écrit :
> Hi Darren,
>
> On 14/06/12 22:09, Darren Hart wrote:
> > This solution improves the kick-the-tires
> > experience with poky-tiny, without pulling in all of init,
>
> I think you really should quantify what 'all of init' means, with
27 matches
Mail list logo