Text 5228, 102 rader
Skriven 2006-02-08 20:22:04 av James Bradley (1:134/77.0)
     Kommentar till en text av Maurice Kinal
Ärende: matroxfb
================
On or about 02-07-06 19:39, Maurice Kinal did engage James Bradley

 MK> took the liberty of adding the mga_vid module to whatever
 MK> kernel's proper /lib/modules/<version>/extra.  For instance;

 MK> root:~# find /lib/modules/ -name "mga_vid.ko"
 MK> /lib/modules/2.6.15.2/extra/mga_vid.ko
 MK> /lib/modules/2.6.15.1/extra/mga_vid.ko
 MK> /lib/modules/2.6.15.3/extra/mga_vid.ko

And if I kill a chicken at dusk, I will be well fed by morn. <-;

Trying to keep up: The three versions are just to accommodate three different
kernel versions, and the files "mga_vid.ko" may be the same? Was it simply
copied there, or was there an anointment/compile/make/ritual sacrifice to get
it there? I'm reading man mod*. Is that the right direction? 

 MK> BTW none of the above is any better then the other kv's wrt 'mplayer
 MK> -vo mga whatever.format'.  What has improved - and is the same as
 MK> far I can tell with the above kv's - is the addition of
 MK> '/sbin/modprobe mga_vid mga_ram_size=16' in the
 MK> '/etc/rc.d/rc.modules' file which happily fixed my console
 MK> graphical abilities.  Additionally - and here is the REAL
 MK> bonus - the 22 hour movie jobber looks absolutely excellent
 MK> in both console and gui worlds now that the 'mplayer -vo xv
 MK> whatever.format' works in X.  I haven't checked 'mplayer -
 MK> vo xmga whatever.format' since altering the rc.modules file
 MK> but it used to work and I imagine that it still could.
 MK> However I think 'xv' is the more prudent way to go seeing
 MK> that it is the default in many gui movie playing apps, or
 MK> at least in X it is.

<nodding w/glazed look> The same "Xv" is the device that tvtime was taking as a
command line argument? My post just earlier was about an argument to the
kernel, "video=matroxfb,mem:8M" with the attempt to limit fb0 to an amount,  as
"mga_ram_size=" would? You may have answered this by now by addressing that
message.

I have to procure another copy of MultiMail too, so I'll try to grab the
mga_vid at the same time. <scribble,scribble> Oh ya... And "matroxfbset".
Anything else come to mind?

 MK>   http://attila.kinali.ch/mga/mga_vid-2.6.12-2005-06-18.tar.gz

 JB> Physically, I have four memory chips by the looks of things, but
 JB> those don't le\ad on how big they are. Would you, or anyone reading
 JB> happen to know?

 MK> Looks to be 8M each by my guesstimation.

Yet probed, it came in at 16 total. How sure is your guesstimate? Even if I
"mem:32M" on the kernel "video=", dmesg still tells me there's only 16M.

 MK> I understand.  I'll be happy to send you whatever you need in the way
 MK> of archives to help you out.  The above source is under 12k so
 MK> it shouldn't be a really big issue.  What do you have in
 MK> terms of media capabilities (cd-rom, usb, whatever) and

Floppy! <chuckle> Let me see what I can do from here. There's a few public
connections that the library suggested I could use for files. It's a bit
uncomfortable, but usually I can stand at an unfamiliar machine long enough to
grab stuff. Optionally, I suppose we could try f-attach. Did you not get my
netmail a few weeks ago?


 JB> Region 0: Memory at e4000000 (32-bit, prefetchable)
 MK> Region 0: Memory at d2000000 (32-bit, prefetchable) [size=32M]
 JB> Region 1: Memory at e0000000 (32-bit, non-prefetchable) [size=16K]
 MK> Region 1: Memory at d4000000 (32-bit, non-prefetchable) [size=16K]
 JB> Region 2: Memory at e1000000 (32-bit, non-prefetchable) [size=8M]
 MK> Region 2: Memory at d5000000 (32-bit, non-prefetchable) [size=8M]

 MK> Looks to me that our respective memory addressing is different.
That would seem to be the case. Plus you allocate 32M to region 0. Regardless
how large I make the AGP memory window from the BIOS, it always starts at "e"
here. There's no need to cache the BIOS, or reserve sections, is there? 

 MK> PInS memtype = 0
This doesn't look familiar.

 MK> and then later;
 MK> Matrox MGA G200/G400/G450/G550 YUV Video interface v2.01
Much later... {-|[ Maybe later today.

 MK> mga_vid: using major: 83 (assigned or default!)

 MK> but that is only for /dev/fb0 as I still have to tweak /dev/fb1 to life
 MK> and am thinking major 83, minor 1 wrt /dev/mga1.  Not quite
 MK> there yet but am attempting to think ahead as far as
 MK> outputting to the tv-out on the breakout box.  Beats me if
 MK> I am sucking slough water with this idea or not but the
 MK> primary (vga) works absolutely great.
This doesn't address the 'tuner' portion, just the outputs, right?

Convention would have it at 29 character device, minor 0?


... James
___ MultiMail/Linux v0.46

--- Maximus 3.01
 * Origin: -=-= Calgary Organization CDN (403) 242-3221 (1:134/77)