From owner-freebsd-wireless@freebsd.org Mon Oct 30 04:28:17 2017 Return-Path: Delivered-To: freebsd-wireless@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id CB8F0E53B42 for ; Mon, 30 Oct 2017 04:28:17 +0000 (UTC) (envelope-from khanzf@gmail.com) Received: from mail-qk0-x22b.google.com (mail-qk0-x22b.google.com [IPv6:2607:f8b0:400d:c09::22b]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 8124272E6F for ; Mon, 30 Oct 2017 04:28:17 +0000 (UTC) (envelope-from khanzf@gmail.com) Received: by mail-qk0-x22b.google.com with SMTP id x82so14617572qkb.12 for ; Sun, 29 Oct 2017 21:28:17 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=oydEeqqWJUxPrDulyzpTg4kDz5wxLR5Gui4/TcmrWug=; b=ge72n36LrnGEEzU4YaVDeTbwrOUjLLllqZ1f8qhNX7FmTZmNHiwkeABVVnXV75q6AH AcP6m7wgcqJ8+Mxn1PTCvs1BcM++gqiY1l524MdLtKLB7w9GRCX84aXuY8R380DwfZXe 9QTDdi/s7rvXj27r9jWjAtASxSWhfRZbDwwHxbXF8mPRDWOulSn8R5cebYclAUb04V6Z 45eWXbmTjoZyDiqjUDGt+MbFDo6H3FW1i66hgAJljhTGN/XdP7YFTAcSC5MVsHhPBQ1y W8FCPN9RiXQNEOMe/mEXQu8ID4eOYQ1As0TuSeZXr0rF/cUbGH/x3Dwnc1BYcD4c5FPD 5+8g== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=oydEeqqWJUxPrDulyzpTg4kDz5wxLR5Gui4/TcmrWug=; b=scMVTJt9nTF1vyYQ4cBITCEdUa1Pr2EatXJuBc7AlH5LIMTaPgNGoEcW9T+JLkqJSA HliYncGY8V3BnE4arqzyaGfqWqo0Toqv4miA02yeIYgrZ1fnveW1UYe3txQP0zehepGe Zql1I4pmsrKXb2ezGXlyIdhYGGTEikbTMPzScBH3e2VoCO7ht1qzK8j1i+k6AC0rGSCA FLMm7C2TEJZ2yLXO+9qRCgJM8AkqzGqSpvRTMQWdcGKS46JvJQObrgMav1TOW0L91AgP f6ITUlUOq+Yo1jptgIq0sKtivY+X9iV9UvqzOGCO6bFIVt3cxvXz+OqHXa9RDStxX0el rt6g== X-Gm-Message-State: AMCzsaVezqdBl19C1BvmttrSKKztOcp/W7lvWTMceK1CYvfi5+hXiJVN 4xr33uWOor5pFkKDDLijedp2VTS0 X-Google-Smtp-Source: ABhQp+QUUjRN15zS1uO1zftmOKPDjwHogkHOFLuCuD1B3EE2cZyz9yUSyU63O80lHjYdjMBnHDKG3A== X-Received: by 10.55.167.22 with SMTP id q22mr11066549qke.234.1509337696329; Sun, 29 Oct 2017 21:28:16 -0700 (PDT) Received: from pc.farhan.codes ([2001:470:8:209::dead:c0de]) by smtp.gmail.com with ESMTPSA id u127sm8812316qkf.79.2017.10.29.21.28.15 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sun, 29 Oct 2017 21:28:15 -0700 (PDT) Subject: Re: C2H on rtwn not handled To: Andriy Voskoboinyk Cc: freebsd-wireless@freebsd.org References: <96dc159c-1d56-5bea-7100-75dd117d828d@gmail.com> From: Farhan Khan Message-ID: <9485c341-52db-5cab-b9da-25f3ecc16c13@gmail.com> Date: Mon, 30 Oct 2017 00:28:15 -0400 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.4.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 30 Oct 2017 04:28:17 -0000 Hi Andriy, Just to be clear, this would mean that in my sc_post_init, I should not utilize callout_reset, which utilizes r92c_handle_c2h_report, correct? 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). As always, thank you very much. On 10/29/2017 07:46 PM, Andriy Voskoboinyk wrote: > Sun, 29 Oct 2017 08:34:21 +0200 було написано Farhan Khan > : > > 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 to >> 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"