Re: [Linux-fbdev-users] rivafb + NV17

[Antonino A. D. <ad...@ho...>]

On Friday 12 November 2004 08:02, David Liontooth wrote:
> Hi Tony,
>
> The directfb works great -- I can now play movies in the framebuffer
> and the quality is as good as in x-windows (even though my fb.mode
> has a depth of 8). CPU usage is below 50% (and that is running the
> CPU at half speed using cpufreq), while in X it's around 75%. Very
> cool actually.
>
> A quirk in the framebuffer: if I touch the mouse while playing a movie
> with mplayer, everything freezes and I have to hardboot. I can't even
> ssh into the machine. I wanted the mousewheel as a way of fast
> forwarding in the movie.

It's possible that this might be fixed in the latest mm kernel, if the bug
is indeed in the kernel framebuffer.  Otherwise, the bug can be part of
DirectFB itself.

>
> I'm also wondering if it's possible to tell the rivafb module to use
> the right mode when loading -- at the moment it loads into 640x480
> and then I use fbset to change it to 1280x854. Here's the first
> entry in my /etc/fb.modes:
>

Currently, no.  You have to add your modeline into the kernel's
modeline table which is located in drivers/video/modedb.c (unless
your mode is already present).

>     #
>     #   Sample video modes
>     #
>
>     #  Generated using modeline2fb, 1280x854, 85.266 MHz dotclock
>
>     mode "fullscreen"
>       geometry   1280 854   1280 26201   8
>       timings    11728   240 16   31 0   256 7
>       hsync low
>       vsync low
>     endmode
>
> The module doesn't seem to accept mode parameters, however.

It does, except for the startup mode, so if rivafb is compiled as a module
(and this is true for most drivers), it will only use the default mode.

>
> >>The main remaining annoyance is that you can't remove the rivafb module,
> >
> >You can actually, as long as you don't enable the framebuffer console.
> > This sequence should work:
> >
> >modprobe rivafb
> >mplayer -vo directfb
> >rmmod rivafb
> >
> >Of course you will only have a vga console.
>
> Not sure I understand -- you don't mean I can insert rivafb while
> the nvidia module is still inserted? In that case I get this:

No, I was answering the part of your question about being able to
remove rivafb, and the answer is yes you can, as long as the framebuffer 
console is disabled.

>
>
>        ---------------------- DirectFB v0.9.20 ---------------------
>              (c) 2000-2002  convergence integrated media GmbH
>              (c) 2002-2003  convergence GmbH
>         -----------------------------------------------------------
>
> (*) Single Application Core. (with MMX support) (2004-01-20 10:18)
> (*) DirectFB/misc/memcpy: using MMXEXT optimized memcpy()
> (!) DirectFB/core/fbdev: Error opening `/dev/fb0'!
>     --> No such device
> (!) DirectFB/Core: Could not initialize 'system' core!
>     --> Not supported!
> (!) DirectFB/Core: Error during initialization (Not supported!)
> vo_directfb2.c <315>:
>         (#) DirectFBError [DirectFBCreate (&dfb)]: Not supported!
>
> Not surprising, right? The framebuffer device /dev/fb0 is not created.
> So what does it mean to use directfb without enabling the framebuffer
> console?

As I've mentioned above, you can load the framebuffer driver, but not load
the framebuffer console, and it should work. Set
CONFIG_FRAMEBUFFER_CONSOLE=n.

Tony