gumstix

Hi Adam,

On Mon, Oct 1, 2012 at 10:35 PM, adam.yh.lee <adam.yh.lee@...> wrote:
> More information is available  here
> <http://gumstix.org/software-development/open-embedded/209-yocto.html>

Is this an "official" layer from Gumstix?

Best regards,
    Trevor

Hey Trevor,

Yes---this is an official layer from Gumstix (but that certainly
doesn't stop others from contributing).  It is a work in progress and
feedback is welcome as we're keen to make it a great BSP layer for
Overo and future Gumstix boards.

--Ash

On Mon, Oct 1, 2012 at 8:27 PM, Trevor Woerner <twoerner@...> wrote:
> Hi Adam,
>
> On Mon, Oct 1, 2012 at 10:35 PM, adam.yh.lee <adam.yh.lee@...> wrote:
>> More information is available  here
>> <http://gumstix.org/software-development/open-embedded/209-yocto.html>
>
> Is this an "official" layer from Gumstix?
>
> Best regards,
>     Trevor
>
> ------------------------------------------------------------------------------
> Don't let slow site performance ruin your business. Deploy New Relic APM
> Deploy New Relic app performance management and know exactly
> what is happening inside your Ruby, Python, PHP, Java, and .NET app
> Try New Relic at no cost today and get our sweet Data Nerd shirt too!
> http://p.sf.net/sfu/newrelic-dev2dev
> _______________________________________________
> gumstix-users mailing list
> gumstix-users@...
> https://lists.sourceforge.net/lists/listinfo/gumstix-users

Hey Ash,

On Tue, Oct 2, 2012 at 11:20 AM, Ash Charles <ash@...> wrote:
> Yes---this is an official layer from Gumstix (but that certainly
> doesn't stop others from contributing).

Wow, that's awesome. Does this mean the old OpenEmbedded instructions
will become deprecated in favour of this Yocto procedure?

Since this is an official layer from the manufacturer, I would suggest
looking into getting it added to:
http://www.openembedded.org/wiki/LayerIndex

Although I already see a collision in the making... :-(

What is the difference between Yocto and OE-core?



--
View this message in context: http://gumstix.8.n6.nabble.com/YoctoProject-Meta-Gumstix-BSP-has-been-posted-tp4965534p4965544.html
Sent from the Gumstix mailing list archive at Nabble.com.

On Tue, Oct 2, 2012 at 12:07 PM, dtran11 <dtran11@...> wrote:
> What is the difference between Yocto and OE-core?

Please have a look at any of the extensive documentation provided by
the Yocto Project:

    http://www.yoctoproject.org
    http://www.yoctoproject.org/about
    https://wiki.yoctoproject.org/wiki/FAQ
    http://www.yoctoproject.org/documentation
    http://www.yoctoproject.org/docs/current/yocto-project-qs/yocto-project-qs.html

In particular you might be interested in:

    https://wiki.yoctoproject.org/wiki/FAQ#What_is_the_difference_between_OpenEmbedded_and_the_Yocto_Project.3F

Thanks for the info. I am downloading the pre-built yocto binaries right now
from gumstix.org. Does anyone know which Linux Distribution it is? I tried
"uname -a" but it only says "Linux overo" which is pretty generic.

thanks.



--
View this message in context: http://gumstix.8.n6.nabble.com/YoctoProject-Meta-Gumstix-BSP-has-been-posted-tp4965534p4965547.html
Sent from the Gumstix mailing list archive at Nabble.com.

On Tue, Oct 2, 2012 at 8:57 AM, Trevor Woerner <twoerner@...> wrote:
> Wow, that's awesome. Does this mean the old OpenEmbedded instructions
> will become deprecated in favour of this Yocto procedure?
Yes.
>
> Since this is an official layer from the manufacturer, I would suggest
> looking into getting it added to:
> http://www.openembedded.org/wiki/LayerIndex
Working with Yocto now to get official blessing :-)
>
> Although I already see a collision in the making... :-(
Andreas has kindly agreed to change his meta-gumstix layer to a
meta-gumstix-deprecated layer in favour of this one.

--Ash

On Tue, Oct 02, 2012 at 09:07:30AM -0700, dtran11 wrote:
> What is the difference between Yocto and OE-core?

I know everybody pretty much hates analogies, but here's one anyway, just for 
fun... :) Well, some things are not exactly 100% match, but pretty close:

Yocto Project = Canonical - an organization and an umbrella entity for projects underneath
Poky = Ubuntu - a Linux distribution, the main product produced by above
OE-Core = kernel - a center/core piece of the above product, developed by broader community

Like I said, the analogy is quite close, but there are some inconsistencies...

-- 
Denys

It's not based on a single distribution.
If you would like to know what's exactly in it, take a look at these two
files in meta-gumstix directory:

gumstix-console-image.bb
gumstix-xfce-image.bb

Hope it helps!

Adam

On Tue, Oct 2, 2012 at 10:46 AM, dtran11 <dtran11@...> wrote:

> Thanks for the info. I am downloading the pre-built yocto binaries right
> now
> from gumstix.org. Does anyone know which Linux Distribution it is? I tried
> "uname -a" but it only says "Linux overo" which is pretty generic.
>
> thanks.
>
>
>
> --
> View this message in context:
> http://gumstix.8.n6.nabble.com/YoctoProject-Meta-Gumstix-BSP-has-been-posted-tp4965534p4965547.html
> Sent from the Gumstix mailing list archive at Nabble.com.
>
>
> ------------------------------------------------------------------------------
> Don't let slow site performance ruin your business. Deploy New Relic APM
> Deploy New Relic app performance management and know exactly
> what is happening inside your Ruby, Python, PHP, Java, and .NET app
> Try New Relic at no cost today and get our sweet Data Nerd shirt too!
> http://p.sf.net/sfu/newrelic-dev2dev
> _______________________________________________
> gumstix-users mailing list
> gumstix-users@...
> https://lists.sourceforge.net/lists/listinfo/gumstix-users
>

On 10/01/2012 10:35 PM, adam.yh.lee wrote:
> Hello everybody :)
>
> A new version of YoctoProject Meta-Gumstix BSP layer has been made public.
> It is currently running on Kernel 3.5. There are console version and XFCE
> desktop version.  Depending on your need, you can start from either one.
>
> The current stable version is developed to be compatible with YoctoProject
> Poky version 'Denzil' 7.
>
> More information is available  here
> <http://gumstix.org/software-development/open-embedded/209-yocto.html>
>
> Please feel free to participate and make contributions. Also ideas and
> suggestions are appreciated.

It is "The Yocto Project", not Yocto :)

