|
From: Nicholas W. <nw...@ne...> - 2002-10-15 23:20:07
|
Hi, I was curious to know if the maintainer for the radeonfb driver was planning to update it wrt James' recent API changes. Considiering it is the latest line available, I'd hope that its brokeness will not be permanent ;-). Cheers, Nicholas |
|
From: Ani J. <aj...@un...> - 2002-10-15 23:42:58
|
radeonfb for 2.5 will be updated in the next release (or 2). ani On Tue, 15 Oct 2002, Nicholas Wourms wrote: > Hi, > > I was curious to know if the maintainer for the radeonfb > driver was planning to update it wrt James' recent API > changes. Considiering it is the latest line available, I'd > hope that its brokeness will not be permanent ;-). > > Cheers, > Nicholas > > > > ------------------------------------------------------- > This sf.net email is sponsored by: viaVerio will pay you up to > $1,000 for every account that you consolidate with us. > http://ad.doubleclick.net/clk;4749864;7604308;v? > http://www.viaverio.com/consolidator/osdn.cfm > _______________________________________________ > Linux-fbdev-devel mailing list > Lin...@li... > https://lists.sourceforge.net/lists/listinfo/linux-fbdev-devel > |
|
From: Nicholas W. <nw...@ne...> - 2002-10-29 14:14:20
|
Ani Joshi wrote: > > radeonfb for 2.5 will be updated in the next release (or 2). > > Ping? =) Cheers, Nicholas |
|
From: Benjamin H. <be...@ke...> - 2002-10-16 20:30:37
|
>I was curious to know if the maintainer for the radeonfb >driver was planning to update it wrt James' recent API >changes. Considiering it is the latest line available, I'd >hope that its brokeness will not be permanent ;-). I've ported radeonfb 0.1.6 to 2.5.42 (available in the linuxppc-2.5 bk tree) and will port it to James latest changes. Ani (the maintainer) will probably then just use that port. Ben. |
|
From: Nicholas W. <nw...@ne...> - 2002-10-16 20:58:52
|
Benjamin Herrenschmidt wrote: >>I was curious to know if the maintainer for the radeonfb >>driver was planning to update it wrt James' recent API >>changes. Considiering it is the latest line available, I'd >>hope that its brokeness will not be permanent ;-). > > > I've ported radeonfb 0.1.6 to 2.5.42 (available in the linuxppc-2.5 > bk tree) and will port it to James latest changes. Ani (the > maintainer) will probably then just use that port. > > Ben. > Excellent! Two other questions (not necessarily related): A) Is it (or will it ever be) possible to run dual head using two different cards (like radeon & riva-tnt2)? I know there is still much work to be done, but I was curious if this was even remotely possible. Sorta hate to let a good video card go to waste if you know what I mean :-). B) Does anyone have a painless, yet precise way of generating modelines for fb.modes if you are using XFree-4.2? I only ask because the XFree modelines are all determined by i2c DDC probing, thus there are none in the XF86Config file. The modeline output captured in the log XFree.0.log is not the same output which modeline2fb expects. Anyhow, I've tried using some of the information in the log, but I always get funky results. I may be looking in the wrong place, but the documentation for both the fbdev kernel drivers and the X drivers are sorely out of date, so please excuse me if this is a question that has previously been answered. I just need some formulae to convert values between what shows up in XFree.0.log when i2c DDC probes for the modelines and what needs to go in fb.modes. Thanks in advance! Cheers, Nicholas |
|
From: Michel <mi...@da...> - 2002-10-16 22:45:47
|
On Mit, 2002-10-16 at 22:55, Nicholas Wourms wrote: >=20 > A) Is it (or will it ever be) possible to run dual head=20 > using two different cards (like radeon & riva-tnt2)? I know=20 > there is still much work to be done, but I was curious if=20 > this was even remotely possible. I think it should theoretically work, but as always the only way to tell is to try it. :) > B) Does anyone have a painless, yet precise way of=20 > generating modelines for fb.modes if you are using=20 > XFree-4.2? I only ask because the XFree modelines are all=20 > determined by i2c DDC probing, thus there are none in the=20 > XF86Config file. If the X driver supports Option "UseFBDev", you should be able to use fbset with that. --=20 Earthling Michel D=E4nzer (MrCooper)/ Debian GNU/Linux (powerpc) developer XFree86 and DRI project member / CS student, Free Software enthusiast |
|
From: Antonino D. <ad...@po...> - 2002-10-18 21:47:12
|
On Thu, 2002-10-17 at 04:55, Nicholas Wourms wrote:
> B) Does anyone have a painless, yet precise way of
> generating modelines for fb.modes if you are using
> XFree-4.2? I only ask because the XFree modelines are all
> determined by i2c DDC probing, thus there are none in the
> XF86Config file. The modeline output captured in the log
> XFree.0.log is not the same output which modeline2fb
> expects. Anyhow, I've tried using some of the information
> in the log, but I always get funky results. I may be
> looking in the wrong place, but the documentation for both
> the fbdev kernel drivers and the X drivers are sorely out of
> date, so please excuse me if this is a question that has
> previously been answered. I just need some formulae to
> convert values between what shows up in XFree.0.log when i2c
> DDC probes for the modelines and what needs to go in
> fb.modes. Thanks in advance!
>
Not necessarily painless...
Given timings in X modeline format (you can generate with xvidtune):
"XRESxYRES" MHZ XACTIVE FP_X HSYNC BP_X YACTIVE FP_Y VSYNC
BP_Y +hsync +vsync
Then timings in fb.mode:
mode "XRESxYRES MHZ"
# D: "MHZ, H: HorizSync kHz, V: VertRefresh Hz
geometry xres yres vxres vyres bpp
timings pixclock left right upper lower hsync vsync
hsync high
vsync high
endmode
where:
pixclock = 1000000/MHZ
left = BP_X - HSYNC
right = FP_X - XACTIVE
upper = BP_Y - VSYNC
lower = FP_Y - YACTIVE
hsync = HSYNC - FP_X
vsync = VSYNC - FP_Y
What you need to concentrate on is the timings field of fb.modes. This
also assumes that the driver actually reads the timings field. Some
drivers disregard those values (considers only xres and yres) then
configure their own timings.
Tony
|
|
From: Nicholas W. <nw...@ne...> - 2002-10-18 22:15:40
|
Antonino Daplas wrote: > Not necessarily painless... > > Given timings in X modeline format (you can generate with xvidtune): > > "XRESxYRES" MHZ XACTIVE FP_X HSYNC BP_X YACTIVE FP_Y VSYNC > BP_Y +hsync +vsync > > Then timings in fb.mode: > > mode "XRESxYRES MHZ" > # D: "MHZ, H: HorizSync kHz, V: VertRefresh Hz > geometry xres yres vxres vyres bpp > timings pixclock left right upper lower hsync vsync > hsync high > vsync high > endmode > > where: > > pixclock = 1000000/MHZ > left = BP_X - HSYNC > right = FP_X - XACTIVE > upper = BP_Y - VSYNC > lower = FP_Y - YACTIVE > hsync = HSYNC - FP_X > vsync = VSYNC - FP_Y > > What you need to concentrate on is the timings field of fb.modes. This > also assumes that the driver actually reads the timings field. Some > drivers disregard those values (considers only xres and yres) then > configure their own timings. > Tony, Thank you, this is *exactly* what I was looking for! I never knew what xvidtune was really for, but this sure answers that one. Cheers, Nicholas |
|
From: James S. <jsi...@in...> - 2002-11-21 18:39:57
|
> Excellent! Two other questions (not necessarily related): > > A) Is it (or will it ever be) possible to run dual head > using two different cards (like radeon & riva-tnt2)? I know > there is still much work to be done, but I was curious if > this was even remotely possible. Sorta hate to let a good > video card go to waste if you know what I mean :-). Well that depends on if it is possible to initialize the card fully without using the graphics BIOS. To my current knowledge the Matrox card can do this and it is possible for the 3Dfx family of cards. This I have seen in the docs. As for NVIDIA cards they don't release that info and ATI is also funny about release such info as well :-( > XFree-4.2? I only ask because the XFree modelines are all > determined by i2c DDC probing, thus there are none in the Ah DDC support. I really wanted to add that into the fbdev layer but unfortunely I don't have the time to do that :-( Only if I did fbdev for a living. |
|
From: Nicholas W. <nw...@ne...> - 2002-10-18 17:31:08
|
Michel Dänzer wrote: > On Mit, 2002-10-16 at 22:55, Nicholas Wourms wrote: >> >> A) Is it (or will it ever be) possible to run dual head >> using two different cards (like radeon & riva-tnt2)? I know >> there is still much work to be done, but I was curious if >> this was even remotely possible. > > I think it should theoretically work, but as always the only way to tell > is to try it. :) Well there isn't much on multiheading in the documentation, so I was hoping for some hints or key insights into how to set this up. Is there any special magic that the matrox people use to thell the kernel to initialize both framebuffers? > >> B) Does anyone have a painless, yet precise way of >> generating modelines for fb.modes if you are using >> XFree-4.2? I only ask because the XFree modelines are all >> determined by i2c DDC probing, thus there are none in the >> XF86Config file. > > If the X driver supports Option "UseFBDev", you should be able to use > fbset with that. > Huh? The problem is that fbset will not work because I need to populate fb.modes with proper mode lines. So at the moment fbset won't work at all. What I was asking, since the documention was written when XFree 3.x was still in use, was how do I get (calculate) the modelines for fb.modes based on the information the i2c DDC probing XFree-4.2.1 outputs in XFree.0.log? Or is there a better way? What might be cool is if the fb drivers used the lm-sensors(i2c) capabilities to automagically probe the information and set up the most optimal settings. Maybe I'm talking too much about something I'm not all that familiar with... Still, it would be nice =). Cheers, Nicholas |
|
From: Michel <mi...@da...> - 2002-10-18 19:28:48
|
On Fre, 2002-10-18 at 19:21, Nicholas Wourms wrote: > Michel D=E4nzer wrote: >=20 > > On Mit, 2002-10-16 at 22:55, Nicholas Wourms wrote: > >>=20 > >> A) Is it (or will it ever be) possible to run dual head > >> using two different cards (like radeon & riva-tnt2)? I know > >> there is still much work to be done, but I was curious if > >> this was even remotely possible. > >=20 > > I think it should theoretically work, but as always the only way to tel= l > > is to try it. :) >=20 > Well there isn't much on multiheading in the documentation, so I was hopi= ng=20 > for some hints or key insights into how to set this up. Something like video=3Dradeonfb video=3Driva ? > >> B) Does anyone have a painless, yet precise way of > >> generating modelines for fb.modes if you are using > >> XFree-4.2? I only ask because the XFree modelines are all > >> determined by i2c DDC probing, thus there are none in the > >> XF86Config file. > >=20 > > If the X driver supports Option "UseFBDev", you should be able to use > > fbset with that. > >=20 >=20 > Huh? The problem is that fbset will not work because I need to populate=20 > fb.modes with proper mode lines. So at the moment fbset won't work at al= l. =20 I was thinking of running X with Option "UseFBDev" and getting information about the modes with fbset. --=20 Earthling Michel D=E4nzer (MrCooper)/ Debian GNU/Linux (powerpc) developer XFree86 and DRI project member / CS student, Free Software enthusiast |
|
From: Nicholas W. <nw...@ne...> - 2002-10-18 20:53:22
|
Michel Dänzer wrote: >> >> B) Does anyone have a painless, yet precise way of >> >> generating modelines for fb.modes if you are using >> >> XFree-4.2? I only ask because the XFree modelines are all >> >> determined by i2c DDC probing, thus there are none in the >> >> XF86Config file. >> > >> > If the X driver supports Option "UseFBDev", you should be able to use >> > fbset with that. >> > >> >> Huh? The problem is that fbset will not work because I need to populate >> fb.modes with proper mode lines. So at the moment fbset won't work at >> all. > > I was thinking of running X with Option "UseFBDev" and getting > information about the modes with fbset. > Hmm... I guess that setting doesn't do what I thought it did. I'll give it a shot and see if it works. Thanks! Cheers, Nicholas |
|
From: James H. C. Jr. <cl...@jh...> - 2002-11-04 08:47:17
|
>>>>> "Nicholas" == Nicholas Wourms <nw...@ne...> writes: Nicholas> how do I get (calculate) the modelines for fb.modes Nicholas> based on the information the i2c DDC probing XFree-4.2.1 Nicholas> outputs in XFree.0.log? It is just a matter of reformatting. Eg, from this box: (II) Reloading /usr/X11R6/lib/modules/libddc.a [etc] (II) RADEON(0): Supported Future Video Modes: (II) RADEON(0): #0: hsize: 1600 vsize 1200 refresh: 60 vid: 16553 (II) RADEON(0): Supported additional Video Mode: (II) RADEON(0): clock: 162.0 MHz Image Size: 305 x 228 mm (II) RADEON(0): h_active: 1600 h_sync: 1664 h_sync_end 1856 h_blank_end 2160 h_border: 0 (II) RADEON(0): v_active: 1200 v_sync: 1201 v_sync_end 1204 v_blanking: 1250 v_border: 0 Those lines give the data for a modeline. That translates to: Modeline "1600x1200x60" 162.0 1600 1664 1856 2160 1200 1201 1204 1250 -JimC |