All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kalle Valo <kvalo@qca.qualcomm.com>
To: Michal Kazior <michal.kazior@tieto.com>
Cc: linux-wireless@vger.kernel.org, ath10k@lists.infradead.org
Subject: Re: [PATCH] ath10k: add new 4addr related fw_feature
Date: Fri, 22 May 2015 13:46:33 +0300	[thread overview]
Message-ID: <874mn46gae.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <1432037374-26339-1-git-send-email-michal.kazior@tieto.com> (Michal Kazior's message of "Tue, 19 May 2015 14:09:34 +0200")

Michal Kazior <michal.kazior@tieto.com> writes:

> Some firmware revisions pad 4th hw address in
> Native Wifi Rx decap. This is the case with 10.x
> and it was assumed that this is true for all
> firmware images.
>
> However QCA988X with 999.999.0.636 and QCA61X4
> with WLAN.RM.2.0-00088 don't have the padding.
> Hence add a feature flag indicating that the
> padding isn't present so firmware images can
> advertise it appropriately. This way driver will
> behave as it was before with old firmware blobs
> and doesn't cause any regressions from user
> perspective.
>
> Effectively this patch enables QCA988X with
> 999.999.0.636 and QCA61X4 with WLAN.RM.2.0-00088
> to set up client bridging provided user has an
> updated firmware blob.
>
> Signed-off-by: Michal Kazior <michal.kazior@tieto.com>

Thanks, applied.

-- 
Kalle Valo

_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k

WARNING: multiple messages have this Message-ID (diff)
From: Kalle Valo <kvalo@qca.qualcomm.com>
To: Michal Kazior <michal.kazior@tieto.com>
Cc: <ath10k@lists.infradead.org>, <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH] ath10k: add new 4addr related fw_feature
Date: Fri, 22 May 2015 13:46:33 +0300	[thread overview]
Message-ID: <874mn46gae.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <1432037374-26339-1-git-send-email-michal.kazior@tieto.com> (Michal Kazior's message of "Tue, 19 May 2015 14:09:34 +0200")

Michal Kazior <michal.kazior@tieto.com> writes:

> Some firmware revisions pad 4th hw address in
> Native Wifi Rx decap. This is the case with 10.x
> and it was assumed that this is true for all
> firmware images.
>
> However QCA988X with 999.999.0.636 and QCA61X4
> with WLAN.RM.2.0-00088 don't have the padding.
> Hence add a feature flag indicating that the
> padding isn't present so firmware images can
> advertise it appropriately. This way driver will
> behave as it was before with old firmware blobs
> and doesn't cause any regressions from user
> perspective.
>
> Effectively this patch enables QCA988X with
> 999.999.0.636 and QCA61X4 with WLAN.RM.2.0-00088
> to set up client bridging provided user has an
> updated firmware blob.
>
> Signed-off-by: Michal Kazior <michal.kazior@tieto.com>

Thanks, applied.

-- 
Kalle Valo

  reply	other threads:[~2015-05-22 10:47 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-19 12:09 [PATCH] ath10k: add new 4addr related fw_feature Michal Kazior
2015-05-19 12:09 ` Michal Kazior
2015-05-22 10:46 ` Kalle Valo [this message]
2015-05-22 10:46   ` Kalle Valo

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=874mn46gae.fsf@kamboji.qca.qualcomm.com \
    --to=kvalo@qca.qualcomm.com \
    --cc=ath10k@lists.infradead.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=michal.kazior@tieto.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.