On Mon, 18 Aug 2003 19:44:04 +0100
Keith Whitwell <[EMAIL PROTECTED]> wrote:
> Jon Smirl wrote:
> > I figured out this this works:
> > insmod ./r128.ko drm_opts=debug:on
> >
> > But won't it be in the spirt of 2.6 module parameters
> > if
> > insmod ./r128.ko debug=on
> >
>
> I've never used t
On Mon, 2003-08-18 at 20:44, Keith Whitwell wrote:
> Jon Smirl wrote:
> > I figured out this this works:
> > insmod ./r128.ko drm_opts=debug:on
> >
> > But won't it be in the spirt of 2.6 module parameters
> > if
> > insmod ./r128.ko debug=on
How would that work with boot arguments? (Also keep
Jon Smirl wrote:
I figured out this this works:
insmod ./r128.ko drm_opts=debug:on
But won't it be in the spirt of 2.6 module parameters
if
insmod ./r128.ko debug=on
I've never used these options. How much use do they get generally? I'd be
just as happy to remove the code.
Keith
--
I figured out this this works:
insmod ./r128.ko drm_opts=debug:on
But won't it be in the spirt of 2.6 module parameters
if
insmod ./r128.ko debug=on
worked?
=
Jon Smirl
[EMAIL PROTECTED]
__
Do you Yahoo!?
Yahoo! SiteBuilder - Free, easy-to-use web site des
On 2.6 I just tried:
modprobe r128 debug=on
>From drm_init.h it looks like this should work.
in dmesg I get:
r128: Unknown parameter `debug'
grepping for the work 'Unknown' I see that there is no
'Unknown parameter' error message.
Do the DRM modules need to be updated for 2.6 module
parameter
