Products > Test Equipment
Linux on CRTU-RU (o;
davorin:
Well...remote launching of X programs works now (o;
But still no LCD Screen or out-of-sync Messages on external VGA Monitor....
fisafisa:
...
For all the memory mapped boards, it would be very good to be able to read back the memory....after initialisation.
I wonder if there are ways to intercept the IO calls and log them too.
Also useful, under linux, would be a way to map these addresses to user-space, so that one can test things without need to write drivers.
Just some ideas.
Filippo
nctnico:
Perhaps you can run some kind of DOS mode VM which can capture/log all the memory transactions. This may actually be easier using Windows and a debugger.
Wuerstchenhund:
--- Quote from: fisafisa on November 08, 2015, 04:56:52 pm ---...
For all the memory mapped boards, it would be very good to be able to read back the memory....after initialisation.
I wonder if there are ways to intercept the IO calls and log them too.
--- End quote ---
Well, there's still debug:
http://thestarman.pcministry.com/asm/debug/debug.htm
fisafisa:
Dosemu seems promising.
It has the ability to pass-through IOs apparently.
And look and behold what the author writes in the plugin section:
"
For what can plug-ins be used?
------------------------------
The main reason I implemented 'plugin' was the need to write a DOS driver for
some (very) special selfmade Hardware, which nobody else would profit from
except my employer ... and because I was too lazy to patch in the changes to
every new released dosemu version;-) This way DOSEMU atleast profits from the
interface.
Having it now, I see some more usage such as
- DOS drivers using 32-bit written by contributors
and distributed separately.
- special debugging code to reverse engineer (DOS) drivers for special
hardware, if the manufacturer does not cooperate in writing
a Linux driver. Also with this, distributing separately can avoid
copyright conflicts.
- Replacements for DOS system commands, which (via inte6) then run
faster in 32-bit or can do things which aren't possible otherwise.
- Drivers for video chips we currently do not support.
We even may consider to move more of our current code into plugin
(as we just did with the keyboard code), this would make it possible to
distribute them separately. It may be necessary to add some more hooks
(plugin_*.h), but for this we wait what happens;-)
"
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version