Re: [riot-devel] Another category for communication device drivers?

[Hauke Petersen]

Hi Neo,

actually the grouping evolved around the obvious, and are mainly driven 
by the high-level interfaces that these groups implement (netdev, SAUL, 
...). For everything that doesn't fit one of these groups, I'd say we 
just put them 'ungrouped' into the drivers folder. Once we find that it 
is feasible to create a new group, we can always refactor later...


Cheers,
Hauke


On 04.03.2017 10:37, Neo wrote:

Hello RIOT developers,

actually there are 3 categories for device drivers in the RIOT source 
tree: network device drivers, sensor device drivers and memory device 
drivers.


How about adding for example an SPI-Uart? It doesn't belong to one of 
these 3 driver categories.


Should it stay stand-alone - especially in the auto_init section?

Best regards,

Neo

___
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] Images

[Hauke Petersen]

Hi Ilias,

in general this should be well possible. But of course it depends on 
some factors, e.g. the network/link layer technology used (e.g. limited 
throughput of IEEE802.15.4), the camera interface, the image 
resolution/size, and of course the timing requirements.


As of know, RIOT does not support any camera module. So you would need 
to implement some device driver(s) for the module of choice. Also there 
is no USB support in RIOT (yet), so this would also need to be addressed 
when you want to use USB cameras.


However, on first sight it seems to me, that there are quite some simple 
i2C and SPI camera modules on the market, for which it should be easy to 
write/port a driver to RIOT.


Cheers,
Hauke



On 11.03.2017 11:34, Ilias Seitanidis wrote:

Hi,
I apologise  my question was really too abstract.  Could it be 
possible to use a riot device(more or less the most common devices are 
m3, m0) connected to a camera( a raspi cam,  or even a usb camera) 
 take a picture and forward the picture to a more powerful computer 
for further processing? For example there is a windows iot with 
raspberry face recognition project.  Of course I am not comparing rasp 
with an m3 or m0 device and thats the reason that the processing will 
take place in a more powerful machine,  but just taking a picture and 
forward  it.

Thank you in advance!
Best,
Ilias

On Mar 10, 2017 15:10, "Emmanuel Baccelli" > wrote:


Hi Ilias,
what do you mean by "image"?
what do you mean by "external module"?
If you gave a concrete example, it would help.
Best,
Emmanuel

On Fri, Mar 10, 2017 at 9:44 AM, Ilias Seitanidis
mailto:iliasseitani...@gmail.com>> wrote:

Dear all,
Is Riot capable of handling images taken by an external module
and transmitting them?  Of course this also depends on the
hardware but I would like to know thats possible at the os
level.  Thank you in advance!

Best,  Ilias

___
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


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

Re: [riot-devel] netdev2 is now netdev

[Martine Lenders]

Hi,

2017-03-15 11:54 GMT+01:00 Oleg Hahm :

> Hi Martine!
>
> Thanks for the info. Just a short clarification question:
>
> On Wed, Mar 15, 2017 at 11:46:47AM +0100, Martine Lenders wrote:
> > The only pitfall that might be a problem I was able to identify when
> > porting is that the adaption layer to GNRC `gnrc_netdev2` is now called
> > `gnrc_netdev`. So if you still include `sys/include/net/gnrc/netdev.h`
> > somewhere make sure to remove it or replace it with an include of
> > `drivers/include/net/netdev.h`.
>
> That means that I need to write #include "net/netdev.h", right?
>

Yes.

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

Re: [riot-devel] netdev2 is now netdev

[Oleg Hahm]

Hi Martine!

Thanks for the info. Just a short clarification question:

On Wed, Mar 15, 2017 at 11:46:47AM +0100, Martine Lenders wrote:
> The only pitfall that might be a problem I was able to identify when
> porting is that the adaption layer to GNRC `gnrc_netdev2` is now called
> `gnrc_netdev`. So if you still include `sys/include/net/gnrc/netdev.h`
> somewhere make sure to remove it or replace it with an include of
> `drivers/include/net/netdev.h`.

That means that I need to write #include "net/netdev.h", right?

Cheers,
Oleg
-- 
/* The HME is the biggest piece of shit I have ever seen. */
linux-2.6.6/drivers/scsi/esp.h


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

[riot-devel] netdev2 is now netdev

[Martine Lenders]

Hi,
with the last network device based on gnrc_netdev removed we were now able
to rename netdev2 to netdev [1], which is now the only (network stack
independent) API to access a network device.

The only pitfall that might be a problem I was able to identify when
porting is that the adaption layer to GNRC `gnrc_netdev2` is now called
`gnrc_netdev`. So if you still include `sys/include/net/gnrc/netdev.h`
somewhere make sure to remove it or replace it with an include of
`drivers/include/net/netdev.h`.

If you still have some network device that is implemented against the
`gnrc_netdev` that is currently not in master, please port to `netdev2` as
soon as possible.

Cheers,
Martine

[1] https://github.com/RIOT-OS/RIOT/pull/6610
___
devel mailing list
devel@riot-os.org
https://lists.riot-os.org/mailman/listinfo/devel