Can you change the name of the page to something more like that.

Thanks,

Philip

>
> Adam
>
>
>
> --
> View this message in context: http://gumstix.8.n6.nabble.com/YoctoProject-Meta-Gumstix-BSP-has-been-posted-tp4965534.html
> Sent from the Gumstix mailing list archive at Nabble.com.
>
> ------------------------------------------------------------------------------
> Don't let slow site performance ruin your business. Deploy New Relic APM
> Deploy New Relic app performance management and know exactly
> what is happening inside your Ruby, Python, PHP, Java, and .NET app
> Try New Relic at no cost today and get our sweet Data Nerd shirt too!
> http://p.sf.net/sfu/newrelic-dev2dev
> _______________________________________________
> gumstix-users mailing list
> gumstix-users@...
> https://lists.sourceforge.net/lists/listinfo/gumstix-users
>
>

Done! Thx,

Adam

On Tue, Oct 2, 2012 at 11:39 AM, Philip Balister <philip@...:

> On 10/01/2012 10:35 PM, adam.yh.lee wrote:
>
>> Hello everybody :)
>>
>> A new version of YoctoProject Meta-Gumstix BSP layer has been made public.
>> It is currently running on Kernel 3.5. There are console version and XFCE
>> desktop version.  Depending on your need, you can start from either one.
>>
>> The current stable version is developed to be compatible with YoctoProject
>> Poky version 'Denzil' 7.
>>
>> More information is available  here
>> <http://gumstix.org/software-**development/open-embedded/209-**yocto.html<http://gumstix.org/software-development/open-embedded/209-yocto.html>
>> >
>>
>> Please feel free to participate and make contributions. Also ideas and
>> suggestions are appreciated.
>>
>
> It is "The Yocto Project", not Yocto :)
>
> Can you change the name of the page to something more like that.
>
> Thanks,
>
> Philip
>
>
>
>> Adam
>>
>>
>>
>> --
>> View this message in context: http://gumstix.8.n6.nabble.**
>> com/YoctoProject-Meta-Gumstix-**BSP-has-been-posted-tp4965534.**html<http://gumstix.8.n6.nabble.com/YoctoProject-Meta-Gumstix-BSP-has-been-posted-tp4965534.html>
>> Sent from the Gumstix mailing list archive at Nabble.com.
>>
>> ------------------------------**------------------------------**
>> ------------------
>> Don't let slow site performance ruin your business. Deploy New Relic APM
>> Deploy New Relic app performance management and know exactly
>> what is happening inside your Ruby, Python, PHP, Java, and .NET app
>> Try New Relic at no cost today and get our sweet Data Nerd shirt too!
>> http://p.sf.net/sfu/newrelic-**dev2dev<http://p.sf.net/sfu/newrelic-dev2dev>
>> ______________________________**_________________
>> gumstix-users mailing list
>> gumstix-users@...>
>> https://lists.sourceforge.net/**lists/listinfo/gumstix-users<https://lists.sourceforge.net/lists/listinfo/gumstix-users>
>>
>>
>>

On Tue, Oct 02, 2012 at 10:46:00AM -0700, dtran11 wrote:
> Thanks for the info. I am downloading the pre-built yocto binaries right now
> from gumstix.org. Does anyone know which Linux Distribution it is? I tried
> "uname -a" but it only says "Linux overo" which is pretty generic.

The distro is called Poky...

-- 
Denys

