G120 access to gadgeteer modules strategie

I have a prototype that I need complete in the next 2 weeks and I was thinking of using the G120.
I know the new SDK is going to be released soon so I’m not asking that question.
I would like to know if the module drivers are being updated to be used in pure NETMF on the G120 or not?
I just don’t want to send the next week modifying the existing ones to work for me only to have the GHI release a canned solution right after I’m done.
Either way it’s no big deal as it shouldn’t be too complicated to modify; I just would like to know the strategie to tackle this going forward

@ MikeCormier - I’m doing the same but using the HDR.
I very much doubt that GHI will update the module drivers to plain NETMF.
In saying that they are pretty simple to change.

@ Justin
I’m using the HDR as well.
Figured as much, I agree its not that difficult to modify the drivers to suit my needs but my concern is maintaining them as GHI modifies the main base drivers.
It would be nice to have the plain NETMF access built in to the base driver.
I don’t know if this violates some gadgeteer standard or something but I would be willing to update the drivers that I will be using and share them for inclusion into the base driver.

Perhaps someone at GHI would like to weigh in? @ GUS?

what “driver” do you mean?

If you’re talking about a Gadgeteer module, then you’re right some of them may use Gadgeteer specific code that can’t simply be included in a vanilla netmf project, but then again some of them can. Best bet is to go to the source, download the file, add it to a non-Gadgeteer project and see!

If you’re talking about the mainboard support, then I’m sure you’ll find GHI will have that supporting vanilla netmf projects.

@ Brett
For example the gadgeteer cellular radio module.
I know its a seed studio module but just using it as an example as It may need to be almost completely rewritten to work with vanilla NETMF.
I’m not trying to say that its too difficult to do I just wondering what GHI envisioned when they put the gadgeteer sockets on the G120HDR for rapid prototyping.
In my opinoin if the G120HDR is ment to use gadgeteer modules then it should be able to access using the sockets kind of like the FEZ Cerbuino Bee.
I just want to know what is GHI’s strategie on this.
If this will be provided in the new SDK when it’s released great and all my questions are moot.
It it is to have individuals modify the supplied drivers thats fine too but I am suggesting that GHI incorporates the this functionallity into the base driver if supplied from the community.

Right, so really for that all you need is the motherboard to be deemed a Gadgeteer board and that to show up in your designer. That’s one way - the other being as you say, rewrite driver to not use Gadgeteer specific bits (I haven’t looked at the cellular module driver to know why it’d require a rewrite, I’ll take your word for that)