History log of /dragonfly/sys/contrib/dev/isp/isp_2100.fw.uu (Results 1 – 1 of 1)
Revision (<<< Hide revision tags) (Show revision tags >>>) Date Author Comments
Revision tags: v6.2.1, v6.2.0, v6.3.0, v6.0.1, v6.0.0, v6.0.0rc1, v6.1.0, v5.8.3, v5.8.2, v5.8.1, v5.8.0, v5.9.0, v5.8.0rc1, v5.6.3, v5.6.2, v5.6.1, v5.6.0, v5.6.0rc1, v5.7.0, v5.4.3, v5.4.2, v5.4.1, v5.4.0, v5.5.0, v5.4.0rc1, v5.2.2, v5.2.1, v5.2.0, v5.3.0, v5.2.0rc, v5.0.2, v5.0.1, v5.0.0, v5.0.0rc2, v5.1.0, v5.0.0rc1, v4.8.1
# 6daa0b12 25-Jun-2017 Jan Sucan <sucanjan@fit.cvut.cz>

kernel/isp: Unify firmware handling with the rest of the system.

* Convert firmware binary data from C arrays in a header files to
uuencode .uu files. Byte order of the firmware image is
little-

kernel/isp: Unify firmware handling with the rest of the system.

* Convert firmware binary data from C arrays in a header files to
uuencode .uu files. Byte order of the firmware image is
little-endian. As far as DragonFly BSD supports only little-endian
architectures it's ok. But in case of a big-endian architecture the
byte order must be changed before firmware is processed by the isp
driver.

* Move the .uu images to a sys/contrib/dev/isp.

* Add a script for conversion of firmware stored in arrays in the C
header files to .uu files. This is for getting the firmware changes
from the other BSD systems more easily.

* Remove use of ispfw module that contains firmwares for all of the
isp.4 driver devices. User can pick a module for a particular device
instead of having firmwares for all of the devices loaded.

* Document that the kitchen sink ispfw.ko module with all firmware is
gone.

Submitted-by: Jan Sucan
Dragonfly-bug: <https://bugs.dragonflybsd.org/issues/3044>

show more ...