On Tue, Oct 02, 2012 at 10:54:01AM -0700, Ash Charles wrote:
> On Tue, Oct 2, 2012 at 8:57 AM, Trevor Woerner <twoerner@...> wrote:
> > Wow, that's awesome. Does this mean the old OpenEmbedded instructions
> > will become deprecated in favour of this Yocto procedure?
> Yes.
> >
> > Since this is an official layer from the manufacturer, I would suggest
> > looking into getting it added to:
> > http://www.openembedded.org/wiki/LayerIndex
> Working with Yocto now to get official blessing :-)
> >
> > Although I already see a collision in the making... :-(
> Andreas has kindly agreed to change his meta-gumstix layer to a
> meta-gumstix-deprecated layer in favour of this one.

May I suggest less dramatic renaming? What about meta-gumstix-community or 
something like that?

In light of this agreement with Andreas, I wouldn't mind updating the 
OpenEmbedded LayerIndex Wiki page above. Or you can talk to Paul Eggleton for 
the same.

-- 
Denys

Looks like we should rename
uImage.bin<http://cumulus.gumstix.org/images/angstrom/developer/yocto/uImage.bin>
 --> uImage<http://cumulus.gumstix.org/images/angstrom/developer/yocto/uImage.bin>
  (in http://cumulus.gumstix.org/images/angstrom/developer/yocto/)
for right boot from SD card.

Because now with *uImage.bin *we've got:

*** Unable to read "uImage" from mmc 0:1 ***
*Booting from nand ...*
*
*
*no devices available*
*Wrong Image Format for bootm command*
*ERROR: can't get kernel image!*
*Overo #*


PS: ..and thank you for 3.5 kernel!

--
Rogoshchenkov Nikolay


On Mon, Oct 1, 2012 at 10:35 PM, adam.yh.lee <adam.yh.lee@...> wrote:

> Hello everybody :)
>
> A new version of YoctoProject Meta-Gumstix BSP layer has been made public.
> It is currently running on Kernel 3.5. There are console version and XFCE
> desktop version.  Depending on your need, you can start from either one.
>
> The current stable version is developed to be compatible with YoctoProject
> Poky version 'Denzil' 7.
>
> More information is available  here
> <http://gumstix.org/software-development/open-embedded/209-yocto.html>
>
> Please feel free to participate and make contributions. Also ideas and
> suggestions are appreciated.
>
> Adam
>
>
>
> --
> View this message in context:
> http://gumstix.8.n6.nabble.com/YoctoProject-Meta-Gumstix-BSP-has-been-posted-tp4965534.html
> Sent from the Gumstix mailing list archive at Nabble.com.
>
>
> ------------------------------------------------------------------------------
> Don't let slow site performance ruin your business. Deploy New Relic APM
> Deploy New Relic app performance management and know exactly
> what is happening inside your Ruby, Python, PHP, Java, and .NET app
> Try New Relic at no cost today and get our sweet Data Nerd shirt too!
> http://p.sf.net/sfu/newrelic-dev2dev
> _______________________________________________
> gumstix-users mailing list
> gumstix-users@...
> https://lists.sourceforge.net/lists/listinfo/gumstix-users
>

My bad. It's been fixed now. Thank you,

Adam

On Tue, Oct 2, 2012 at 1:22 PM, Nikolay Rogoshchenkov
<nickolayr@...:

> Looks like we should rename uImage.bin<http://cumulus.gumstix.org/images/angstrom/developer/yocto/uImage.bin>
>  --> uImage<http://cumulus.gumstix.org/images/angstrom/developer/yocto/uImage.bin>
>   (in http://cumulus.gumstix.org/images/angstrom/developer/yocto/)
> for right boot from SD card.
>
> Because now with *uImage.bin *we've got:
>
> *** Unable to read "uImage" from mmc 0:1 ***
> *Booting from nand ...*
> *
> *
> *no devices available*
> *Wrong Image Format for bootm command*
> *ERROR: can't get kernel image!*
> *Overo #*
>
>
> PS: ..and thank you for 3.5 kernel!
>
> --
> Rogoshchenkov Nikolay
>
>
> On Mon, Oct 1, 2012 at 10:35 PM, adam.yh.lee <adam.yh.lee@...:
>
>> Hello everybody :)
>>
>> A new version of YoctoProject Meta-Gumstix BSP layer has been made public.
>> It is currently running on Kernel 3.5. There are console version and XFCE
>> desktop version.  Depending on your need, you can start from either one.
>>
>> The current stable version is developed to be compatible with YoctoProject
>> Poky version 'Denzil' 7.
>>
>> More information is available  here
>> <http://gumstix.org/software-development/open-embedded/209-yocto.html>
>>
>> Please feel free to participate and make contributions. Also ideas and
>> suggestions are appreciated.
>>
>> Adam
>>
>>
>>
>> --
>> View this message in context:
>> http://gumstix.8.n6.nabble.com/YoctoProject-Meta-Gumstix-BSP-has-been-posted-tp4965534.html
>> Sent from the Gumstix mailing list archive at Nabble.com.
>>
>>
>> ------------------------------------------------------------------------------
>> Don't let slow site performance ruin your business. Deploy New Relic APM
>> Deploy New Relic app performance management and know exactly
>> what is happening inside your Ruby, Python, PHP, Java, and .NET app
>> Try New Relic at no cost today and get our sweet Data Nerd shirt too!
>> http://p.sf.net/sfu/newrelic-dev2dev
>> _______________________________________________
>> gumstix-users mailing list
>> gumstix-users@...
>> https://lists.sourceforge.net/lists/listinfo/gumstix-users
>>
>
>
>
> ------------------------------------------------------------------------------
> Don't let slow site performance ruin your business. Deploy New Relic APM
> Deploy New Relic app performance management and know exactly
> what is happening inside your Ruby, Python, PHP, Java, and .NET app
> Try New Relic at no cost today and get our sweet Data Nerd shirt too!
> http://p.sf.net/sfu/newrelic-dev2dev
> _______________________________________________
> gumstix-users mailing list
> gumstix-users@...
> https://lists.sourceforge.net/lists/listinfo/gumstix-users
>
>

Hi,

adam.yh.lee wrote
> Hello everybody :)
> 
> A new version of YoctoProject Meta-Gumstix BSP layer has been made public. 
> It is currently running on Kernel 3.5. There are console version and XFCE
> desktop version.  Depending on your need, you can start from either one.  
> 
> The current stable version is developed to be compatible with YoctoProject
> Poky version 'Denzil' 7. 
> 
> More information is available 
> here
> <http://gumstix.org/software-development/open-embedded/209-yocto.html>  
> 
> Please feel free to participate and make contributions. Also ideas and
> suggestions are appreciated. 
> 
> Adam

This piece of news is very exciting and I look forward to learning and using
the new workflow; including the 'repo' git-management tools.

James Ang



