other than the extensions, obviously.
for example:
./lib/firmware/dabusb/bitstream.bin
./lib/firmware/dabusb/firmware.fw
i know the .fw file may be needed to make this component work, but what is the .bin file for, generally speaking?
whats the difference between .bin and .fw?
The extension is a convention and is usually used to describe the format of the contents of the file, but in actual fact is totally optional.
Having said that I would imagine the the FW is meant to imply FirmWare which is probably a binary BIOS file.
Having said that I would imagine the the FW is meant to imply FirmWare which is probably a binary BIOS file.
"Just think of it as leaving early to avoid the rush" - T Pratchett
i know, but these days (especially wrt to puppy and its really excellent filetype integration with rox) there is only an increasing amount of attention paid to extensions in /linux.The extension is a convention and is usually used to describe the format of the contents of the file, but in actual fact is totally optional.
oh yeah-- fw is firmware and ko is a kernel module (which may require a fw file additionally. there is a table on the debian wiki) but nowhere does it clarify the .bin files.Having said that I would imagine the the FW is meant to imply FirmWare which is probably a binary BIOS file.
given how many there are, and their location, my guess is that .bin is just another way of saying .fw, which takes us right back to what you were saying about conventions.