4 ms·

The good people contribute to Darwin and the other core Apple projects and their code ends up in mainline os x. Could you link to some commits on Macosforge th

by Zev 17y ago

The good people contribute to Darwin and the other core Apple projects and their code ends up in mainline os x. Could you link to some commits on Macosforge that were based on patches by people from osx86? This is the first I'm hearing of this. Hackintosh users are some of the most prolific driver writers and help get tons of USB drivers written that are useful to macs and osx86 machines alike. Last time I looked at osx86 (admittedly, years ago, long before Leopard was released), there weren't any custom kexts written by the community, just plists from Apple that were edited. Can you link to some custom kext's that have risen from osx86?

drewcrawford 17y ago
> Could you link to some commits on Macosforge that were based on patches by people from osx86? There are cases that I'm aware of, but I think several Apple employees would fear retaliation if I outed them here :-) It's too bad that the XNU development process is totally closed (even if the code is OSS), as that's where you see so much of the osx86 activity. In particular, go look at voodooxnu, xnu-dev, etc. These are all drop-in replacement kernels for mach_kernel, run by hackintoshers, that accept patches from contributors. I believe voodoo will be the default kernel for the next PureDarwin (the new OpenDarwin) release. > Can you link to some custom kext's that have risen from osx86? http://code.google.com/p/voodoohda/ http://code.google.com/p/voodoohda/ http://code.google.com/p/voodoo-power/ http://code.google.com/p/voodoo-power/
- Zev 17y ago
  These are all drop-in replacement kernels for mach_kernel, run by hackintoshers, that accept patches from contributors It sounds like none of these modifications are sent back to Apple. Its great that they can fork projects - that much, anyone can do. The original claim was that osx86 hackers had contributed code to Apple, that was now in Darwin and is used in shipping OS's. Thats far more interesting then any modification that's made on a fork. And of the two kext's you linked to, they both look to be dead in development, with more then a few major bugs each. Thats more of a hinderance than a help for your argument, really.
  - drewcrawford 17y ago
    > And of the two kext's you linked to, they both look to be dead in development, with more then a few major bugs each I use both of those drivers daily on three different machines. I have yet to experience a single bug on my hardware. For bleeding-edge chipsets, YMMV. As for speed of development, I generally install drivers (as opposed to userland software) once and forget about it unless there's a problem. Given that I have no problems, I'm quite satisfied.

by Zev 17y ago

drewcrawford 17y ago

> Could you link to some commits on Macosforge that were based on patches by people from osx86? There are cases that I'm aware of, but I think several Apple employees would fear retaliation if I outed them here :-) It's too bad that the XNU development process is totally closed (even if the code is OSS), as that's where you see so much of the osx86 activity. In particular, go look at voodooxnu, xnu-dev, etc. These are all drop-in replacement kernels for mach_kernel, run by hackintoshers, that accept patches from contributors. I believe voodoo will be the default kernel for the next PureDarwin (the new OpenDarwin) release. > Can you link to some custom kext's that have risen from osx86? http://code.google.com/p/voodoohda/ http://code.google.com/p/voodoohda/ http://code.google.com/p/voodoo-power/ http://code.google.com/p/voodoo-power/

Zev 17y ago
These are all drop-in replacement kernels for mach_kernel, run by hackintoshers, that accept patches from contributors It sounds like none of these modifications are sent back to Apple. Its great that they can fork projects - that much, anyone can do. The original claim was that osx86 hackers had contributed code to Apple, that was now in Darwin and is used in shipping OS's. Thats far more interesting then any modification that's made on a fork. And of the two kext's you linked to, they both look to be dead in development, with more then a few major bugs each. Thats more of a hinderance than a help for your argument, really.
- drewcrawford 17y ago
  > And of the two kext's you linked to, they both look to be dead in development, with more then a few major bugs each I use both of those drivers daily on three different machines. I have yet to experience a single bug on my hardware. For bleeding-edge chipsets, YMMV. As for speed of development, I generally install drivers (as opposed to userland software) once and forget about it unless there's a problem. Given that I have no problems, I'm quite satisfied.