--
View this message in context: http://gumstix.8.n6.nabble.com/YoctoProject-Meta-Gumstix-BSP-has-been-posted-tp4965534p4965561.html
Sent from the Gumstix mailing list archive at Nabble.com.

Hello Adam & Ash,

I just tried the console image with Overo FE/IronSTORM + Tobi, an 4-port,
powered USB hub connected to the OTG port with a keyboard and mouse.

The hub, keyboard and mouse are not detected and can't work.
The same thing with the previous v3.2 kernel too.

It's working with the v3.0 kernel.

Even switching to the USB host port, the hub, KB and mouse are still not
working.

Please advise.

Thanks.

James Ang.




--
View this message in context: http://gumstix.8.n6.nabble.com/YoctoProject-Meta-Gumstix-BSP-has-been-posted-tp4965534p4965562.html
Sent from the Gumstix mailing list archive at Nabble.com.

A small correction to my earlier statement,

On Oct 3, 2012 3:17 PM, "JamesAng" <angweiyang@...> wrote:
>
> Hello Adam & Ash,
>
> I just tried the console image with Overo FE/IronSTORM + Tobi, an 4-port,
> powered USB hub connected to the OTG port with a keyboard and mouse.
>
> The hub, keyboard and mouse are not detected and can't work.
> The same thing with the previous v3.2 kernel too.
>
The hub is detected but it get suspended immediately and does not wake up.
USB peripherals attached to the hub are not detected and doesn't cause the
hub to wakeup too.

I've read that this happened since v3.2 as there's a change in USB
subsystem.

> It's working with the v3.0 kernel.
>
> Even switching to the USB host port, the hub, KB and mouse are still not
> working.

Please advise how to workaround this occurrence.

Thanks.

James Ang

On Tue, Oct 2, 2012 at 8:02 PM, Denys Dmytriyenko <denis@...> wrote:
> On Tue, Oct 02, 2012 at 10:54:01AM -0700, Ash Charles wrote:
>> On Tue, Oct 2, 2012 at 8:57 AM, Trevor Woerner <twoerner@...> wrote:
>> > Wow, that's awesome. Does this mean the old OpenEmbedded instructions
>> > will become deprecated in favour of this Yocto procedure?
>> Yes.
>> >
>> > Since this is an official layer from the manufacturer, I would suggest
>> > looking into getting it added to:
>> > http://www.openembedded.org/wiki/LayerIndex
>> Working with Yocto now to get official blessing :-)
>> >
>> > Although I already see a collision in the making... :-(
>> Andreas has kindly agreed to change his meta-gumstix layer to a
>> meta-gumstix-deprecated layer in favour of this one.
>
> May I suggest less dramatic renaming? What about meta-gumstix-community or
> something like that?
I don't have much of a preference here. Would meta-gumstix-community
be Ok for gumstix? If no complaints I will rename it on monday 8th.
>
> In light of this agreement with Andreas, I wouldn't mind updating the
> OpenEmbedded LayerIndex Wiki page above. Or you can talk to Paul Eggleton for
> the same.
I prefer to have the official meta-gumstix in the layer index although
I personally will use my layer for a while because meta-gumstix layer
is much more than a BSP (too much in my opinion) and therefore linked
to stable release I am not working with at the moment.

Andreas

On Wed, Oct 3, 2012 at 10:04 AM, Andreas Müller
<schnitzeltony@...> wrote:
> I prefer to have the official meta-gumstix in the layer index although
> I personally will use my layer for a while because meta-gumstix layer
> is much more than a BSP (too much in my opinion) and therefore linked
> to stable release I am not working with at the moment.

I think the best solution would be to have one official layer called
meta-gumstix in which we would find a couple of different branches. If
people clone and checkout the master they get the latest unstable
(which would track the Yocto Project's HEAD) which could allow
contributions from the community (much like any other project, via
patches to the mailing list, administered by... someone official from
Gumstix) and would be known to be in constant flux (i.e. it might not
build today, try again tomorrow).

If developers want something "stable" then the official instructions
from Gumstix would talk about using the Yocto Project's denzil release
(for example), cloning the official meta-gumstix layer, but checking
out a "denzil" branch before starting the build.

Perhaps other branches could exist for the work of the other members
of the gumstix development community (i.e. Scott, Sakoman, Andreas,
etc...)?

On Wed, Oct 3, 2012 at 7:04 AM, Andreas Müller
<schnitzeltony@...> wrote:
> I don't have much of a preference here. Would meta-gumstix-community
> be Ok for gumstix? If no complaints I will rename it on monday 8th.
>>
meta-gumstix-community is fine for Gumstix, Inc..  @Andreas, thanks
again for being so accommodating.

The main idea is to provide an 'official' layer and something of a
rallying/starting point for using the fruits of the Yocto Project when
working with Gumstix boards.  I expect others will use their own
layers or versions of meta-gumstix which is the great benefit of
open-source.  Hopefully using repo+git we can (community included!)
craft both a stable BSP for Overo and others and give ready access to
the bleeding edge (repo init -b dev).

--Ash

Hello James, can I ask what your set up is (name of USB hub, keyboard and
mouse)?

I tried a couple different USB hubs in the office (they are pretty generic,
cheap models) and they seem work fine. However the USB hub built into my
Dell monitor doesn't work.

Regards,

Adam

On Wed, Oct 3, 2012 at 6:29 AM, James Ang <angweiyang@...> wrote:

> A small correction to my earlier statement,
>
> On Oct 3, 2012 3:17 PM, "JamesAng" <angweiyang@...> wrote:
> >
> > Hello Adam & Ash,
> >
> > I just tried the console image with Overo FE/IronSTORM + Tobi, an 4-port,
> > powered USB hub connected to the OTG port with a keyboard and mouse.
> >
> > The hub, keyboard and mouse are not detected and can't work.
> > The same thing with the previous v3.2 kernel too.
> >
> The hub is detected but it get suspended immediately and does not wake up.
> USB peripherals attached to the hub are not detected and doesn't cause the
> hub to wakeup too.
>
> I've read that this happened since v3.2 as there's a change in USB
> subsystem.
>
> > It's working with the v3.0 kernel.
> >
> > Even switching to the USB host port, the hub, KB and mouse are still not
> > working.
>
> Please advise how to workaround this occurrence.
>
> Thanks.
>
> James Ang
>
>
> ------------------------------------------------------------------------------
> Don't let slow site performance ruin your business. Deploy New Relic APM
> Deploy New Relic app performance management and know exactly
> what is happening inside your Ruby, Python, PHP, Java, and .NET app
> Try New Relic at no cost today and get our sweet Data Nerd shirt too!
> http://p.sf.net/sfu/newrelic-dev2dev
> _______________________________________________
> gumstix-users mailing list
> gumstix-users@...
> https://lists.sourceforge.net/lists/listinfo/gumstix-users
>
>

On Wed, Oct 3, 2012 at 6:05 PM, Adam Lee <adam.yh.lee@...> wrote:
> Hello James, can I ask what your set up is (name of USB hub, keyboard and
> mouse)?
>
> I tried a couple different USB hubs in the office (they are pretty generic,
> cheap models) and they seem work fine. However the USB hub built into my
> Dell monitor doesn't work.
>
> Regards,
>
> Adam
I had the same hub problem here. I worked it around by [1] and there
were kernel patches suggested in [2-3] to workaround.

Andreas

[1] http://gitorious.org/schnitzeltony-oe-meta/meta-gumstix/commit/fe09baad389e4e113fba363dc56ade2e7422210d
[2] http://www.spinics.net/lists/linux-usb/msg71529.html
[3] http://www.spinics.net/lists/linux-usb/msg71530.html

> I personally will use my layer for a while because meta-gumstix layer
> is much more than a BSP (too much in my opinion)

This is a good point, and I agree!

Perhaps it would be better for Gumstix to do 2 layers:

meta-gumstix-bsp: a "pure" bsp layer, machine related recipes/bbappends only
meta-gumstix: a layer for recreating the Gumstix provided images

That way folks who don't want the image related recipes can just use
the meta-gumstix-bsp layer.

Steve


---------- Forwarded message ----------
From: Andreas Müller <schnitzeltony@...>
Date: Wed, Oct 3, 2012 at 7:04 AM
Subject: Re: [Gumstix-users] YoctoProject Meta-Gumstix BSP has been posted
To: "General mailing list for gumstix users."
<gumstix-users@...>


On Tue, Oct 2, 2012 at 8:02 PM, Denys Dmytriyenko <denis@...> wrote:
> On Tue, Oct 02, 2012 at 10:54:01AM -0700, Ash Charles wrote:
>> On Tue, Oct 2, 2012 at 8:57 AM, Trevor Woerner <twoerner@...> wrote:
>> > Wow, that's awesome. Does this mean the old OpenEmbedded instructions
>> > will become deprecated in favour of this Yocto procedure?
>> Yes.
>> >
>> > Since this is an official layer from the manufacturer, I would suggest
>> > looking into getting it added to:
>> > http://www.openembedded.org/wiki/LayerIndex
>> Working with Yocto now to get official blessing :-)
>> >
>> > Although I already see a collision in the making... :-(
>> Andreas has kindly agreed to change his meta-gumstix layer to a
>> meta-gumstix-deprecated layer in favour of this one.
>
> May I suggest less dramatic renaming? What about meta-gumstix-community or
> something like that?
I don't have much of a preference here. Would meta-gumstix-community
be Ok for gumstix? If no complaints I will rename it on monday 8th.
>
> In light of this agreement with Andreas, I wouldn't mind updating the
> OpenEmbedded LayerIndex Wiki page above. Or you can talk to Paul Eggleton for
> the same.
I prefer to have the official meta-gumstix in the layer index although
I personally will use my layer for a while because meta-gumstix layer
is much more than a BSP (too much in my opinion) and therefore linked
to stable release I am not working with at the moment.

Andreas

------------------------------------------------------------------------------
Don't let slow site performance ruin your business. Deploy New Relic APM
Deploy New Relic app performance management and know exactly
what is happening inside your Ruby, Python, PHP, Java, and .NET app
Try New Relic at no cost today and get our sweet Data Nerd shirt too!
http://p.sf.net/sfu/newrelic-dev2dev
_______________________________________________
gumstix-users mailing list
gumstix-users@...
https://lists.sourceforge.net/lists/listinfo/gumstix-users

Hi Adam,

adam.yh.lee wrote
> Hello James, can I ask what your set up is (name of USB hub, keyboard and
> mouse)?
> 
> I tried a couple different USB hubs in the office (they are pretty
> generic,
> cheap models) and they seem work fine. However the USB hub built into my
> Dell monitor doesn't work.
> 
> Regards,
> Adam

I tried 2 different cheap hub, powered with a 5V PSU. From dmesg,

a) idVendor=05e3, idProduct=0608, Mfr=0, Product=1, SerialNumber=0,
Product:USB 2.0 Hub, 4 ports detected.
[No brand. It is using a Genesys Logic GL850G chipset]
b) idVendor=1a40,idProduct=0101, Mfr=0, Product=1, SerialNumber=0,
Product:USB 2.0 Hub, 4 ports detected.
[Brand=CLiPtec. Unknown chipset]

