Typically if a driver gets broken to the point where it doesn't work due to
the deblobbing, it would fail to compile as well (at least, I'd hope).
I know that, when compiling Linux-libre, it returns a lot of warnings because
of it replacing all the firmware blobs with the */(DEBLOBBED)*/ string, but
it still compiles.
For example, my desktop computer has two ethernet ports. Both complain about
missing firmware, and return this lovely error in dmesg:
[ 2.913103] r8169 0000:0d:00.0 eth1: unable to load firmware patch
/*(DEBLOBBED)*/ (-22)
Yet, I know for a fact the driver works still because for whatever reason,
despite missing firmware, both ethernet ports still continue to function. So,
I don't really think that deblobbing can break any driver functionality, but
I could be wrong as well.
