From owner-freebsd-questions@FreeBSD.ORG Tue Aug 26 11:31:32 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 54E63292 for ; Tue, 26 Aug 2014 11:31:32 +0000 (UTC) Received: from mail-wi0-x230.google.com (mail-wi0-x230.google.com [IPv6:2a00:1450:400c:c05::230]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id DDC7C3BB4 for ; Tue, 26 Aug 2014 11:31:31 +0000 (UTC) Received: by mail-wi0-f176.google.com with SMTP id bs8so4007475wib.15 for ; Tue, 26 Aug 2014 04:31:30 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=references:mime-version:in-reply-to:content-type :content-transfer-encoding:message-id:cc:from:subject:date:to; bh=G64f12uK5ow7Sb93rzVrfVCNuAJeMiwxeSl6wtFAwWA=; b=k8voUyYFf2a1wjJitosoyLP3zjD1eYdBas4jtBkf9Ld5DsbLMqhz/YlMnZCeKrfQmG C8Usr72Bj+TdF29+OWwWR1+VLwxQ6A7R6vQ31yKV0uO4JnOdhQdzutlmW+qNjm7C9FwM 7tfyQ9aKcPiXjMcNNtBjNrAjxfZL4SK5SaSHhbBhPYvxGwBvUSls66N16X8ZTjfoSkmI c1o4Wj9YeWZGnIQ01CkYWDO3AX64QobMFJJvjS+m+0Tr040IDZodN3h/yq2gB96twPWg AxpE2eVFiiLaajyhvmp2/tI1GW2fqHBH0qMtUoNNeDONl89eF2AlMGNSKn2DpyfF4yEZ 5NgA== X-Received: by 10.180.95.135 with SMTP id dk7mr21016480wib.68.1409052690073; Tue, 26 Aug 2014 04:31:30 -0700 (PDT) Received: from [192.168.20.2] ([62.219.134.104]) by mx.google.com with ESMTPSA id la2sm5827198wjb.5.2014.08.26.04.31.28 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 26 Aug 2014 04:31:28 -0700 (PDT) References: <20140826123236.d5313f16.freebsd@edvax.de> Mime-Version: 1.0 (1.0) In-Reply-To: <20140826123236.d5313f16.freebsd@edvax.de> Message-Id: X-Mailer: iPod Mail (10B500) From: atar Subject: Re: TL-WN722N support on FreeBSD. Date: Tue, 26 Aug 2014 14:31:25 +0300 To: Polytropon Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 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 11:31:32 -0000 Ok, I've understood the point. So probably there's no way to use this popula= r TP-LINK dongle with FreeBSD. Disappointed. > 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? >=20 > 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). >=20 >=20 > --=20 > Polytropon > Magdeburg, Germany > Happy FreeBSD user since 4.0 > Andra moi ennepe, Mousa, ...