[arch-dev-public] [new package] nouveau-drm / xf86-video-nouveau
I'd like to bring in these packages in a slightly modified version from AUR to testing and later to extra repos. Both packages have a nice amount of votes in AUR. http://nouveau.freedesktop.org/wiki/ nouveau-drm provides a mesa/drm git version with new drm-nouveau code not yet implemented in the mainline kernel drm.ko. xf86-video-nouveau is the opensource Xorg driver under heavy developement. 2D support is stable using EXA and much faster than the "nv" driver developed by Nvidia company for Xorg. I'm running the xf86-video-nouveau driver in a DualHead configuration with RandR1.2 for some time now. It's stable and a good opensource alternative to the Nvidia closed one and to the slow and poor of features "nv" driver. 3D support is under development with Gallium3d and will show major changes as well as radeon/ati and intel driver do with K(ernel) M(ode) S(ettings). But that's something different and will happen past Xorg-Server 1.6 and Mesa7.3. Any objections moving in that open source driver for Nvidia cards? -Andy
Andreas Radke schrieb:
I'd like to bring in these packages in a slightly modified version from AUR to testing and later to extra repos. Both packages have a nice amount of votes in AUR.
http://nouveau.freedesktop.org/wiki/
nouveau-drm provides a mesa/drm git version with new drm-nouveau code not yet implemented in the mainline kernel drm.ko.
You must do this differenlty: This package installs drm.ko in extra/. This way it doesn't conflict with drm.ko from kernel26, but it is still possible that the stock one will be loaded first. This module MUST be put in the updates/ directory so it will always take precedence. This might break other drm drivers, so I suggest providing a "drm-git" package instead, which would install updates for all drm modules from git to updates/ (instead of just nouveau). This package could then also be used by non-nouveau users.
On Thu, Jan 22, 2009 at 11:11 AM, Thomas Bächler <thomas@archlinux.org> wrote:
Andreas Radke schrieb:
I'd like to bring in these packages in a slightly modified version from AUR to testing and later to extra repos. Both packages have a nice amount of votes in AUR.
http://nouveau.freedesktop.org/wiki/
nouveau-drm provides a mesa/drm git version with new drm-nouveau code not yet implemented in the mainline kernel drm.ko.
You must do this differenlty: This package installs drm.ko in extra/. This way it doesn't conflict with drm.ko from kernel26, but it is still possible that the stock one will be loaded first.
This module MUST be put in the updates/ directory so it will always take precedence. This might break other drm drivers, so I suggest providing a "drm-git" package instead, which would install updates for all drm modules from git to updates/ (instead of just nouveau). This package could then also be used by non-nouveau users.
That seems way too complicated. What's wrong with just conflicting like normal? Can you think of any standard case where these conflicts are going to hurt us? Which packages contain drm.ko? Besides what Thomas mentions, putting this in extra is fine by me, Andreas.
Aaron Griffin schrieb:
That seems way too complicated. What's wrong with just conflicting like normal? Can you think of any standard case where these conflicts are going to hurt us?
Which packages contain drm.ko?
kernel26
On Thu, Jan 22, 2009 at 1:17 PM, Thomas Bächler <thomas@archlinux.org> wrote:
Aaron Griffin schrieb:
That seems way too complicated. What's wrong with just conflicting like normal? Can you think of any standard case where these conflicts are going to hurt us?
Which packages contain drm.ko?
kernel26
So then simply putting this one in the updates directory should be enough, right?
Am Thu, 22 Jan 2009 13:28:18 -0600 schrieb Aaron Griffin <aaronmgriffin@gmail.com>:
On Thu, Jan 22, 2009 at 1:17 PM, Thomas Bächler <thomas@archlinux.org> wrote:
Aaron Griffin schrieb:
That seems way too complicated. What's wrong with just conflicting like normal? Can you think of any standard case where these conflicts are going to hurt us?
Which packages contain drm.ko?
kernel26
So then simply putting this one in the updates directory should be enough, right?
I haven't seen any problem so far with the module in extra. It has been always loaded first. I can't imagine a situation where the module in extra could cause an issue. You usually use drm only with one graphic card driver. But I'll read around a bit how kernel modules get loaded and how other distributions do this. Building a drm-git providing _all_ possible drm modules is much more than we want here. Putting it into extra or update path should be enough here. I'll try to find out what's the recommended/best way we should go. -Andy
Andreas Radke schrieb:
I haven't seen any problem so far with the module in extra. It has been always loaded first. I can't imagine a situation where the module in extra could cause an issue. You usually use drm only with one graphic card driver.
If you install this package it might happen that a drm driver from kernel26 is loaded together with drm.ko from your package, which might be incompatible. To ensure it is loaded first, you must put it in updates/, putting it in extra works purely out of coincidence.
Putting it into extra or update path should be enough here. I'll try to find out what's the recommended/best way we should go.
Put at least drm.ko in extra.
Am Thu, 22 Jan 2009 21:11:22 +0100 schrieb Thomas Bächler <thomas@archlinux.org>:
Andreas Radke schrieb:
I haven't seen any problem so far with the module in extra. It has been always loaded first. I can't imagine a situation where the module in extra could cause an issue. You usually use drm only with one graphic card driver.
If you install this package it might happen that a drm driver from kernel26 is loaded together with drm.ko from your package, which might be incompatible.
This shouldn't happen. People will only install it when they want to use the nouveau module in their xorg.conf
To ensure it is loaded first, you must put it in updates/, putting it in extra works purely out of coincidence.
Putting it into extra or update path should be enough here. I'll try to find out what's the recommended/best way we should go.
Put at least drm.ko in extra.
[andyrtr@workstation64 ~]$ pacman -Ql nouveau-drm nouveau-drm /lib/ nouveau-drm /lib/modules/ nouveau-drm /lib/modules/2.6.28-ARCH/ nouveau-drm /lib/modules/2.6.28-ARCH/extra/ nouveau-drm /lib/modules/2.6.28-ARCH/extra/drm.ko nouveau-drm /lib/modules/2.6.28-ARCH/kernel/ nouveau-drm /lib/modules/2.6.28-ARCH/kernel/drivers/ nouveau-drm /lib/modules/2.6.28-ARCH/kernel/drivers/video/ nouveau-drm /lib/modules/2.6.28-ARCH/kernel/drivers/video/nouveau.ko nouveau-drm /usr/ nouveau-drm /usr/include/ nouveau-drm /usr/include/nouveau_drm.h so you're fine with this? I couldn't find something about the module load order here ( http://tldp.org/HOWTO/Module-HOWTO/ ) or somewhere else so I expect the module to get loaded in alphabetical order: /lib/modules/2.6.28-ARCH/extra/drm.ko /lib/modules/2.6.28-ARCH/kernel/drivers/gpu/drm/drm.ko Not sure if the kernel, Xorg or udev does the loading here. -Andy
Andreas Radke schrieb:
I couldn't find something about the module load order here ( http://tldp.org/HOWTO/Module-HOWTO/ ) or somewhere else so I expect the module to get loaded in alphabetical order:
/lib/modules/2.6.28-ARCH/extra/drm.ko /lib/modules/2.6.28-ARCH/kernel/drivers/gpu/drm/drm.ko
It may be alphabetical, but this is coincidental and uncodumented. The precedence of /updates/ however is documented and intentional behaviour.
participants (3)
-
Aaron Griffin
-
Andreas Radke
-
Thomas Bächler