For the mouse,
idVendor=0458, idProduct=0007, Mfr=1, Product=2, SerialNumber=0, Product:
Optical Mouse, Manufacturer: KYE,
generic-usb 0003:0458:0007.0001: input: USB HID v1.10 Mouse
[Brand: Asustek]

For the keyboard,
idVendor=04d9, idProduct=1503, Mfr=1, Product=2, SerialNumber=0, Product:
USB Keyboard, Manufacturer=<blank>,
generic-usb 0003:04D9:1503.0002: input: USB HID v1.10 Keyboard
[Brand: Asustek]

Tested with both OTG port (with white OTG cable from gumstix) and Host port
(normal USB cable) have the same result.

James Ang.



--
View this message in context: http://gumstix.8.n6.nabble.com/YoctoProject-Meta-Gumstix-BSP-has-been-posted-tp4965534p4965586.html
Sent from the Gumstix mailing list archive at Nabble.com.

Hi Andreas,


Andreas Müller-2 wrote
> On Wed, Oct 3, 2012 at 6:05 PM, Adam Lee <

> adam.yh.lee@

> > wrote:
>> Hello James, can I ask what your set up is (name of USB hub, keyboard and
>> mouse)?
>>
>> I tried a couple different USB hubs in the office (they are pretty
>> generic,
>> cheap models) and they seem work fine. However the USB hub built into my
>> Dell monitor doesn't work.
>>
>> Regards,
>>
>> Adam
> I had the same hub problem here. I worked it around by [1] and there
> were kernel patches suggested in [2-3] to workaround.
> 
> Andreas
> 
> [1]
> http://gitorious.org/schnitzeltony-oe-meta/meta-gumstix/commit/fe09baad389e4e113fba363dc56ade2e7422210d
> [2] http://www.spinics.net/lists/linux-usb/msg71529.html
> [3] http://www.spinics.net/lists/linux-usb/msg71530.html

For the [1] change, the change needed is "# CONFIG_USB_SUSPEND is not set"
right? i.e. to just disable USB suspend.
The rest of the USB setting should remains.

[2] & [3] points out that it is with Genesys Logic chipset and some rare
devices.

Hope the above patches get into mainline soon.

James Ang.



--
View this message in context: http://gumstix.8.n6.nabble.com/YoctoProject-Meta-Gumstix-BSP-has-been-posted-tp4965534p4965587.html
Sent from the Gumstix mailing list archive at Nabble.com.

Ash Charles-2 wrote
> The main idea is to provide an 'official' layer and something of a
> rallying/starting point for using the fruits of the Yocto Project when
> working with Gumstix boards.  I expect others will use their own
> layers or versions of meta-gumstix which is the great benefit of
> open-source.  Hopefully using repo+git we can (community included!)
> craft both a stable BSP for Overo and others and give ready access to
> the bleeding edge (repo init -b dev).
> 
> --Ash


Steve Sakoman wrote
> Perhaps it would be better for Gumstix to do 2 layers:
> 
> meta-gumstix-bsp: a "pure" bsp layer, machine related recipes/bbappends
> only
> meta-gumstix: a layer for recreating the Gumstix provided images
> 
> That way folks who don't want the image related recipes can just use
> the meta-gumstix-bsp layer.
> 
> Steve

I felt Steve's suggestion to split into 2 layers is a good idea from the
point of maintenance and integration.

Trevor's point of aligning to Yocto Project's way of having a common branch
naming would be less confusing and aid in migrating to newer branch easily.
Even Scott's earlier post on using Yocto follows the same process, layering
and branch naming.

For those who do not intend to use Repo (now), they can still follow Yocto
Project's Guide and not have to read the Repo's XML file to get the correct
git and revision.

The point is branching and naming convention.

Anyway, Repo is useful to automate the clone of the various git in either
workflow.

Just my $0.02 thought.

James Ang.



--
View this message in context: http://gumstix.8.n6.nabble.com/YoctoProject-Meta-Gumstix-BSP-has-been-posted-tp4965534p4965588.html
Sent from the Gumstix mailing list archive at Nabble.com.

On Thu, Oct 4, 2012 at 4:04 AM, JamesAng <angweiyang@...> wrote:
> Hi Andreas,
>
>
> Andreas Müller-2 wrote
>> On Wed, Oct 3, 2012 at 6:05 PM, Adam Lee &lt;
>
>> adam.yh.lee@
>
>> &gt; wrote:
>>> Hello James, can I ask what your set up is (name of USB hub, keyboard and
>>> mouse)?
>>>
>>> I tried a couple different USB hubs in the office (they are pretty
>>> generic,
>>> cheap models) and they seem work fine. However the USB hub built into my
>>> Dell monitor doesn't work.
>>>
>>> Regards,
>>>
>>> Adam
>> I had the same hub problem here. I worked it around by [1] and there
>> were kernel patches suggested in [2-3] to workaround.
>>
>> Andreas
>>
>> [1]
>> http://gitorious.org/schnitzeltony-oe-meta/meta-gumstix/commit/fe09baad389e4e113fba363dc56ade2e7422210d
>> [2] http://www.spinics.net/lists/linux-usb/msg71529.html
>> [3] http://www.spinics.net/lists/linux-usb/msg71530.html
>
> For the [1] change, the change needed is "# CONFIG_USB_SUSPEND is not set"
> right? i.e. to just disable USB suspend.
Yes
> The rest of the USB setting should remains.
A bit confused me that by disabling CONFIG_USB_SUSPEND the entry
CONFIG_USB_OTG is removed. This is no problem since OTG is handled by
gadget drivers.

>
> [2] & [3] points out that it is with Genesys Logic chipset and some rare
> devices.
>
> Hope the above patches get into mainline soon.
>
> James Ang.
>
Andreas

