RE: [Paparazzi-devel] gps module

[Chtangeev, Maxim]

Thanks, Poine, for adding this topic to the documentation wiki. 

I particularly like the dependency feature of the 'module' approach. For 
example, the gps code may be implemented as modules, one for each gps chip set. 
These gps modules (ublox_lea4p, ublox_lea5h, etc.) could depend on, say, 
gps_nmea module which implements a standard nmea parsing, thereby sharing nmea 
implementation since most gps chip sets operate in ether a proprietary binary 
mode or the standard nmea mode. 

Thanks again,
Max

________________________________________
From: address@hidden address@hidden on behalf of antoine drouin address@hidden
Sent: Thursday, December 16, 2010 7:45 AM
To: address@hidden
Subject: Re: [Paparazzi-devel] gps module

Hello Maxim

I think your question shows a need for a bit of documentation about
modules and subsystems.
I wrote some lines in the wiki (
http://paparazzi.enac.fr/wiki/FirmwareArchitecture ). Feel free to
add/edit.
It might also be the place for a discussion about them.

Regards

Poine

On Mon, Dec 13, 2010 at 11:19 PM, Chtangeev, Maxim
<address@hidden> wrote:
> Friends,
>
> I am working on adding to the gps code for Paprazzi and was hoping to get a
> clarification on the differences between 'subsystems' and 'modules'.
>
> Currently 'gps' is a subsystem with a couple of types: 'ublox_lea4p',
> 'ublox_lea5h". However, reading through the wiki I got a feeling that the
> desired architecture would be to re-implement gps as a module
> (http://paparazzi.enac.fr/wiki/Modules_list).
>
> In the future, do you see 'gps' implemented as a subsystem or a module?
>
> Thanks,
> Max
>
> _______________________________________________
> Paparazzi-devel mailing list
> address@hidden
> http://lists.nongnu.org/mailman/listinfo/paparazzi-devel
>
>

_______________________________________________
Paparazzi-devel mailing list
address@hidden
http://lists.nongnu.org/mailman/listinfo/paparazzi-devel