From owner-freebsd-wireless@freebsd.org Mon May 28 05:34:05 2018 Return-Path: Delivered-To: freebsd-wireless@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 416BAEF91D4 for ; Mon, 28 May 2018 05:34:05 +0000 (UTC) (envelope-from kevlo@ns.kevlo.org) Received: from ns.kevlo.org (220-135-115-6.HINET-IP.hinet.net [220.135.115.6]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "ns.kevlo.org", Issuer "ns.kevlo.org" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 75F5E7CDC7 for ; Mon, 28 May 2018 05:34:03 +0000 (UTC) (envelope-from kevlo@ns.kevlo.org) Received: from ns.kevlo.org (localhost [127.0.0.1]) by ns.kevlo.org (8.15.2/8.15.2) with ESMTPS id w4S5XOQx022878 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Mon, 28 May 2018 13:33:25 +0800 (CST) (envelope-from kevlo@ns.kevlo.org) Received: (from kevlo@localhost) by ns.kevlo.org (8.15.2/8.15.2/Submit) id w4S5XNbD022877; Mon, 28 May 2018 13:33:23 +0800 (CST) (envelope-from kevlo) Date: Mon, 28 May 2018 13:33:23 +0800 From: Kevin Lo To: Yuri Cc: freebsd-wireless Subject: Re: Should if_urtwm be imported? Message-ID: <20180528053323.GA22855@ns.kevlo.org> References: <20180526080902.GA9118@ns.kevlo.org> <27c162fa-3937-c9b9-c3b3-1e3910b62b8b@rawbw.com> <20180526141427.GA11664@ns.kevlo.org> <47c4dfde-1c4f-49eb-c501-05b06bb39c97@rawbw.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <47c4dfde-1c4f-49eb-c501-05b06bb39c97@rawbw.com> User-Agent: Mutt/1.8.0 (2017-02-23) X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.26 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, 28 May 2018 05:34:05 -0000 On Sat, May 26, 2018 at 09:19:39AM -0700, Yuri wrote: > > On 05/26/18 07:14, Kevin Lo wrote: > > Yours is RTL8821AE mPCIe chip which is not supported. > > > Do you know is it generally hard to port the diver for the chipset > available for USB interface to mPCIe interface, like in this case? Why don't you give it a go and see if it's easy or hard to port the diver? > Yuri