From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: Received: from mail-ew0-f207.google.com ([209.85.219.207]:53580 "EHLO mail-ew0-f207.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1758501AbZKESlu (ORCPT ); Thu, 5 Nov 2009 13:41:50 -0500 From: Ivo van Doorn To: Bartlomiej Zolnierkiewicz Subject: Re: [PATCH 06/41] rt2800pci: fix comment about IV/EIV fields Date: Thu, 5 Nov 2009 19:41:53 +0100 Cc: linux-wireless@vger.kernel.org, Gertjan van Wingerde , linux-kernel@vger.kernel.org, "John W. Linville" References: <20091104173151.28463.68742.sendpatchset@localhost.localdomain> <20091104173239.28463.22571.sendpatchset@localhost.localdomain> In-Reply-To: <20091104173239.28463.22571.sendpatchset@localhost.localdomain> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-15" Message-Id: <200911051941.53838.IvDoorn@gmail.com> Sender: linux-wireless-owner@vger.kernel.org List-ID: On Wednesday 04 November 2009, Bartlomiej Zolnierkiewicz wrote: > From: Bartlomiej Zolnierkiewicz > Subject: [PATCH] rt2800pci: fix comment about IV/EIV fields > > The bit tested by hardware is TXD_W3_WIV and its value > equals the negated value of ENTRY_TXD_ENCRYPT_IV bit. > > Signed-off-by: Bartlomiej Zolnierkiewicz Acked-by: Ivo van Doorn > --- > drivers/net/wireless/rt2x00/rt2800pci.c | 4 ++-- > 1 file changed, 2 insertions(+), 2 deletions(-) > > Index: b/drivers/net/wireless/rt2x00/rt2800pci.c > =================================================================== > --- a/drivers/net/wireless/rt2x00/rt2800pci.c > +++ b/drivers/net/wireless/rt2x00/rt2800pci.c > @@ -2206,8 +2206,8 @@ static void rt2800pci_write_tx_desc(stru > > /* > * Always write 0 to IV/EIV fields, hardware will insert the IV > - * from the IVEIV register when ENTRY_TXD_ENCRYPT_IV is set to 0. > - * When ENTRY_TXD_ENCRYPT_IV is set to 1 it will use the IV data > + * from the IVEIV register when TXD_W3_WIV is set to 0. > + * When TXD_W3_WIV is set to 1 it will use the IV data > * from the descriptor. The TXWI_W1_WIRELESS_CLI_ID indicates which > * crypto entry in the registers should be used to encrypt the frame. > */ >