From: "Andreas Färber" <afaerber@suse.de>
To: Ben Whitten <ben.whitten@gmail.com>
Cc: starnight@g.ncu.edu.tw, jiri@resnulli.us,
linux-lpwan@lists.infradead.org,
linux-arm-kernel@lists.infradead.org, netdev@vger.kernel.org,
Ben Whitten <ben.whitten@lairdtech.com>,
"David S. Miller" <davem@davemloft.net>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH RFC lora-next 3/4] net: lora: sx1301: add minimal to get transmission out
Date: Sun, 30 Dec 2018 21:21:23 +0100 [thread overview]
Message-ID: <7458afe3-bb00-fec7-d3ed-1a709ebaf03d@suse.de> (raw)
In-Reply-To: <20181219155616.9547-4-ben.whitten@lairdtech.com>
Am 19.12.18 um 16:56 schrieb Ben Whitten:
> diff --git a/drivers/net/lora/sx1301.c b/drivers/net/lora/sx1301.c
> index 0c7b6d0b31af..9bcbb967f307 100644
> --- a/drivers/net/lora/sx1301.c
> +++ b/drivers/net/lora/sx1301.c
> @@ -24,6 +24,44 @@
>
> #include "sx1301.h"
>
> +struct sx1301_tx_header {
> + u8 tx_freq[3];
[...]
> + /* HACK set to 868MHz */
> + hdr->tx_freq[0] = 217;
> + hdr->tx_freq[1] = 0;
> + hdr->tx_freq[3] = 0;
hdr->tx_freq[2]
Regards,
Andreas
--
SUSE Linux GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Felix Imendörffer, Jane Smithard, Graham Norton
HRB 21284 (AG Nürnberg)
next prev parent reply other threads:[~2018-12-30 20:21 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20181219155616.9547-1-ben.whitten@lairdtech.com>
2018-12-19 15:56 ` [PATCH RFC lora-next 1/4] net: lora: sx125x sx1301: correct style warnings Ben Whitten
2018-12-29 0:05 ` Andreas Färber
2019-01-05 7:36 ` Ben Whitten
2018-12-19 15:56 ` [PATCH RFC lora-next 2/4] net: lora: sx1301: add minimal to get AGC working prior to tx work Ben Whitten
2018-12-29 0:58 ` Andreas Färber
2019-01-04 12:42 ` Ben Whitten
2018-12-19 15:56 ` [PATCH RFC lora-next 3/4] net: lora: sx1301: add minimal to get transmission out Ben Whitten
2018-12-30 20:21 ` Andreas Färber [this message]
2018-12-19 15:56 ` [PATCH RFC lora-next 4/4] net: lora: sx1301: introduce a lora frame for packet metadata Ben Whitten
2018-12-30 23:38 ` Andreas Färber
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=7458afe3-bb00-fec7-d3ed-1a709ebaf03d@suse.de \
--to=afaerber@suse.de \
--cc=ben.whitten@gmail.com \
--cc=ben.whitten@lairdtech.com \
--cc=davem@davemloft.net \
--cc=jiri@resnulli.us \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-lpwan@lists.infradead.org \
--cc=netdev@vger.kernel.org \
--cc=starnight@g.ncu.edu.tw \
/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
all inboxes | Powered by JetHome®