Linux IEEE 802.15.4 and 6LoWPAN development
 help / color / mirror / Atom feed
From: Walter Mack <wmack@componentsw.com>
To: Alexander Aring <alex.aring@gmail.com>
Cc: linux-wpan@vger.kernel.org, alan@signal11.us, simon.vincent@xsilon.com
Subject: Re: [PATCH wpan-next] ieee802154: mrf24j40: support for external rx/tx
Date: Tue, 16 Sep 2014 13:13:12 -0700	[thread overview]
Message-ID: <541899D8.4020101@componentsw.com> (raw)
In-Reply-To: <20140916070156.GB1244@omega>

Alex,

this is not a question of chip revisions. Chips with the same revision 
can be used in designs with or without the external 
transmitter/receiver. Its just that the chip has to be set up to be 
compatible with the design.

On 09/16/2014 12:01 AM, Alexander Aring wrote:
> Alan,
>
> ping?
>
> This looks for me like what Simon Vincent has send about a month ago.
>
> I like more to check on chip revision instead setting module parameter,
> but you have the last word.
>
> Please, handle this in any way which you like. I see now there comming
> more patches for the same issue, I don't like that. We should add
> support for this.
>
> - Alex
>


  reply	other threads:[~2014-09-16 20:13 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-15  5:35 [PATCH wpan-next] ieee802154: mrf24j40: support for external rx/tx Walter Mack
2014-09-16  7:01 ` Alexander Aring
2014-09-16 20:13   ` Walter Mack [this message]
2014-09-16 20:20     ` Alexander Aring
2014-09-23  3:51       ` Alan Ott
2014-09-23  7:19         ` Alexander Aring
2014-09-23  7:58           ` Simon Vincent
2014-09-23  8:06             ` Alexander Aring
2014-09-24  6:11         ` Walter Mack
2014-09-24  6:35           ` Alexander Aring

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=541899D8.4020101@componentsw.com \
    --to=wmack@componentsw.com \
    --cc=alan@signal11.us \
    --cc=alex.aring@gmail.com \
    --cc=linux-wpan@vger.kernel.org \
    --cc=simon.vincent@xsilon.com \
    /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