Date: Mon, 30 Oct 2017 10:12:53 +0200 From: "Andriy Voskoboinyk" <s3erios@gmail.com> To: "Farhan Khan" <khanzf@gmail.com> Cc: freebsd-wireless@freebsd.org Subject: Re: C2H on rtwn not handled Message-ID: <op.y8ww3rhriew4ia@localhost> In-Reply-To: <9485c341-52db-5cab-b9da-25f3ecc16c13@gmail.com> References: <96dc159c-1d56-5bea-7100-75dd117d828d@gmail.com> <op.y8v9n7tbiew4ia@localhost> <9485c341-52db-5cab-b9da-25f3ecc16c13@gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Mon, 30 Oct 2017 06:28:15 +0200 =D0=B1=D1=83=D0=BB=D0=BE =D0=BD=D0=B0=D0= =BF=D0=B8=D1=81=D0=B0=D0=BD=D0=BE Farhan Khan = <khanzf@gmail.com>: > Hi Andriy, > > Just to be clear, this would mean that in my sc_post_init, I should no= t = > utilize callout_reset, which utilizes r92c_handle_c2h_report, correct?= Yeah, rs_c2h_* fields are not used on RTL8188E* > This appears to be how rtl > > If so, how do I know when a C2H event arrives? (I am not too familiar = = > with C2H or how it works yet). Just check if IMR_TXCCK_88E / IMR_C2HCMD_88E bits are set in interrupt status (R88E_HIMR register, see r92ce_classify_intr() as an example). > > As always, thank you very much. > > On 10/29/2017 07:46 PM, Andriy Voskoboinyk wrote: >> Sun, 29 Oct 2017 08:34:21 +0200 =D0=B1=D1=83=D0=BB=D0=BE =D0=BD=D0=B0= =D0=BF=D0=B8=D1=81=D0=B0=D0=BD=D0=BE Farhan Khan = >> <khanzf@gmail.com>: >> Hi, >> You should not use polling for RTL8188EE - it was mainly used for >> RTL8192C* (since there is no documented way to get events from it) >> and can be enabled on RTL881(1,2)A (but just is not needed here). >> Look into rtwn/rtl8188e/r88e_rx.c - I think you can call >> r88e_ratectl_tx_complete() and/or r88e_handle_c2h_report() indirectly= >> from rtwn_pci_intr() when C2H event arrives. >> >>> Hi all, >>> >>> I am trying to extend the rtwn driver to add RTL8188EE support. I am= = >>> still getting this error whenever I enable the WiFi card: >>> >>> rtwn0: r92c_handle_c2h_task: C2H report 0 (len 0) was not handled >>> >>> From my reading of the code, it appears that the driver is trying t= o = >>> read a status-value from the card, but it fails to return a valid = >>> result. Is there something that I need to do to initialize this? If= = >>> so, what exactly? This appears to be a firmware-specific routine and= I = >>> have enabled the firmware. >>> >>> I have been on this for an extended period of time and am stuck :( >>> >>> Thank you! >>> >>> -- Farhan Khan >>> PGP Fingerprint: B28D 2726 E2BC A97E 3854 5ABE 9A9F 00BC D525 16EE >>> _______________________________________________ >>> freebsd-wireless@freebsd.org mailing list >>> https://lists.freebsd.org/mailman/listinfo/freebsd-wireless >>> To unsubscribe, send any mail to = >>> "freebsd-wireless-unsubscribe@freebsd.org"
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?op.y8ww3rhriew4ia>