[riot-devel] Supported platforms

Mic Musk mic.musk at gmail.com
Sat Feb 8 14:16:31 CET 2014


Looks great :)

Cheers,
-- 
Mic

On February 8, 2014 at 6:50:16 PM, Ludwig Ortmann (ludwig.ortmann at fu-berlin.de) wrote:

I just added the radios.  

Cheers, Ludwig  

On Wed, Feb 05, 2014 at 09:39:54AM +0800, Mic Musk wrote:  
> Cool then :-P  
>  
>  
> --   
> Mic Musk  
>  
> On February 5, 2014 at 5:50:38 AM, Emmanuel Baccelli (emmanuel.baccelli at inria.fr) wrote:  
>  
> +1 for the radio in the table.  
>  
> Le 4 févr. 2014 19:27, "Hauke Petersen" <hauke.petersen at fu-berlin.de> a écrit :  
> Hello Mic,  
>  
> I completely agree with you here - the list with the platforms was actually just created this morning and is subject to rework/improvement. We are in the progress of creating dedicated wiki-pages for each platform which would than list all this information about on-board radios and sensors as well as the state of the corresponding drivers. So this information should be available in the wiki soon... But maybe it would be a good idea to already say something about the radio in the main table as this is indeed quite useful information when talking about IoT!  
>  
> Best regards,  
> Hauke  
>  
>  
> On 04.02.2014 19:14, Mic Musk wrote:  
> Hi,  
>  
> I just checked out https://github.com/RIOT-OS/RIOT/wiki/RIOT-Platforms  
>  
> Most of the platforms have a radio, which is one of the key elements to the corresponding platform. But I don't see the radio information listed.  
>  
> It seems to the reader that the "Status" column only reflects the support status of the MCU, not the entire platform. But some radio drivers looks partially supported by the source repository, thus it's somehow confusing to new comers like me to comprehend what "full support" or "partly supported" actually means.  
>  
>  
> Regards,  
> --   
> Mic Musk  
>  
> On February 4, 2014 at 8:53:10 PM, Hauke Petersen (hauke.petersen at fu-berlin.de) wrote:  
>  
> Hi,  
> > What about links to issues related to the family/MCU/board (only  
> > families have labels at the moment)?  
> >  
> > Is supplier related to vendor somehow? I'm wondering because of the betty.  
> The idea was the following: Vendor is the company, that produces the  
> MCU, as this is the source for getting Programming Manuals, Datasheets  
> and so on needed for porting to this device.  
>  
> Supplier was meant to be the source, where you can get the actual  
> platform -> use case is someone who wants to start using RIOT on a  
> target and who will need then to buy a platform, then in the supplier  
> section you can find out, where to get a board or who was responsible  
> for making it...  
>  
> Cheers,  
> Hauke  
> >  
> > Cheers, Ludwig  
> > _______________________________________________  
> > devel mailing list  
> > devel at riot-os.org  
> > http://lists.riot-os.org/mailman/listinfo/devel  
>  
> _______________________________________________  
> devel mailing list  
> devel at riot-os.org  
> http://lists.riot-os.org/mailman/listinfo/devel  
>  
>  
> _______________________________________________  
> devel mailing list  
> devel at riot-os.org  
> http://lists.riot-os.org/mailman/listinfo/devel  
>  
>  
> _______________________________________________  
> devel mailing list  
> devel at riot-os.org  
> http://lists.riot-os.org/mailman/listinfo/devel  
>  
> _______________________________________________  
> devel mailing list  
> devel at riot-os.org  
> http://lists.riot-os.org/mailman/listinfo/devel  

> _______________________________________________  
> devel mailing list  
> devel at riot-os.org  
> http://lists.riot-os.org/mailman/listinfo/devel  

_______________________________________________  
devel mailing list  
devel at riot-os.org  
http://lists.riot-os.org/mailman/listinfo/devel  
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.riot-os.org/pipermail/devel/attachments/20140208/cdfe42d3/attachment.html>


More information about the devel mailing list