OXE810 support

OXE810 support

[Sledz, Steffen]

Sorry for sending this message again in a new thread. But i did not got any response to my first try. May be the original thread was in the killfile of the relevant guys. Or is nobody interested in support for new hardware?

> I'm planning to make OXE810 machine support available for the 
> community in a few days (i'm waiting for some feedback from 
> Oxford Semiconductors before).

Everything is ready now for the community. :)

> Now my question is, what's the preferred way to do this (i've 
> no git commit access yet)?
> 
> The wiki says "Aspiring developers are encouraged to request 
> a personal git tree where they can store and share changes. 
> They can then submit these patches for review on the mailing 
> list and when ready, someone with commit rights can merge or 
> if needed cherry pick the changes into the main development branch."
> 
> That sounds OK for me. But i miss a description *how* to do 
> all that (sorry, i'm a CVS, SVN & Co. user/admin for a long 
> time, but i'm not that familiar with the git philosophy). How 
> to create this personal tree? Or means "tree" a "branch" 
> here? How to keep this tree/branch up to date from the dev 
> branch? How to submit the patches to the mailing list? ...?

So herewith i request "a personal git tree" (could be named oxe810) for this stuff or an alternative instruction how to continue.

Steffen

Re: OXE810 support

[Robert Schuster]

[-- Attachment #1: Type: text/plain, Size: 1804 bytes --]

Hi Steffen,
please open a bug report and attach some of your files there. E.g.
the machine configuration.

Regards
Robert

Sledz, Steffen schrieb:
> Sorry for sending this message again in a new thread. But i did not got any response to my first try. May be the original thread was in the killfile of the relevant guys. Or is nobody interested in support for new hardware?
> 
>> I'm planning to make OXE810 machine support available for the 
>> community in a few days (i'm waiting for some feedback from 
>> Oxford Semiconductors before).
> 
> Everything is ready now for the community. :)
> 
>> Now my question is, what's the preferred way to do this (i've 
>> no git commit access yet)?
>>
>> The wiki says "Aspiring developers are encouraged to request 
>> a personal git tree where they can store and share changes. 
>> They can then submit these patches for review on the mailing 
>> list and when ready, someone with commit rights can merge or 
>> if needed cherry pick the changes into the main development branch."
>>
>> That sounds OK for me. But i miss a description *how* to do 
>> all that (sorry, i'm a CVS, SVN & Co. user/admin for a long 
>> time, but i'm not that familiar with the git philosophy). How 
>> to create this personal tree? Or means "tree" a "branch" 
>> here? How to keep this tree/branch up to date from the dev 
>> branch? How to submit the patches to the mailing list? ...?
> 
> So herewith i request "a personal git tree" (could be named oxe810) for this stuff or an alternative instruction how to continue.
> 
> Steffen
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
> 



[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 268 bytes --]

Re: OXE810 support

[Sledz, Steffen]

> please open a bug report and attach some of your files there. E.g.
> the machine configuration.

I did, see http://bugs.openembedded.net/show_bug.cgi?id=4827

Re: OXE810 support

[Sledz, Steffen]

> > please open a bug report and attach some of your files there. E.g.
> > the machine configuration.
> 
> I did, see http://bugs.openembedded.net/show_bug.cgi?id=4827

What's the next step now?

Steffen

Re: OXE810 support

[Robert Schuster]

[-- Attachment #1: Type: text/plain, Size: 622 bytes --]

Hi Steffen,

Sledz, Steffen schrieb:
>>> please open a bug report and attach some of your files there. E.g.
>>> the machine configuration.
>> I did, see http://bugs.openembedded.net/show_bug.cgi?id=4827
> 
> What's the next step now?
sorry for the delay. As it seems no one else bothers testing,
so I am doing it. :)

I applied your patches, will build a minimal image and if everything
goes well I will push your changes.

Afterwards I will propose you for rw access since it would make no sense
if a machine maintainer needs people in between to fix problems for his
own machine.


Regards
Robert


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 268 bytes --]