Date: Tue, 26 Aug 2014 14:31:25 +0300 From: atar <atar.yosef@gmail.com> To: Polytropon <freebsd@edvax.de> Cc: "freebsd-questions@freebsd.org" <freebsd-questions@freebsd.org> Subject: Re: TL-WN722N support on FreeBSD. Message-ID: <E7966B00-0394-4F31-9F25-BC2F18DBB5AF@gmail.com> In-Reply-To: <20140826123236.d5313f16.freebsd@edvax.de> References: <C18F5819-A884-4A86-9FBA-FF7CEFF70695@gmail.com> <20140826123236.d5313f16.freebsd@edvax.de>
next in thread | previous in thread | raw e-mail | index | archive | help
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, ...
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?E7966B00-0394-4F31-9F25-BC2F18DBB5AF>