[riot-devel] Driver for the at86rf215

Robert Hartung hartung at ibr.cs.tu-bs.de
Fri Oct 25 08:22:32 CEST 2019


Hi José,
hrmpf. Should've looked again into the list of PRs, was a while ago ;)
Will contribute with reviewing and testing.
Regards
Robert

On 24.10.19 16:26, José Alamos wrote:
> Hi Robert,
> 
> Note there's already a PR for this radio [1].
> It's using 2 `netdev_ieee802154` for handling each radio.
> 
> Maybe you can sync there and contribute with feedback and testing.
> 
> Best,
> José
> 
> [1]: https://github.com/RIOT-OS/RIOT/pull/12128
> On Thu, 2019-10-24 at 16:20 +0200, Robert Hartung wrote:
>> Hello fellow developers,
>>
>> I am targeting this question to developers here first before opening
>> any
>> issues. We are looking to implement a driver for the at86rf215. The
>> challenge here is, that we cannot fit it into the existing at86rf2xx
>> driver for a simple reason: It has two interfaces for Sub-Ghz and
>> 2.4Ghz
>> communication, but shares a single interrupt pin. My idea was to have
>> a
>> single device, which has multiple communication interfaces. From what
>> I've seen and researched about netdev, this is not possible, as a
>> netdev
>> has a driver, which consists of the callbacks, including the isr
>> handler.
>>
>> The Idea would then be to have a meta device for the interrupt
>> handling
>> and then calling the actual isr for the radio that the interrupt was
>> ment for. Any one having a similar problem or any ideas how to solve
>> this issue?
>>
>> Best Regards
>> Robert
>>
> 
> _______________________________________________
> devel mailing list
> devel at riot-os.org
> https://lists.riot-os.org/mailman/listinfo/devel
> 

-- 
Robert Hartung, M.Sc.

Technische Universität Braunschweig
Institut für Betriebssysteme und Rechnerverbund
Mühlenpfordtstr. 23, Raum 115
38106 Braunschweig

Fon: +49 (531) 391 - 3264
Fax: +49 (531) 391 - 5936
E-Mail: hartung at ibr.cs.tu-bs.de


More information about the devel mailing list