One question that I've had for a long time involves binary drivers. Yes, I know everyone's supposed to hate binary blobs and if a driver doesn't exist, write it yourself, etc., etc., etc.
Linux wireless support has become much better in the past year (and a half?). But one of the good things to know was there was always ndiswrapper. What is ndiswrapper? It is a way to use native windows network drivers inside of linux. How does this happen? It's basically because the NDIS layer is one of the (few) things that is well-documented by Microsoft. So it was possible to write such a `driver wrapper'.
My question is about Mac on intel (and Mac in general) with the BSD-based OSX. Second to Windows, hardware manufacturers try to include Mac support for their products (linux is lower on the list. especially for inkjet printers). My question is:
Since much of the Mac operating system is open (at least to look at), how hard would it be to write a `wrapper' for Mac drivers to work on linux? I assume that since Mac has moved to intel, hardware manufacturers will start to create drivers for printers/etc. to use on intel-macs; so there would be a greater incentive for linux developers (the vast majority of whome use x86) to write a wrapper that lets one use mactel drivers on x86 linux.
Am I way off base here?