I had an idea that you might be be able to do this via /proc but a test in my environment (Linux 2.4, GForce 2 MX) was disppointing although I was able to retrive the boundary address for the vid card address space. Unfortunately I am using the NON-OPENSOURCED (sheesh) NVidia Drivers so I couldn't look at the driver source for clues.
But I suspect even if you do have the register addresses in hand for you card you will have resort to 'C' to get grab register info directly or interrogate the driver.
Update: Erik Hensema is right on. I am so used to thinking in terms my own dev environment where I am grand poobar :). Registers of interest will as Eric points out reside in kernel space and require privileged access. To expand on Eric's idea you could look at Xconfigurator( is this a Red Hat Only thing?) source
since it does probe for monitor type.
mitd-Made in the Dark
'Interactive! Paper tape is interactive!
If you don't believe me I can show
you my paper cut scars!'
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
| |
For: |
|
Use: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.