Hi Jes, On Tue, Mar 1, 2016 at 9:05 AM, <Jes.Sorensen@xxxxxxxxxx> wrote: > From: Jes Sorensen <Jes.Sorensen@xxxxxxxxxx> > > Set the correct TRXFF boundary for 8723bu. > > Signed-off-by: Jes Sorensen <Jes.Sorensen@xxxxxxxxxx> > --- > drivers/net/wireless/realtek/rtl8xxxu/rtl8xxxu.c | 5 ++++- > 1 file changed, 4 insertions(+), 1 deletion(-) > > diff --git a/drivers/net/wireless/realtek/rtl8xxxu/rtl8xxxu.c b/drivers/net/wireless/realtek/rtl8xxxu/rtl8xxxu.c > index 3a7fd2c..835eca8 100644 > --- a/drivers/net/wireless/realtek/rtl8xxxu/rtl8xxxu.c > +++ b/drivers/net/wireless/realtek/rtl8xxxu/rtl8xxxu.c > @@ -6182,7 +6182,10 @@ static int rtl8xxxu_init_device(struct ieee80211_hw *hw) > /* > * Set RX page boundary > */ > - rtl8xxxu_write16(priv, REG_TRXFF_BNDY + 2, 0x27ff); > + if (priv->rtlchip == 0x8723b) > + rtl8xxxu_write16(priv, REG_TRXFF_BNDY + 2, 0x3f7f); > + else > + rtl8xxxu_write16(priv, REG_TRXFF_BNDY + 2, 0x27ff); Is this likely to be different for other chipsets in the future? If so, would it make sense to stuff it into the fops structure? Thanks, -- Julian Calaby Email: julian.calaby@xxxxxxxxx Profile: http://www.google.com/profiles/julian.calaby/ -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