Hello

In our project we wanted to use Gumstix + Caspa camera for image 
processing. We have everything set up and first drafts of algorithms 
written. But we observed strange behavior of the camera.

When we place the camera in one point and take a picture, on the image 
we are marking the center of the picture. Now, if camera stays in the 
same place, but is rotated a few degrees the center of new image is not 
in the same place as it used to be, sometimes it is in very different place.

We are thinking, that image sensor isn't in the center of the camera so 
to speak, also it may be at some angle.

So I wanted to ask, if someone encountered the same behavior with this 
camera, or we just got some faulty model?

Or maybe you have some other explanation of this situation?

Andreas Müller-2 wrote
>> For the [1] change, the change needed is "# CONFIG_USB_SUSPEND is not
>> set"
>> right? i.e. to just disable USB suspend.
> Yes
>> The rest of the USB setting should remains.
> A bit confused me that by disabling CONFIG_USB_SUSPEND the entry
> CONFIG_USB_OTG is removed. This is no problem since OTG is handled by
> gadget drivers.

Hmmm.. maybe the proper way is to use [2] & [3]
or take the fight to v3.6!! LOL..

James Ang.




--
View this message in context: http://gumstix.8.n6.nabble.com/YoctoProject-Meta-Gumstix-BSP-has-been-posted-tp4965534p4965593.html
Sent from the Gumstix mailing list archive at Nabble.com.

On Mon, Oct 1, 2012 at 9:35 PM, adam.yh.lee <adam.yh.lee@...> wrote:

> Hello everybody :)
>
> A new version of YoctoProject Meta-Gumstix BSP layer has been made public.
> It is currently running on Kernel 3.5. There are console version and XFCE
> desktop version.  Depending on your need, you can start from either one.
>
> The current stable version is developed to be compatible with YoctoProject
> Poky version 'Denzil' 7.
>
> More information is available  here
> <http://gumstix.org/software-development/open-embedded/209-yocto.html>
>
> Please feel free to participate and make contributions. Also ideas and
> suggestions are appreciated.
>

Hi Adam,

I have a procedural question.  How do I track your upstream
build/layout/packaging/patch changes in my own build tree?

I can go to ${path}/Gumstix-YoctoProject-Repo/ and run git pull there.

Then is the proper procedure to cd to my $path/yocto/ directory and run
"repo sync", followed by bitbake {image}

Thanks,

Curt.
-- 
Curtis Olson:
http://www.atiak.com - http://aem.umn.edu/~uav/
http://www.flightgear.org - http://gallinazo.flightgear.org

Hey Curtis,

On Thu, Oct 4, 2012 at 8:39 AM, Curtis Olson <curtolson@...> wrote:
> I have a procedural question.  How do I track your upstream
> build/layout/packaging/patch changes in my own build tree?
>
> I can go to ${path}/Gumstix-YoctoProject-Repo/ and run git pull there.
>
> Then is the proper procedure to cd to my $path/yocto/ directory and run
> "repo sync", followed by bitbake {image}
If you want to maintain your own repo, just git clone the
Gumstix-YoctoProject-Repo and make whatever changes you want then
re-do your repo init (you don't have to blow away your previously
checked out content).  See the customize section of this page
https://github.com/gumstix/Gumstix-YoctoProject-Repo.

Repo actually checks out the git repository to .repo/manifest so
nominally, you can just edit it in there (as well as adding a
'local-manifest.xml' file apparently...not tried this).  This usually
ends up confusing me though so I prefer to keep my copy of the
manifest repo separately checked out.

--Ash

On Wed, Oct 3, 2012 at 10:35 AM, Steve Sakoman <sakoman@...> wrote:
> This is a good point, and I agree!
>
> Perhaps it would be better for Gumstix to do 2 layers:
>
> meta-gumstix-bsp: a "pure" bsp layer, machine related recipes/bbappends only
> meta-gumstix: a layer for recreating the Gumstix provided images
>
> That way folks who don't want the image related recipes can just use
> the meta-gumstix-bsp layer.
Yeah---this seems reasonable to me.  I assume kernel and u-boot
receipes still belong in a BSP?
For the proposed 'meta-gumstix' layer which would contain gumstix
images and recipes we think are interesting, do we need a more
descriptive name than 'meta-gumstix'?

--Ash

On Thu, Oct 4, 2012 at 9:17 AM, Ash Charles <ash@...> wrote:
> On Wed, Oct 3, 2012 at 10:35 AM, Steve Sakoman <sakoman@...> wrote:
>> This is a good point, and I agree!
>>
>> Perhaps it would be better for Gumstix to do 2 layers:
>>
>> meta-gumstix-bsp: a "pure" bsp layer, machine related recipes/bbappends only
>> meta-gumstix: a layer for recreating the Gumstix provided images
>>
>> That way folks who don't want the image related recipes can just use
>> the meta-gumstix-bsp layer.
> Yeah---this seems reasonable to me.  I assume kernel and u-boot
> receipes still belong in a BSP?

Yes, just things that are machine specific  -- boot loaders, kernel,
things like custom alsa-state.

Basically anything that would produce an overo package (vs an "all" or
"armv7a-vfp-neon" package).

> For the proposed 'meta-gumstix' layer which would contain gumstix
> images and recipes we think are interesting, do we need a more
> descriptive name than 'meta-gumstix'?

No strong opinion on that!

Steve

Great ideas.
So I take that meta-gumstix should depend on meta-gumstix-bsp? (ie can't
build an image with meta-gumstix without meta-gumstix-bsp)

On Thu, Oct 4, 2012 at 9:25 AM, Steve Sakoman <sakoman@...> wrote:

