Browsing this Thread:
1 Anonymous Users
|
Re: Issues with Nvida driver/hidd
|
||||
|---|---|---|---|---|
|
Home away from home
 
|
I was afraid of that... well, it shouldn't be too much trouble to not add the BIOS data areas in when the memlists are being built. You lose a few K of memory - big deal. I'll look at that when I look into changing the VESA code.
Posted on: 2004/11/25 23:27
|
|||
|
||||
|
Re: Issues with Nvida driver/hidd
|
||||
|---|---|---|---|---|
|
Home away from home
|
Quote:
The only thing that would prevent you from using the older vbe would be if native mode overwrote the BIOS data area in memory as most video BIOSes put some of the data they need in the regular and extended BIOS data areas. Um... I think Native does overwrite the BIOS Data area.
Posted on: 2004/11/24 20:42
|
|||
|
||||
|
Re: Issues with Nvida driver/hidd
|
||||
|---|---|---|---|---|
|
Home away from home
|
Quote:
Actually, I was referring to the 16-bit protected-mode vbe interface that is guaranteed to be on every card.  It takes a wrapper routine to act as the thunk to and from 16-bit mode, but as I said before, the code has been around for almost a decade. I used it myself in a project some six or seven years ago. The only thing that would prevent you from using the older vbe would be if native mode overwrote the BIOS data area in memory as most video BIOSes put some of the data they need in the regular and extended BIOS data areas. Other than that, there were a few "quirks" you had to look for - improper reporting of 15bit vs 16 bit modes... things like that. I'll dig up my old VESA code and see if maybe I can't work that into the VESA driver.
Posted on: 2004/11/24 17:39
|
|||
|
||||
|
Re: Issues with Nvida driver/hidd
|
||||
|---|---|---|---|---|
|
Home away from home
|
Quote:
Which one do you mean? Using the RealMode to switch resolutions or rather using the 32-bit vbe interface which is hardly implemented even on NVidia cards? The real mode resolution switching is a little bit tricky and perhaps an x86 emulator (or x86 virtual mode) should be used in order to implement it.
Posted on: 2004/11/24 6:18
|
|||
|
||||
|
Anonymous
|
Re: Issues with Nvida driver/hidd
|
|||
|---|---|---|---|---|
|
well,
im not sure if it is possible to change the vesa resolution at runtime. but sure this is some great talk, including the mesa support (i wonder if would worth to support the warp functions) aros has lots of stuff in the todo list...but i think the core is going very well (showing how thing should be done), im tring to see if the arosmax stable fit the iso bountie. if i can reach that, i would like to bountie, and i think in 2 things: 1- implement JOBS,Signaling and a [fake] Fork() handle support 2- support for mouse scroller in intuition, fix the save option in fkey and implement iconx support in the ML are talks about timer stuff...so maybe a higer precision device can appear at some point! having tcp/ip and the (1) topic would make me "live" inside aros much easier! :vik1: ps: nicja was working on update our mesa port, dunno what is the status! |
||||
|
||||
|
Anonymous
|
Re: Issues with Nvida driver/hidd
|
|||
|---|---|---|---|---|
|
Sounds like a serious amount of work, but nesscesary work.
Maybe the community needs to consider a bounty for this. I would, but I would have to wait till Jan before I can start any bounties. I have a few in mind, waiting on getting my house sold, move and live through the holidays. Tis the season. .Quote: It really bugs the hell out of me to tell WB or a game to use it's own screen at 640x480, but it merely draws to the upper left corner of the 1024x768 display that was opened at boot time. It is one of the stranger things I have seen in AROS. Never knew why. Would be nice to have that "fixed" P.S. thanks for the explination. It is really appricated |
||||
|
||||
|
Re: Issues with Nvida driver/hidd
|
||||
|---|---|---|---|---|
|
Home away from home
|
Quote:
Well, you'd have to remove the fake vertical blank code and add some kind of support in the video hidd for vertical blank interrupts. Then the hidd can decide to do a real vertical blank or to fake it if one isn't available. I'll take a look at the video code sometime to see what else can be done to improve things. One thing in particular I've wanted to do - add support for REAL resolution changing. It really bugs the hell out of me to tell WB or a game to use it's own screen at 640x480, but it merely draws to the upper left corner of the 1024x768 display that was opened at boot time. VESA code to change the resolution has been out since the early 90's... who the heck wrote this code? Same business with hosted - why do you only get a window? How about a nice full-screen display like you find with most X Windows programs. There's plenty of code to show how to open a full screen X Window at whatever resolution you want. The video needs a SERIOUS updating. The hidd should at least also define a basic set of 3D operations similar to Warp3D. On hosted, it would just call the hosted libGL. For native, you would have software routines with hardware support for documented cards like the Voodoo, Permedia, Virge, Savage, and older Radeons. An up to date version of Mesa that used the hidd 3D functions would be great... you'd get accelerated 3D when available that way.
Posted on: 2004/11/23 19:39
|
|||
|
||||
|
Anonymous
|
Re: Issues with Nvida driver/hidd
|
|||
|---|---|---|---|---|
|
Quote:
Thanks! At least I know that I am not crazy. |
||||
|
||||
|
Anonymous
|
Re: Issues with Nvida driver/hidd
|
|||
|---|---|---|---|---|
|
Quote:
Ok. Just to ask. How hard would doing these things including supporting Vertical Blank be? |
||||
|
||||
|
Re: Issues with Nvida driver/hidd
|
||||
|---|---|---|---|---|
|
Home away from home
|
The nvidia.hidd driver relies on the VendorID/ProductID of the gfx card, and the table of supported devices has to be actualized all the time. Unfortunatelly it was not refreshed for a long time.
Time for update then ;) I'll try to do it next weeks.
Posted on: 2004/11/23 12:05
|
|||
|
||||
You can view topic.
You cannot start a new topic.
You cannot reply to posts.
You cannot edit your posts.
You cannot delete your posts.
You cannot add new polls.
You cannot vote in polls.
You cannot attach files to posts.
You cannot post without approval.
You cannot use topic type.
You cannot use HTML syntax.
You cannot use signature.
You cannot create PDF files.
You cannot get print page.
