From owner-freebsd-questions@FreeBSD.ORG Tue Aug 26 10:32:46 2014 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 2D10A7B5 for ; Tue, 26 Aug 2014 10:32:46 +0000 (UTC) Received: from mx01.qsc.de (mx01.qsc.de [213.148.129.14]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id E44453603 for ; Tue, 26 Aug 2014 10:32:45 +0000 (UTC) Received: from r56.edvax.de (port-92-195-111-1.dynamic.qsc.de [92.195.111.1]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx01.qsc.de (Postfix) with ESMTPS id 690CC3DED5; Tue, 26 Aug 2014 12:32:37 +0200 (CEST) Received: from r56.edvax.de (localhost [127.0.0.1]) by r56.edvax.de (8.14.5/8.14.5) with SMTP id s7QAWagS002972; Tue, 26 Aug 2014 12:32:36 +0200 (CEST) (envelope-from freebsd@edvax.de) Date: Tue, 26 Aug 2014 12:32:36 +0200 From: Polytropon To: atar Subject: Re: TL-WN722N support on FreeBSD. Message-Id: <20140826123236.d5313f16.freebsd@edvax.de> In-Reply-To: References: Reply-To: Polytropon Organization: EDVAX X-Mailer: Sylpheed 3.1.1 (GTK+ 2.24.5; i386-portbld-freebsd8.2) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: "freebsd-questions@freebsd.org" X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 26 Aug 2014 10:32:46 -0000 On Tue, 26 Aug 2014 10:32:24 +0300, atar wrote: > Now, my question is, since the above mentioned device is supported > by Linux via a special atheros firmware module, and since FreeBSD > provides a Linux virtualization, will this device work on a FreeBSD > system by its Linux virtualization capability? Probably this won't work. The Linux support in FreeBSD is in the form of an ABI, an alternative binary interface. This allows Linux _programs_ to make Linux system calls which are then "translated" into BSD system calls. This happens in user space, the "layer" in which programs are running. Device drivers, on the other hand, do not operate in this "layer", they are very tightly connected to the system kernel, using its interfaces. As FreeBSD's kernel space is very different from Linux's kernel space, the driver probably cannot be used 1:1. A rewrite would be required (or at last some major adjustments). -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ...