Menu
▾
▴
linux-fbdev-devel
|
From: James S. <jsi...@tr...> - 2002-04-10 19:45:27
|
I just got my hands on a Permedia 2 card. This card has on it a S3 virge chip for vga modes and a 3DLabs GLINT delta and 500TX chips on it. Did anyone manage to get it to work? . --- |o_o | |:_/ | Give Micro$oft the Bird!!!! // \ \ Use Linux!!!! (| | ) /'_ _/`\ ___)=(___/ |
|
From: Romain D. <do...@ir...> - 2002-04-11 06:20:41
|
James Simmons wrote: > > I just got my hands on a Permedia 2 card. This card has on it a S3 virge > chip for vga modes and a 3DLabs GLINT delta and 500TX chips on it. Did > anyone manage to get it to work? I don't think this is a permedia2 card, as the permedia2 was a single chip with 2D and some 2D integrated. This is likely an older card (such as a Gloria L). The real permedia2 was supported at some point in the linux kernel (I used th code as th basis for pm3fb), but the maintainer orphaned it a while ago. The virge could work by itself, I suppose (it's likely a different PCI function). -- DOLBEAU Romain | I have lost the will to live ENS Cachan / Ker Lann | Simply nothing more to give Thesard IRISA / CAPS | -- Metallica, dol...@cl... | 'Fade to Black' |
|
From: James S. <jsi...@tr...> - 2002-04-11 19:26:02
|
> I don't think this is a permedia2 card, as the permedia2 > was a single chip with 2D and some 2D integrated. This > is likely an older card (such as a Gloria L). Ug. That sucks. |
|
From: Jim H. <jim...@ac...> - 2002-04-12 12:09:24
|
On 11-Apr-2002 Romain Dolbeau wrote: > The real permedia2 was supported at some point in the > linux kernel (I used th code as th basis for pm3fb), but > the maintainer orphaned it a while ago. Funny this should come up now. Yesterday I did some work on updating the pm2fb driver in 2.4 to include the changes in Illo's last released driver. I have a x86 machine with a PCI Permedia card (Creative GraphicsBlaster?) which I've been using happily for some time with Illo's driver on 2.2. The driver in stock 2.2 doesn't work well for me, but Illo's last release does. The 2.4 update isn't done yet, as the change to 2.4 has uncovered a bug which manifests as default modes with low hsync/vsync actually getting high hsync/vsync (guess who's using an old Sun fixed-frequency monitor that requires low hsync/vsync...), but I'm pretty sure I now know what's wrong and the fix is easy. I'm hoping it'll also fix the problem I've had using it with the X glint server too. When that's all out of the way I'm happy to take a crack at moving it to the new API (once the whitepaper is ready :-)), though I won't be quick - I don't have much spare time, and I'm no video driver expert. Any pointers to docs on the chip would be welcome. -- Jim Hague - jim...@in... (Work), ji...@be... (Play) Never trust a computer you can't lift. |
|
From: Sven <lu...@dp...> - 2002-04-12 23:02:28
|
On Fri, Apr 12, 2002 at 01:09:11PM +0100, Jim Hague wrote: > On 11-Apr-2002 Romain Dolbeau wrote: > > The real permedia2 was supported at some point in the > > linux kernel (I used th code as th basis for pm3fb), but > > the maintainer orphaned it a while ago. > > Funny this should come up now. Yesterday I did some work on updating the pm2fb > driver in 2.4 to include the changes in Illo's last released driver. Hello, You might try to look at the possibility of merging it back into pm3fb, or at least merge the common parts of both drivers, altough i am not sure what romain thinks about it, since there were many changes to the pm3fb driver since romain worked on it, and it may not be easy or worthwhile to merge them together. Friendly, Sven Luther |
|
From: <dol...@cl...> - 2002-04-13 06:32:45
|
> You might try to look at the possibility of merging it back into pm3fb, or > at least merge the common parts of both drivers, altough i am not sure > what romain thinks about it, since there were many changes to the pm3fb > driver since romain worked on it, and it may not be easy or worthwhile to > merge them together. Huh ? pm3fb in 2.4.19pre6 seems to be exactly the same as my CVS... Or are you talking about the old attempt at a port that I put in linux-console a while ago ? It someone managed to get it to work Id'd like to hear of it, and eventually to merge the change that were done in regular pm3fb since the first port. I don't think merging is worth the effort. There's not that much code in common (beside some registers definitions), pm2fb support more buses than pm3fb (PCI/AGP -only), and very few people will need both pm2fb and pm3fb at the same time. We might save a few KiB from the kernel sources, but that's not worth the pain, and it would bloat the kernel for those with only pm2 or pm3 card(s). -- Romain DOLBEAU | Energy derives from both ENS Cachan / Ker Lann | the plus and negative Thesard IRISA / CAPS | -- Metallica, dol...@cl... | 'Eye of the Beholder' |
|
From: Sven <lu...@dp...> - 2002-04-15 09:57:52
|
On Sat, Apr 13, 2002 at 08:33:44AM +0200, Romain Dolbeau wrote: > > You might try to look at the possibility of merging it back into pm3fb, or > > at least merge the common parts of both drivers, altough i am not sure > > what romain thinks about it, since there were many changes to the pm3fb > > driver since romain worked on it, and it may not be easy or worthwhile to > > merge them together. > > Huh ? pm3fb in 2.4.19pre6 seems to be exactly the same as my CVS... Or > are you talking about the old attempt at a port that I put in > linux-console a while ago ? It someone managed to get it to work Id'd > like to hear of it, and eventually to merge the change that were done in > regular pm3fb since the first port. I was speaking about the time since you forked pm2fb into pm3fb. > I don't think merging is worth the effort. There's not that much code in > common (beside some registers definitions), pm2fb support more buses > than pm3fb (PCI/AGP -only), and very few people will need both pm2fb and > pm3fb at the same time. We might save a few KiB from the kernel sources, > but that's not worth the pain, and it would bloat the kernel for those > with only pm2 or pm3 card(s). I was just suggesting it so that the guy who wanted to look at pm2fb could look also at pm3fb for inspiration if he wanted to. Friendly, Sven Luther |
|
From: Jim H. <jim...@ac...> - 2002-04-17 11:07:55
|
On 15-Apr-2002 Sven wrote: > I was just suggesting it so that the guy who wanted to look at pm2fb could > look also at pm3fb for inspiration if he wanted to. Oh, I have been looking at pm3fb. Most Useful, thanks. I've now got Illo's last available driver working nicely (for me) under 2.4.18 (bar some tidying up). There were a couple of bugs relating to modes with low (h|v)sync which I've sorted out (I use a fixed-frequency monitor which requires low sync). I got delayed for a while making it work with the X Glint server. Romain, have you noticed that X Glint using the hardware cursor (the default), when used with UseFBDev=True *always* asks for high sync, regardless of the mode requested? I've bodged a 'force low sync' option into pm2fb to cope. -- Jim Hague - jim...@in... (Work), ji...@be... (Play) Never trust a computer you can't lift or you don't control. |
|
From: Romain D. <do...@ir...> - 2002-04-17 11:17:46
|
Jim Hague wrote: > I got delayed for a while making it work with the X Glint server. Romain, have > you noticed that X Glint using the hardware cursor (the default), when used with > UseFBDev=True *always* asks for high sync, regardless of the mode requested? > I've bodged a 'force low sync' option into pm2fb to cope. No, I didn't notice ; the sync stuff is an area I never thoroughly tested. My Iiyama 702HT can take about anything and display it :-) I can't even remember if my default X config use 'UseFBDev' or not. By your description, it definitely look like a XFree86 bug - or maybe a permedia3 'feature' that you can't use low sync with the HW cursor. Sven, any idea on that ? -- DOLBEAU Romain | We'll know for the first time ENS Cachan / Ker Lann | If we're evil or divine Thesard IRISA / CAPS | -- Dio, dol...@cl... | 'The Last In Line' |
|
From: Sven <lu...@dp...> - 2002-04-18 08:15:47
|
On Wed, Apr 17, 2002 at 01:15:25PM +0200, Romain Dolbeau wrote: > Jim Hague wrote: > > > I got delayed for a while making it work with the X Glint server. Romain, have > > you noticed that X Glint using the hardware cursor (the default), when used with > > UseFBDev=True *always* asks for high sync, regardless of the mode requested? > > I've bodged a 'force low sync' option into pm2fb to cope. > > No, I didn't notice ; the sync stuff is an area I never > thoroughly tested. My Iiyama 702HT can take about > anything and display it :-) I can't even remember if > my default X config use 'UseFBDev' or not. No, it doesn't, the fbdev code in the glint X driver is hardcoded for pm2fb. (and maybe even apus-pm2fb). > By your description, it definitely look like a XFree86 > bug - or maybe a permedia3 'feature' that you can't > use low sync with the HW cursor. Sven, any idea on that ? No, it has been a long time since i looked at that, and i have no real time for it right now. That said, i guess he is speaking about pm2fb + glint X driver, and i don't know if he uses USEFBDev or not, but like said, the glint X driver is hardcoded for pm2fb, and was done such, by Michel Daenzer i think, but it was a long time ago, in order to get it working on powerpc/apus(amiga with powerup board and Blizzard/CyberVision pm2 graphic board) hardware, so it is possible that it has some hardcoded stuff needed for the apus specific case. (but i thnk i have seen a mail from michel lower in the thread, so maybe he will tell you more) Friendly, Sven Luther |
|
From: Michel <mi...@da...> - 2002-04-17 11:39:35
|
On Wed, 2002-04-17 at 13:07, Jim Hague wrote: >=20 > I got delayed for a while making it work with the X Glint server. Romain,= have > you noticed that X Glint using the hardware cursor (the default), when us= ed with > UseFBDev=3DTrue *always* asks for high sync, regardless of the mode reque= sted? IIRC I added that code because the HW cursor didn't work with low sync on the Permedia2 board I worked with. --=20 Earthling Michel D=E4nzer (MrCooper)/ Debian GNU/Linux (powerpc) developer XFree86 and DRI project member / CS student, Free Software enthusiast |
|
From: Jim H. <jim...@ac...> - 2002-04-17 12:01:08
|
On 17-Apr-2002 Michel Dänzer wrote: > On Wed, 2002-04-17 at 13:07, Jim Hague wrote: >> >> I got delayed for a while making it work with the X Glint server. Romain, >> have >> you noticed that X Glint using the hardware cursor (the default), when used >> with >> UseFBDev=True *always* asks for high sync, regardless of the mode requested? > > IIRC I added that code because the HW cursor didn't work with low sync > on the Permedia2 board I worked with. The Permedia2 and Permedia3 frame buffer drivers both now set high sync in all cases, and use the RAMDAC to invert the sync if low is required, just like the X Glint driver. This wasn't the case in the past. So I suppose that code has outlived its usefulness. I'll file a bug report. -- Jim Hague - jim...@in... (Work), ji...@be... (Play) Never trust a computer you can't lift or you don't control. |
|
From: Sven <lu...@dp...> - 2002-04-18 08:18:30
|
On Wed, Apr 17, 2002 at 01:01:03PM +0100, Jim Hague wrote: > On 17-Apr-2002 Michel D=E4nzer wrote: > > On Wed, 2002-04-17 at 13:07, Jim Hague wrote: > >>=20 > >> I got delayed for a while making it work with the X Glint server. Ro= main, > >> have > >> you noticed that X Glint using the hardware cursor (the default), wh= en used > >> with > >> UseFBDev=3DTrue *always* asks for high sync, regardless of the mode = requested? > >=20 > > IIRC I added that code because the HW cursor didn't work with low syn= c > > on the Permedia2 board I worked with. >=20 > The Permedia2 and Permedia3 frame buffer drivers both now set high sync= in all > cases, and use the RAMDAC to invert the sync if low is required, just l= ike the > X Glint driver. This wasn't the case in the past. This will most probably break the glint X driver on apus boards, not nice. That said, the permedia3 glint driver don't use "USEFBDev", and i guess y= ou should be able to run your pci based permedia2 board without this option = even if you have are using pm2fb. > So I suppose that code has outlived its usefulness. Unless there are no more apus users, then you might be right, but it woul= d be best to still support these boards, i may be wanting to resurect mine one= of those days :))) Friendly, Sven Luther |
|
From: James S. <jsi...@tr...> - 2002-04-16 19:08:42
|
> Huh ? pm3fb in 2.4.19pre6 seems to be exactly the same as my CVS... Or > are you talking about the old attempt at a port that I put in > linux-console a while ago ? Hm. Now that a good chunk of the new new fbdev api is in the Dave Jones tree would you like to give it a try for porting again? I'm even working on docs right now, I'm presenting a talk on it soon. |
|
From: Romain D. <do...@ir...> - 2002-04-17 08:57:21
|
James Simmons wrote: > Hm. Now that a good chunk of the new new fbdev api is in the Dave Jones > tree would you like to give it a try for porting again? I'm even working > on docs right now, I'm presenting a talk on it soon. I'd like to, but the DJ tree disagree with us. <driver/macintosh/macserial.c> doesn't compile. After disabling it, <driver/macintosh/mac_hid.c> doesn't compile. After disabling all HID, <driver/macintosh/adb.c> doesn't compile. At that point I gave up, as obviously the DJ tree cannot be used on a PPC. Unfortunately the only permedia3 card I own live in a PPC box, so the port will have to wait a bit more. -- DOLBEAU Romain | We'll know for the first time ENS Cachan / Ker Lann | If we're evil or divine Thesard IRISA / CAPS | -- Dio, dol...@cl... | 'The Last In Line' |
|
From: Romain D. <do...@ir...> - 2002-04-18 08:35:40
|
Romain Dolbeau wrote: > > James Simmons wrote: > > > Hm. Now that a good chunk of the new new fbdev api is in the Dave Jones > > tree would you like to give it a try for porting again? I'm even working > > on docs right now, I'm presenting a talk on it soon. > > I'd like to, but the DJ tree disagree with us. Apparently it's not really the DJ tree, regular 2.5.8 doesn't build on my box either. -- DOLBEAU Romain | I witness a time and a place that never dies, ENS Cachan / Ker Lann | still frozen in time, this darkness the only Thesard IRISA / CAPS | place that I can hide. I witness, a dream. dol...@cl...| -- Black Sabbath, 'I Witness' |
|
From: Sven <lu...@dp...> - 2002-04-11 07:10:39
|
On Wed, Apr 10, 2002 at 12:45:16PM -0700, James Simmons wrote: > > I just got my hands on a Permedia 2 card. This card has on it a S3 virge > chip for vga modes and a 3DLabs GLINT delta and 500TX chips on it. Did > anyone manage to get it to work? James, ... This is not a permedia2 board. it is a delta+tx combo, while the permedia2 chip had the delta core on die. I don't know even if it is a permedia chip (i think the glint R1 are another name for permedia1, but i suppose that glint delta is only one chip, which may or may not be a permedia1 chip). What does lspci or scanpci say about it ? I guess that what really happens here is that you have one delta chip, which comprise just a geometry setup unit and some other 3d stuff, not really used for fbdev, and a 500TX rasterizer coupled with the S3 virge ramdac possibly, and this is what you would want to address. The X server does have support for this kind of config, so you could look there for inspiration if you want. Friendly, Sven Luther |
|
From: James S. <jsi...@tr...> - 2002-04-11 19:29:47
|
> > chip for vga modes and a 3DLabs GLINT delta and 500TX chips on it. Did > > anyone manage to get it to work? > > James, ... > > This is not a permedia2 board. it is a delta+tx combo, while the permedia2 > chip had the delta core on die. > > I don't know even if it is a permedia chip (i think the glint R1 are another > name for permedia1, but i suppose that glint delta is only one chip, which may > or may not be a permedia1 chip). > > What does lspci or scanpci say about it ? 00:0c.0 VGA compatible unclassified device: S3 Inc. 86c325 [ViRGE] (rev 05) Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop+ ParErr- Stepping- SERR- FastB2B- Status: Cap- 66Mhz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- Latency: 32 (1000ns min, 63750ns max) Interrupt: pin A routed to IRQ 11 Region 0: Memory at dc000000 (32-bit, non-prefetchable) [size=64M] Expansion ROM at 000c0000 [disabled] [size=64K] 00:0c.1 Non-VGA unclassified device: 3DLabs GLINT Delta (rev 01) Control: I/O- Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap- 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- Latency: 32 (48000ns min, 48000ns max) Interrupt: pin A routed to IRQ 11 Region 0: Memory at db800000 (32-bit, non-prefetchable) [disabled] [size=128K] 00:0c.2 Non-VGA unclassified device: 3DLabs GLINT 500TX (rev 01) Control: I/O- Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap- 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- Latency: 32 Interrupt: pin A routed to IRQ 11 Region 0: Memory at db000000 (32-bit, non-prefetchable) [disabled] [size=128K] Region 1: Memory at da000000 (32-bit, non-prefetchable) [disabled] [size=16M] Region 2: Memory at d9800000 (32-bit, non-prefetchable) [disabled] [size=8M] Region 3: Memory at d8000000 (32-bit, non-prefetchable) [disabled] [size=16M] Expansion ROM at e3fa0000 [disabled] [size=64K] > I guess that what really happens here is that you have one delta chip, which > comprise just a geometry setup unit and some other 3d stuff, not really used > for fbdev, and a 500TX rasterizer coupled with the S3 virge ramdac possibly, > and this is what you would want to address. > > The X server does have support for this kind of config, so you could look > there for inspiration if you want. Not yet. The main goal was to port the PM2 driver over to the new api. I was hoping I came around the hardware I needed. |
|
From: Sven <lu...@dp...> - 2002-04-11 23:11:48
|
On Thu, Apr 11, 2002 at 12:29:37PM -0700, James Simmons wrote: > Not yet. The main goal was to port the PM2 driver over to the new api. I > was hoping I came around the hardware I needed. No, this is as i have guessed, a delta + TX500 board. Friendly, Sven Luther |
Thanks for helping keep SourceForge clean.
X