Binary blob: Difference between revisions

Content deleted Content added
External links: Some boards are store firmware binary files in /boot/firmware used for its bootloader; for example, Raspberry Pi.
Tags: Mobile edit Mobile web edit
Many wired network controllers (such as Realtek) are also use microcode to fix bugs; in Linux implementations, its driver is open-sourced, but its microcode file is closed-sourced.
Tags: Mobile edit Mobile web edit
Line 34:
}}</ref> The term ''[[Binary large object|blob]]'' was first used in [[database management system]]s to describe a collection of [[binary data]] stored as a single entity.
 
When [[computer hardware]] vendors provide complete technical documentation for their products, operating system developers are able to write hardware device drivers to be included in the operating system kernels. However, some vendors, such as [[Nvidia#Open-source software support|Nvidia]], do not provide complete documentation for some of their products and instead provide binary-only drivers. This practice is most common for [[Graphics processing unit|accelerated graphics]] drivers, [[Wireless network interface controller|wireless networking device]]s, and hardware [[Disk array controller|RAID controllers]].<ref>{{cite web | url = https://packages.debian.org/source/sid/firmware-nonfree | title = Debian packages built from the source package 'firmware-nonfree' - Binary firmware for various drivers in the Linux kernel | year = 2010 | access-date = 2010-03-25}}</ref> Most notably, binaryclosed-source blobsdrivers are very uncommon for non-wireless [[network interface controller]]s, which can almost always be configured via standard utilities (like [[ifconfig]]) out of the box; [[Theo de Raadt]] of [[OpenBSD]] attributes this to the work done by a single [[FreeBSD]] developer.<ref name=lor-opencon06>{{cite web
|author= Constantine A. Murenin |date= 2006-12-10
|url= https://www.linux.org.ru/news/hardware/1690470