From: danielhilst@gmail.com (Daniel.)
To: kernelnewbies@lists.kernelnewbies.org
Subject: RF class driver
Date: Wed, 21 Sep 2016 10:07:22 -0300 [thread overview]
Message-ID: <CAF3SDA69f=Q+w6zN=uPa8g6brXTXe9T7ONDp1F08orRBAMBXEA@mail.gmail.com> (raw)
In-Reply-To: <CAF3SDA55MW93H4qEjiTixN4h2W8wmpn6Zr+63sXU-vnD+tYNfQ@mail.gmail.com>
I was trying to make it out-of-tree, but seems not possible or not
easy spottable for me :)
2016-09-21 10:05 GMT-03:00 Daniel. <danielhilst@gmail.com>:
> I look into it,
>
> Still I need to patch if_ether.h and add some ETH_P_*
>
> 2016-09-21 9:57 GMT-03:00 Hayward, Shaun <haywshau@amazon.com>:
>> It might be worth taking a look at the Socket CAN drivers (https://www.kernel.org/doc/Documentation/networking/can.txt). It?s not the same type of hardware as the RF devices you?re working with, but it is a case where a network interface was created for devices that are very different than Ethernet.
>>
>> Shaun
>>
>> On 9/21/16, 8:43 AM, "kernelnewbies-bounces at kernelnewbies.org on behalf of Daniel." <kernelnewbies-bounces at kernelnewbies.org on behalf of danielhilst@gmail.com> wrote:
>>
>> I have a driver for nRF24L01+ (not L0) I'm planing to submit it to
>> main line but before that I was trying to make it a network device. My
>> dificult was to make it fit in the ethernet world since it does not
>> have anything in common to a network card. This one can be found here:
>> https://bitbucket.org/danielhilst/nrf24 the network try is here, but
>> is not finished: https://bitbucket.org/danielhilst/nrf24l01p
>>
>> 2016-09-21 7:08 GMT-03:00 Greg KH <greg@kroah.com>:
>> > On Wed, Sep 21, 2016 at 03:09:09PM +0530, Raul Piper wrote:
>> >> On Wed, Sep 21, 2016 at 1:13 PM, Greg KH <greg@kroah.com> wrote:
>> >> I wanted to know in which class RF Transceivers - (Sub 1 -Ghz
>> >> devices) Linux drivers will fall and where to find them in Linux
>> >> kernel ,
>> >> I grepped keywords like Ghz, Sub , and it leads me to the folder
>> >> drivers/net/wireless/* but I am not getting whether they refer to the
>> >> RF class of drivers or something else.
>> >
>> > Those are wireless networking drivers.
>> >
>> >> Is there a framework for them or
>> >> all will come under Wireless device drivers or network device
>> >> drivers?What is the appropriate mailing list for the same?
>> >
>> > linux-wireless at vger.kernel.org
>> >
>> >> Few example of such devices are -
>> >>
>> >> Sub-1 GHz CC1120-CC1190 - From Texas Instruments
>> >>
>> >> nRF905 - From Nordic Semiconductor
>> >>
>> >> nRF9E5 - From Nordic Semiconductor
>> >>
>> >> nRF24L01 - From Texas Instruments
>> >>
>> >> Si4455 - From Silicon Labs
>> >> OL23xx - From Nxp.
>> >
>> > Those are almost always integrated directly into a wifi chipset, and not
>> > independant. If you have an independant device, the GNU Radio project
>> > might be a good thing to look into.
>> >
>> > good luck!
>> >
>> > greg k-h
>> >
>> > _______________________________________________
>> > Kernelnewbies mailing list
>> > Kernelnewbies at kernelnewbies.org
>> > https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
>>
>>
>>
>> --
>> "Do or do not. There is no try"
>> Yoda Master
>>
>> _______________________________________________
>> Kernelnewbies mailing list
>> Kernelnewbies at kernelnewbies.org
>> https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
>>
>>
>
>
>
> --
> "Do or do not. There is no try"
> Yoda Master
--
"Do or do not. There is no try"
Yoda Master
prev parent reply other threads:[~2016-09-21 13:07 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-20 12:32 RF class driver Raul Piper
2016-09-20 12:43 ` Greg KH
2016-09-20 12:45 ` Raul Piper
2016-09-21 7:43 ` Greg KH
2016-09-21 9:39 ` Raul Piper
2016-09-21 10:08 ` Greg KH
2016-09-21 12:43 ` Daniel.
2016-09-21 12:57 ` Hayward, Shaun
2016-09-21 13:05 ` Daniel.
2016-09-21 13:07 ` Daniel. [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAF3SDA69f=Q+w6zN=uPa8g6brXTXe9T7ONDp1F08orRBAMBXEA@mail.gmail.com' \
--to=danielhilst@gmail.com \
--cc=kernelnewbies@lists.kernelnewbies.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).