netdev - [lora-next RFC] Socket details for PF

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Date:   Mon, 5 Nov 2018 16:45:40 +0000
From:   Ben Whitten <Ben.Whitten@...rdtech.com>
To:     "afaerber@...e.de" <afaerber@...e.de>
CC:     "starnight@...cu.edu.tw" <starnight@...cu.edu.tw>,
        "hasnain.virk@....com" <hasnain.virk@....com>,
        "netdev@...r.kernel.org" <netdev@...r.kernel.org>,
        "liuxuenetmail@...il.com" <liuxuenetmail@...il.com>,
        "shess@...sware.de" <shess@...sware.de>
Subject: [lora-next RFC] Socket details for PF_LORA on sx1301

Hi,

Using the test application to send data into a PF_LORA socket I have gotten
the sx1301 driver to a point where I was able to produce a LoRa packet
on the air.

There a few options that this socket will need per transmission from the
upper layers which I have compiled with some questions, I will focus on
the LoRa modulation - will FSK have a different socket type?

Transmission frequency in MHz.
Transmit time - can we use SO_TXTIME sockopt?
Modulation bandwidth.
Transmission power in dBm.
Enable CRC16.
Coding rate.
Spreading factor.
Preamble.

The rest of the info needed to program the sx1301 can be inferred from
the hardware configuration or set as a sysfs entry if needed; for example
which radio (A/B) to use as transmitter.
The reference design only has one radios (A) transmit pins connected so
is a static hardware choice set in DTS.

What would be the best way to get this additional info down to the lora
portion of the socket, setsockopts?

Thanks,
Ben Whitten