News for hackers. Stuff that matters.
Re:“Blob-free OpenBSD kernel needed” by seba_dos1 on Saturday June 06, 2015 @05:29PM (#9672343)
You still cannot be sure that WiFi blob isn't being reflashed over the air.

Sure, it's harder to mess with reflashable firmware stored inside the device. However, it's only just like you said - a change on priority list, nothing else. Differentiating this in terms of freedom is a hypocrisy.

Anyway. Kernel just provides you an interface to load such firmware into your device. When the firmware is freely redistributable, it's also included in the kernel source tree. Nothing more, nothing less. It's up to you to decide what to do with it - you can easily look up all the needed info and remove unwanted firmware files.

For me there's no difference where it's stored. Closed firmware is closed firmware. We either have to accept it or not use PCs at all.

In the meantime, we should rather focus on producing stuff that increasingly stops requiring it, instead of aimlessly fighting with kernel developers.

Re:“Blob-free OpenBSD kernel needed” by ergethaxsd on Saturday June 06, 2015 @05:48PM (#9672402)
> "When the firmware is freely redistributable, it's also included in the kernel source tree. Nothing more, nothing less. It's up to you to decide what to do with it - you can easily look up all the needed info and remove unwanted firmware files."

Only, this process could be made more clear and more readily configurable (as I suggest, for example, a libre verbosity level, and noblob params). It is also not hypocrisy to fight battles in order of proximity - rather, it is strategy.

Re:“Blob-free OpenBSD kernel needed” by seba_dos1 on Saturday June 06, 2015 @09:19PM (#9673022)
As I said, under Linux it's just a matter of files in /lib/firmware, so you can easily implement this process however you would like to in userspace.