From: Alexander Aring <alex.aring@gmail.com>
To: Andrey Yurovsky <yurovsky@gmail.com>
Cc: linux-wpan@vger.kernel.org
Subject: Re: Atmel at86rf212 and 'b' support in Linux
Date: Sat, 9 Aug 2014 10:35:44 +0200 [thread overview]
Message-ID: <20140809083542.GA15408@omega> (raw)
In-Reply-To: <CAAkeqgWGgHLeFpaGM-AYFZkfcAMWydcnW__ow+pf5_c0c+C8jA@mail.gmail.com>
On Fri, Aug 08, 2014 at 02:58:21PM -0700, Andrey Yurovsky wrote:
> Hi Alex. I'm working with the at86rf212b and we're using the
> at86rf230.c from mainline. There's a version check there that
> specifically rejects anything except version 1:
>
> case 7:
> chip = "at86rf212";
> if (version == 1) {
> lp->data = &at86rf212_data;
> lp->dev->flags |= IEEE802154_HW_LBT;
> lp->dev->phy->channels_supported[0] = 0x00007FF;
> lp->dev->phy->channels_supported[2] = 0x00007FF;
> } else {
> rc = -ENOTSUPP;
> }
> break;
>
> ...and our hardware returns version 3. I've removed this check and
> things seem to work and I've also discussed it with two Atmel FAEs and
> they don't see any reason for this check to be performed or for the
> driver to have different behavior for the different revisions (they're
> going to send me a change list for the HW either way).
>
> Do you know more about this? Is there a specific issue this check is
> trying to address? If not, would you mind if I submitted a patch that
> removes it?
>
This is there because nobody tested the driver with another version than
1. If you tested it, please send patches. There is no other reason why
we check on version 1 there. If nobody tested it, you can never be sure
it's working then.
- Alex
parent reply other threads:[~2014-08-09 8:35 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <CAAkeqgWGgHLeFpaGM-AYFZkfcAMWydcnW__ow+pf5_c0c+C8jA@mail.gmail.com>]
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=20140809083542.GA15408@omega \
--to=alex.aring@gmail.com \
--cc=linux-wpan@vger.kernel.org \
--cc=yurovsky@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.