On Sun, 22 Oct 2006, Ted Mittelstaedt wrote:
I think it's only device drivers, I've not heard of anything else in
anywhere, other than 3rd party programs that might be in the ports, that do
this.
In the base system, binary parts definitely only for device drivers. A quick
find for .uu files in /usr/src/sys on RELENG_6 reveals:
fledge:/usr/src/sys> find . -name \*.uu
./contrib/dev/ath/public/arm9-le-thumb-elf.hal.o.uu
./contrib/dev/ath/public/armv4-be-elf.hal.o.uu
./contrib/dev/ath/public/armv4-le-elf.hal.o.uu
./contrib/dev/ath/public/i386-elf.hal.o.uu
./contrib/dev/ath/public/mips-be-elf.hal.o.uu
./contrib/dev/ath/public/mips-le-elf.hal.o.uu
./contrib/dev/ath/public/mips1-be-elf.hal.o.uu
./contrib/dev/ath/public/mips1-le-elf.hal.o.uu
./contrib/dev/ath/public/mipsisa32-be-elf.hal.o.uu
./contrib/dev/ath/public/mipsisa32-le-elf.hal.o.uu
./contrib/dev/ath/public/powerpc-be-eabi.hal.o.uu
./contrib/dev/ath/public/powerpc-le-eabi.hal.o.uu
./contrib/dev/ath/public/sh4-le-elf.hal.o.uu
./contrib/dev/ath/public/x86_64-elf.hal.o.uu
./contrib/dev/ath/public/xscale-be-elf.hal.o.uu
./contrib/dev/ath/public/xscale-le-elf.hal.o.uu
./contrib/dev/ath/public/alpha-elf.hal.o.uu
./contrib/dev/ath/public/powerpc-be-elf.hal.o.uu
./contrib/dev/ath/public/sparc64-be-elf.hal.o.uu
./contrib/dev/ath/public/ap30.hal.o.uu
./contrib/dev/ath/public/ap43.hal.o.uu
./contrib/dev/ath/public/ap51.hal.o.uu
./contrib/dev/ath/public/ap61.hal.o.uu
./contrib/dev/ath/public/sparc-be-elf.hal.o.uu
./contrib/dev/nve/amd64/nvenetlib.o.bz2.uu
./contrib/dev/nve/i386/nvenetlib.o.bz2.uu
./contrib/dev/oltr/i386-elf.trlld.o.uu
./dev/hptmv/i386-elf.raid.o.uu
./dev/hptmv/amd64-elf.raid.o.uu
./dev/rr232x/amd64-elf.rr232x_lib.o.uu
./dev/rr232x/i386-elf.rr232x_lib.o.uu
There are a variety of binary-only programs that can be pulled in via the
ports collection -- typically third party applications, such as vmware, etc.
It's worth noting that at least a few of the above are firmware images, not
objects that run on the same CPU as the OS. In some cases, firmware images
aren't licensed for inclusion in FreeBSD, so are installed via the ports
collection. For example, the firmware for the Intel wireless driver.
Robert N M Watson
Computer Laboratory
University of Cambridge
Ted
----- Original Message -----
From: "Antonios Anastasiadis" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Friday, October 20, 2006 2:30 PM
Subject: binary blobs in freebsd
Hello.
I am thinking about using FreeBSD in various places, however before I
do that it would be comfortable to know what binary blobs it includes
in any part of the system, be it binary daemon, binary driver etc.
Two I am aware of are the Atheros Hal and an Adaptec RAID driver.
I did not find any definitive resource of some kind anywhere, hence
the question here.
Thank you.
_______________________________________________
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to
"[EMAIL PROTECTED]"
_______________________________________________
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
_______________________________________________
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
