From: viking <vi...@fl...> - 2005-03-21 23:31:39
|
On Mon, Mar 21, 2005 at 12:44:26PM -0800, Andrew Morton wrote: > > Guys, we seem to have a tridentfb regression in 2.6.12-rc1. > > viking <vi...@fl...> wrote: > > > > Also (and this is something I've noticed since I tried tridentfb) the video > > buffer never seems to get cleared, except when I change virtual terminals, > > then change back to the terminal concerned. THEN it's cleared. So for the > > moment, I've gone back to using VESAfb. ********** Actually, it's in every release I've ever tested. ********** I hadn't mentioned it before, because vesafb does what I want, apart from not being resizable. I have a Apollo MVP4, VIA686A (or B) video chipset, though the Video shows itself as a CyberBlade/i7: brick$ lspci -v -v ... 01:00.0 VGA compatible controller: Trident Microsystems CyberBlade/i7 (rev 5d) (prog-if 00 [VGA]) Subsystem: FIRST INTERNATIONAL Computer Inc: Unknown device 9915 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 10 Region 0: Memory at e5800000 (32-bit, non-prefetchable) [size=8M] Region 1: Memory at e6000000 (32-bit, non-prefetchable) [size=128K] Region 2: Memory at e5000000 (32-bit, non-prefetchable) [size=8M] Expansion ROM at <unassigned> [disabled] [size=64K] Capabilities: [80] AGP version 1.0 Status: RQ=33 Iso- ArqSz=0 Cal=0 SBA+ ITACoh- GART64- HTrans- 64bit- FW- AGP3- Rate=x1,x2 Command: RQ=1 ArqSz=0 Cal=0 SBA- AGP- GART64- 64bit- FW- Rate=<none> Capabilities: [90] Power Management version 1 Flags: PMEClk- DSI+ D1+ D2+ AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-) Status: D0 PME-Enable- DSel=0 DScale=0 PME- I have via-agp and agpgart loaded, though those aren't for 2d. Not sure what else to tell you, to be honest. If I put BOTH the vesafb AND the tridentfb into the kernel, and select vesafb on lilo (video=vesafb:mtrr,ypan), the kernel boots up using tridentfb regardless. The 640x480-60 (the one the kernel seems to boot up on unless told otherwise) screenmode looks absolutely shocking, with a very wiggly screen mainly in the X direction. That's probably due to the definition in drivers/video/modedb.c, something I can either tweak myself, or avoid using. I'll do more testing, see what I come up with aside from that. You may need to tell me what other details you want though. Andrew - you still wish to be CC:ed on this video issue? -- /| _,.:*^*:., |\ Cheers from the Viking family, including Pippin, our cat | |_/' viking@ `\_| | | flying-brick | $FunnyMail : What do you mean, I've lost the plot? \_.caverock.net.nz_/ 5.40 : I planted them carrots right here!! |