> On Thu, Oct 4, 2012 at 9:17 AM, Ash Charles <ash@...> wrote:
> > On Wed, Oct 3, 2012 at 10:35 AM, Steve Sakoman <sakoman@...>
> wrote:
> >> This is a good point, and I agree!
> >>
> >> Perhaps it would be better for Gumstix to do 2 layers:
> >>
> >> meta-gumstix-bsp: a "pure" bsp layer, machine related recipes/bbappends
> only
> >> meta-gumstix: a layer for recreating the Gumstix provided images
> >>
> >> That way folks who don't want the image related recipes can just use
> >> the meta-gumstix-bsp layer.
> > Yeah---this seems reasonable to me.  I assume kernel and u-boot
> > receipes still belong in a BSP?
>
> Yes, just things that are machine specific  -- boot loaders, kernel,
> things like custom alsa-state.
>
> Basically anything that would produce an overo package (vs an "all" or
> "armv7a-vfp-neon" package).
>
> > For the proposed 'meta-gumstix' layer which would contain gumstix
> > images and recipes we think are interesting, do we need a more
> > descriptive name than 'meta-gumstix'?
>
> No strong opinion on that!
>
> Steve
>

On Thu, Oct 4, 2012 at 2:42 PM, Adam Lee <adam.yh.lee@...> wrote:
> Great ideas.
> So I take that meta-gumstix should depend on meta-gumstix-bsp? (ie can't
> build an image with meta-gumstix without meta-gumstix-bsp)

Yes, but meta-gumstix-bsp should be usable without meta-gumstix.

In fact meta-gumstix-bsp should be usable with just oe-core and no other layers.

Steve

> On Thu, Oct 4, 2012 at 9:25 AM, Steve Sakoman <sakoman@...> wrote:
>>
>> On Thu, Oct 4, 2012 at 9:17 AM, Ash Charles <ash@...> wrote:
>> > On Wed, Oct 3, 2012 at 10:35 AM, Steve Sakoman <sakoman@...>
>> > wrote:
>> >> This is a good point, and I agree!
>> >>
>> >> Perhaps it would be better for Gumstix to do 2 layers:
>> >>
>> >> meta-gumstix-bsp: a "pure" bsp layer, machine related recipes/bbappends
>> >> only
>> >> meta-gumstix: a layer for recreating the Gumstix provided images
>> >>
>> >> That way folks who don't want the image related recipes can just use
>> >> the meta-gumstix-bsp layer.
>> > Yeah---this seems reasonable to me.  I assume kernel and u-boot
>> > receipes still belong in a BSP?
>>
>> Yes, just things that are machine specific  -- boot loaders, kernel,
>> things like custom alsa-state.
>>
>> Basically anything that would produce an overo package (vs an "all" or
>> "armv7a-vfp-neon" package).
>>
>> > For the proposed 'meta-gumstix' layer which would contain gumstix
>> > images and recipes we think are interesting, do we need a more
>> > descriptive name than 'meta-gumstix'?
>>
>> No strong opinion on that!
>>
>> Steve
>
>

On Thu, Oct 04, 2012 at 03:33:16PM -0700, Steve Sakoman wrote:
> On Thu, Oct 4, 2012 at 2:42 PM, Adam Lee <adam.yh.lee@...> wrote:
> > Great ideas.
> > So I take that meta-gumstix should depend on meta-gumstix-bsp? (ie can't
> > build an image with meta-gumstix without meta-gumstix-bsp)
> 
> Yes, but meta-gumstix-bsp should be usable without meta-gumstix.
> 
> In fact meta-gumstix-bsp should be usable with just oe-core and no other layers.

That is a worthy goal, yes! :)

-- 
Denys

> > On Thu, Oct 4, 2012 at 9:25 AM, Steve Sakoman <sakoman@...> wrote:
> >>
> >> On Thu, Oct 4, 2012 at 9:17 AM, Ash Charles <ash@...> wrote:
> >> > On Wed, Oct 3, 2012 at 10:35 AM, Steve Sakoman <sakoman@...>
> >> > wrote:
> >> >> This is a good point, and I agree!
> >> >>
> >> >> Perhaps it would be better for Gumstix to do 2 layers:
> >> >>
> >> >> meta-gumstix-bsp: a "pure" bsp layer, machine related recipes/bbappends
> >> >> only
> >> >> meta-gumstix: a layer for recreating the Gumstix provided images
> >> >>
> >> >> That way folks who don't want the image related recipes can just use
> >> >> the meta-gumstix-bsp layer.
> >> > Yeah---this seems reasonable to me.  I assume kernel and u-boot
> >> > receipes still belong in a BSP?
> >>
> >> Yes, just things that are machine specific  -- boot loaders, kernel,
> >> things like custom alsa-state.
> >>
> >> Basically anything that would produce an overo package (vs an "all" or
> >> "armv7a-vfp-neon" package).
> >>
> >> > For the proposed 'meta-gumstix' layer which would contain gumstix
> >> > images and recipes we think are interesting, do we need a more
> >> > descriptive name than 'meta-gumstix'?
> >>
> >> No strong opinion on that!
> >>
> >> Steve
> >
> >
> 
> ------------------------------------------------------------------------------
> Don't let slow site performance ruin your business. Deploy New Relic APM
> Deploy New Relic app performance management and know exactly
> what is happening inside your Ruby, Python, PHP, Java, and .NET app
> Try New Relic at no cost today and get our sweet Data Nerd shirt too!
> http://p.sf.net/sfu/newrelic-dev2dev
> _______________________________________________
> gumstix-users mailing list
> gumstix-users@...
> https://lists.sourceforge.net/lists/listinfo/gumstix-users
>