The expression for ati-drivers is at `pkgs/os-specific/linux/ati-drivers/default.nix`. The first thing you should notice is that it uses a custom builder. I think you can safely skip all the details of the builder, what’s interesting is the `patchPhase` attribute of the the derivation. It is just a string representing a shell script that the builder `eval`s (line 14 of the builder).
So what you have to do is download the patches you like and apply them in `patchPhase`. You should also ensure that the new patches interact well with the one that is already applied (and whether this one still needed at all). On Sun, May 10, 2015 at 12:20 AM Matthias Beyer <[email protected]> wrote: > I guess I'm willing to try patching the driver. > > Can you guide me how to? I'd apply this[0] patch, which > is from the thread you linked. > > [0]: https://bugs.gentoo.org/attachment.cgi?id=402514&action=diff > > On 09-05-2015 08:38:00, Kirill Elagin wrote: > > The cr4 functions should be easy to fix, they just were renames, as far > as > > I can tell. > > > > Other errors are a little more mysterious. > > This should be helpful: https://bugs.gentoo.org/show_bug.cgi?id=548118. > > > > On Sat, May 9, 2015 at 9:41 AM Vladimír Čunát <[email protected]> wrote: > > > > > Hi, > > > it's common that proprietary drivers fail to compile after kernel > > > update. Typically it's easiest to search for a patch in other distros. > > > > > > Vladimir > > > > > > > > > _______________________________________________ > > > nix-dev mailing list > > > [email protected] > > > http://lists.science.uu.nl/mailman/listinfo/nix-dev > > > > > -- > Mit freundlichen Grüßen, > Kind regards, > Matthias Beyer > > Proudly sent with mutt. > Happily signed with gnupg. >
_______________________________________________ nix-dev mailing list [email protected] http://lists.science.uu.nl/mailman/listinfo/nix-dev
