On Sat, 26 Mar 2011 03:20:52 +0800 wu zhangjin <wuzhang...@gmail.com> wrote:
> > Not sure about long-term stability of this driver, or if changing from
> > rtl8187b to rtl8187 will help fix my lock-up issue discussed in the
> > previous thread - will need to test that some more.
By the way it did NOT produce any lock-ups for me for yesterday and today, and
I even switched my network to previously more problematic WPA2 AES. It looks
like my lock-up problem is specific to rtl8187b and not present with rtl8187.
> By the way, does Fn+F5 work with rtl8187? I mean does rtl8187 provide the
> rfkill interface?
Yes, this is the downside I discovered today. rtl8187 at this moment can't
seem to unblock the "hardware" rfkill via the software interface, i.e. after
running "rfkill unblock wifi", it will only become:
# rfkill list wifi
0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: yes
But manually pressing Fn+F5 key unblocks it successfully. The rtl8187b did not
require manual Fn+F5 at this point, so perhaps the rfkill-handling part could
be ported over from that source into the mainline driver.
> > Another difference between these drivers I spotted: rtl8187b shows Link
> > Quality as "90/100", whereas rtl8187 has "70/70" there.
>
> That is because there was some Loongson specific optimization in the
> rtl8187b driver, perhaps it's time for us to merge that part to the
> mainline rtl8187 and eventually throw rtl8187b away.
I hope more people who use Yeeloong with WiFi could test the new rtl8187 and
check if it works fine for them.
--
With respect,
Roman
signature.asc
Description: PGP signature
