Re: [riot-devel] MIPS Port

2016-09-28 Thread Joakim NohlgÄrd
I don't have anything to comment on the PR, but I thought it should be
mentioned that only maintainers can set labels and assign people to an
issue/PR, you'll probably get some labels added on it by the maintainers
soon.

Best regards, Joakim

On Sep 28, 2016 13:52, "Neil Jones"  wrote:

Hi all,

I have just submitted a pull-request for MIPS support.

This is my first pull request and I couldn't work how to apply any
labels to it ? (So go easy on me).

A big thanks goes out to Leon Alrae who started the ball rolling on this
MIPS port.

All reviews welcome.

Cheers,

Neil.

___
devel mailing list
devel@riot-os.org
https://lists.riot-os.org/mailman/listinfo/devel
___
devel mailing list
devel@riot-os.org
https://lists.riot-os.org/mailman/listinfo/devel


Re: [riot-devel] MIPS Port

2016-09-28 Thread Stefan Schmidt

Hello.

On 28/09/16 13:51, Neil Jones wrote:

Hi all,

I have just submitted a pull-request for MIPS support.


What the PR number or link? :)


This is my first pull request and I couldn't work how to apply any
labels to it ? (So go easy on me).

A big thanks goes out to Leon Alrae who started the ball rolling on this
MIPS port.

All reviews welcome.


I guess there would be a way to run it on the 6lowpan clikcers? Is this 
a basic port or do you already support the transceiver (cc2520 or ca-8210)?


regards
Stefan Schmidt
___
devel mailing list
devel@riot-os.org
https://lists.riot-os.org/mailman/listinfo/devel


[riot-devel] mips port

2016-05-13 Thread Neil Jones
Hi Leon,

I see from the riot mailing list that you are working on a mips32 port
of RIOT.

Let me introduce myself, I manage the RTOS / embedded group at
Imagination Technologies and one of the activities my group gets
involved in is helping out open source RTOSes to improve their MIPS
support, for example we have recently improved the MIPS support in FreeRTOS.

TBH RIOT has be off radar somewhat as there was no MIPS support at all,
we have been looking at RTOSes with some MIPS support already (usually
PIC32 which is a somewhat specialised mips32 implementation) and trying
to get the up-to-date with modern mips features.

So its great to see someone working on MIPS support for RIOT and I would
like to offer my assistance, be that loaning or donation of target
hardware, or engineering resource (although we are a small teams) for
patch reviewing and assisting with features etc.

Cheers,

Neil

___
devel mailing list
devel@riot-os.org
https://lists.riot-os.org/mailman/listinfo/devel


Re: [riot-devel] MIPS port

2016-04-27 Thread Leon Alrae
On 27/04/16 21:37, Martine Lenders wrote:
> Hey Leon,
> we have a "WIP" label for PRs so if you have something that *you* deem
> presentable: go for it ;-).
> In general I always think its better to be transparent to the community
> about what you do. This way duplicate work is prevented and you benefit
> from input from the community.

Okay, thanks! I'll come back with the pullreq as soon as I get the code
into good shape.

Regards,
Leon

> 
> Regards,
> Martine
> 
> 2016-04-27 22:29 GMT+02:00 Leon Alrae :
> 
>> Hi,
>>
>> Recently I started porting RIOT OS to MIPS. My initial goal is to
>> support emulated MIPS32r2 cores in QEMU. For now I verified that I'm
>> able to run the examples/hello-world application:
>>
>> main(): This is RIOT! (Version: 2016.03-devel-827-g89959-hppav-mips-malta)
>> Hello World!
>> You are running RIOT on a(n) mips-malta board.
>> This board features a(n) mips_common MCU.
>>
>> There's more work required to run other examples (I think I haven't got
>> Makefiles entirely right as I hit some linking errors for other
>> examples), but I was wondering if reaching the stage where all/most of
>> these apps run on MIPS core emulated by QEMU would be good enough to
>> create the pull request? Or perhaps I should come back once I ported it
>> to the physical board? After QEMU this is my next step but it will
>> happen much later...
>>
>> Thanks,
>> Leon
>>
>> ___
>> devel mailing list
>> devel@riot-os.org
>> https://lists.riot-os.org/mailman/listinfo/devel
>>
> 
> 
> 
> ___
> devel mailing list
> devel@riot-os.org
> https://lists.riot-os.org/mailman/listinfo/devel
> 

___
devel mailing list
devel@riot-os.org
https://lists.riot-os.org/mailman/listinfo/devel


Re: [riot-devel] MIPS port

2016-04-27 Thread Martine Lenders
Hey Leon,
we have a "WIP" label for PRs so if you have something that *you* deem
presentable: go for it ;-).
In general I always think its better to be transparent to the community
about what you do. This way duplicate work is prevented and you benefit
from input from the community.

Regards,
Martine

2016-04-27 22:29 GMT+02:00 Leon Alrae :

> Hi,
>
> Recently I started porting RIOT OS to MIPS. My initial goal is to
> support emulated MIPS32r2 cores in QEMU. For now I verified that I'm
> able to run the examples/hello-world application:
>
> main(): This is RIOT! (Version: 2016.03-devel-827-g89959-hppav-mips-malta)
> Hello World!
> You are running RIOT on a(n) mips-malta board.
> This board features a(n) mips_common MCU.
>
> There's more work required to run other examples (I think I haven't got
> Makefiles entirely right as I hit some linking errors for other
> examples), but I was wondering if reaching the stage where all/most of
> these apps run on MIPS core emulated by QEMU would be good enough to
> create the pull request? Or perhaps I should come back once I ported it
> to the physical board? After QEMU this is my next step but it will
> happen much later...
>
> Thanks,
> Leon
>
> ___
> devel mailing list
> devel@riot-os.org
> https://lists.riot-os.org/mailman/listinfo/devel
>
___
devel mailing list
devel@riot-os.org
https://lists.riot-os.org/mailman/listinfo/devel