Re: non-free firmware: driver in main or contrib?
>I think it's a question of what "dependence" means for contrib. If the
>driver absolutely _depends_ on using the non-free firmware, it should be
>in contrib. If the non-free firmware is optional, it should go into
Again, please explain which part of the policy defines this criteria.
>Of course, there's shades of gray, here. If all the driver does is emit
>a message CAN'T FIND NON-FREE FIRMWARE, ABORTING without the firmware,
>it's hard to say that it doesn't depend on the firmware. But if the
This applies to almost every driver in the Linux kernel. Are you ready
to move most of the kernel to non-free too?