Skip to content

[WIP] [RFC] drivers: add gsm (ublox) driver#8602

Closed
vincent-d wants to merge 30 commits intoRIOT-OS:masterfrom
OTAkeys:pr/gsm_ublox
Closed

[WIP] [RFC] drivers: add gsm (ublox) driver#8602
vincent-d wants to merge 30 commits intoRIOT-OS:masterfrom
OTAkeys:pr/gsm_ublox

Conversation

@vincent-d
Copy link
Copy Markdown
Member

Contribution description

This PR adds gsm base driver with an implementation for ublox modules.
This is based on @kaspar030 work (https://github.com/kaspar030/RIOT/tree/add_gsm_driver/) even though I changed the API, and did not re-import the original implementations.

I'd like we discuss the API in this PR and test the implementation with the ublox module (someone can still implement for another module of course ;). I know we can not merge as is, but as I'd like to move forward on this topic, I open the PR early.

So far I can send GET and POST HTTP requests, receive SMS, and do the basic initialization of the module.

Issues/PRs references

#7084 #8542
https://github.com/kaspar030/RIOT/tree/add_gsm_driver/

kaspar030 and others added 22 commits February 20, 2018 13:17
Out-of-band data can be registered through at_add_oob.
Then the user must call at_process_oob when idle to process data
received from the device. If any data matches a registered oob URC,
the associated callback is called.
@vincent-d vincent-d added State: WIP State: The PR is still work-in-progress and its code is not in its final presentable form yet Type: new feature The issue requests / The PR implemements a new feature for RIOT Discussion: RFC The issue/PR is used as a discussion starting point about the item of the issue/PR State: waiting for other PR State: The PR requires another PR to be merged first Area: drivers Area: Device drivers labels Feb 20, 2018
@vincent-d vincent-d requested a review from kaspar030 February 20, 2018 13:30
@stale
Copy link
Copy Markdown

stale bot commented Aug 10, 2019

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. If you want me to ignore this issue, please mark it with the "State: don't stale" label. Thank you for your contributions.

@stale stale bot added the State: stale State: The issue / PR has no activity for >185 days label Aug 10, 2019
@stale stale bot closed this Sep 10, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Area: drivers Area: Device drivers Discussion: RFC The issue/PR is used as a discussion starting point about the item of the issue/PR State: stale State: The issue / PR has no activity for >185 days State: waiting for other PR State: The PR requires another PR to be merged first State: WIP State: The PR is still work-in-progress and its code is not in its final presentable form yet Type: new feature The issue requests / The PR implemements a new feature for RIOT

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants