Greg KH wrote:
>># Internal aliases, do not edit
>>alias char-major-195 nvidia
>>alias /dev/nvidiactl char-major-195
> Why do you need these? Aren't they automatically generated by depmod if
> you put the correct code in the kernel module source code (see the
> MODULE_ALIAS() stuff.)
Was not aware of that - will investigate.
>># Configurable module parameters
>># For more details, see /usr/share/doc/nvidia-kernel-1.0.6629/README.gz
>># silence_nvidia_output - Silence output: 0 (default, verbose) or 1
>># NVreg_EnableVia4x - Enable AGP4x on VIA chipsets (default disabled)
>># NVreg_EnableALiAGP - Enable AGP on ALi1541/1647 chipsets (default
>># NVreg_NvAGP - Select which AGPGART is used if unspecified by X - 0
>>(disable), 1 (use nvidia), 2 (use kernel), 3 (try 2 then 1, default)
>># NVreg_EnableAGPSBA - Enable AGP Side Band Addressing
>># NVreg_EnableAGPFW - Enable AGP Fast Writes (default disabled)
>># NVreg_SoftEDIDs - Enable dynamic generation of EDID info (default
>># NVreg_Mobile - Select Mobile registry key when SoftEDIDs is disabled - 0
>>(auto, default), 1 (Dell), 2 (Toshiba), 3 (other), 4 (Compal/Toshiba), 5
> modinfo also generates this automaticallly, with full strings, right?
> Hm, your patch has that.
Yep thats how they are generated. Except nvidia were too lazy to include param
descriptions, so I had to write some myself in that other patch.
> I guess I don't see the need for why we have these modules.d files.
> Anyone want to hit me with the cluestick for being not awake yet today?
To provide default options when loading or autoloading modules. For example, I
have the example in that file uncommented, and when I boot up, nvidia module
gets autoloaded with those options I have specified. To be more specific, all
of the /etc/modules.d/ files get aggregated into /etc/modules.conf when
"modules-update" is run (every bootup).
Bear in mind that I am simply automating/generalising a process that is
already in place. Currently,
/usr/portage/media-video/nvidia-kernel/files/1.0.6629/nvidia is copied into
/etc/modules.d but I am trying to generate a mechanism to automatically
generate this and generalise it so that other module ebuilds can use it too.
email@example.com mailing list