public inbox for linux-msdos@vger.kernel.org
 help / color / mirror / Atom feed
* Re: Can I use DOSEMU for testing device driver code?
@ 2004-02-13 20:12 Stas Sergeev
  0 siblings, 0 replies; 16+ messages in thread
From: Stas Sergeev @ 2004-02-13 20:12 UTC (permalink / raw)
  To: linux-msdos


Hello.

Edenyard wrote:
> It appears that DOSEMU has BIG problems when one wants to do this sort
> of thing and nobody quite seems to know why.
Yes, this is the case sometimes, but
usually it is not.

> Last time I asked about this on the mailing list, the response
> I got was, "What's RTS?"....
What have you expected? You haven't
provided the test-case program, no
logs either, you haven't even opened
a bug report on SF tracker.
No reply only means that noone had
that problem previously.
I am using the serial ports via dosemu
at work every day, I can toggle both RTS
and CTS lines as well as the TX line,
the oscilloscope was attached just in
case - so if you sumbit a bug report
and provide at least some info and a
test-case, perhaps your problem would
have been resolved long ago already.
I was saying that in that list many
times and I can only repeat: problems
are not get fixed themselves! You have to
do at least something to get them fixed,
at least open a bug report and provide
a test-case (or logs, but logs not always help).
Unfortunately even when explicitly asked,
many people are not willing to submit a bug
report. Nothing can be done in that case -
game over. On the other hand, some users
are not only providing a bug reports, but
are also willing to do many additional
tests that are required, and in most cases
that works very good. Please see this as
a recent example:
http://sourceforge.net/tracker/index.php?func=detail&aid=884096&group_id=49784&atid=457447

Hope that helps. Be reasonable. You were
asked "What's RTS" not because noone
knew that:)

^ permalink raw reply	[flat|nested] 16+ messages in thread
[parent not found: <4034D439.5080308@edenyard.co.uk>]
* Re: Can I use DOSEMU for testing device driver code?
@ 2004-02-15 11:15 Stas Sergeev
  0 siblings, 0 replies; 16+ messages in thread
From: Stas Sergeev @ 2004-02-15 11:15 UTC (permalink / raw)
  To: linux-msdos


Hello.

Ryan Underwood wrote:
>> The problem in (B) seems to be that all of my transmitted characters
>> disappear into a sort of 'virtual' UART to be transmitted later, whilst
>> the RTS signal seems to come out of the port in 'real' time. 
>  I don't think that is happening. i.e. in,out instructions are directly
>  executed, there is no emulation involved.
No, the "problem B" was about an
emulated access, which is indeed
going via an emulated UART.
Its latency was considerably
reduced in dosemu-1.2.0 (not in
any 1.1), but still of course can't
match the direct access.
The fact that RTS gets out of sync
with the TX looks like a bug, most
likely the emulated FIFO is being
switched on when it shouldn't. But
sigh, looks like that bug will have
to wait for the next time:)
Btw, from the docs I have, it is
unclear whether there are some
ways to disable the FIFO, other than
by writing to FCR directly. But I
strongly suspect that at least
changing the DLAB state also should
disables it, which may explain this
problem.
If someone have an info on that -
would be nice to have a look.

^ permalink raw reply	[flat|nested] 16+ messages in thread
* Re: Can I use DOSEMU for testing device driver code?
@ 2004-02-12 21:53 easlab
  2004-02-13  8:17 ` Edenyard
  2004-02-15  5:04 ` Ryan Underwood
  0 siblings, 2 replies; 16+ messages in thread
From: easlab @ 2004-02-12 21:53 UTC (permalink / raw)
  To: linux-msdos; +Cc: easlab

On Thu, Feb 12, 2004 at 04:11:34AM -0200, synthespian wrote:
> >  I have a "special need" wrt DOSEMU: I
> > have this excellent book on
> > programming for hardware (device
> > drivers), but it's written only for
> > DOS/Win32. But it's a /very/ good
> > book, full of C code.
> >  As I don't have a DOS/Windows
> > platform and I would really like to
> > use this book, I was wondering if
> > DOSEMU could help me.=20
> >  I wonder if you implement device
> > control in a standard DOS way, using
> > wrappers that remain faithful to the
> > DOS original. I imagine that, by
> > studying your code, I could learn how
> > to program the stuff I want, while at
> > the same time beeing able to use the
> > book /and/ learning about Linux.

Ryan Underwood wrote:
> Device drivers in DOSEMU that need to access hardware/host OS resources
> are implemented in a static manner; i.e. the necessary ISR is already
> installed at the time when you start dosemu.   You can hook those ISR to
> add your own functionality, but you will not be able to access the
> hardware (port I/O or IRQ) of the host machine without specifically
> allowing DOSEMU to do so (see $_ports and friends).  Only the drivers
> that are installed when DOSEMU is started are allowed to access host
> hardware otherwise.
> 
> 
> That said, what type of device are you programming?  If it is controlled
> just through some hardware registers and polling, $_ports should work
> for you.  If it needs an interrupt, you need to also pass its IRQ to
> dosemu through the config file and make sure linux doesn't have
> something already on that IRQ.  This is for DOS drivers; I don't know
> anything about how Windows drivers would interact with DOSEMU.

All my DOS application can't do is toggle 2 pins of the par-port.
No interupts.      dosemu-1.1.99 as root, won't do it, even with
editing dosemu.conf to:
     $_ports { device /dev/lp1 fast range 0x378 0x37f } # lpt1
and other combinations

Under DOS these are the correct port addresses.
Has any body ever done this ?

== Chris Glur.



^ permalink raw reply	[flat|nested] 16+ messages in thread
* Can I use DOSEMU for testing device driver code?
@ 2004-02-12  6:11 synthespian
  2004-02-12 10:15 ` Ryan Underwood
  0 siblings, 1 reply; 16+ messages in thread
From: synthespian @ 2004-02-12  6:11 UTC (permalink / raw)
  To: linux-msdos

Hello --

 I have a "special need" wrt DOSEMU: I
have this excellent book on
programming for hardware (device
drivers), but it's written only for
DOS/Win32. But it's a /very/ good
book, full of C code.
 As I don't have a DOS/Windows
platform and I would really like to
use this book, I was wondering if
DOSEMU could help me. 
 I wonder if you implement device
control in a standard DOS way, using
wrappers that remain faithful to the
DOS original. I imagine that, by
studying your code, I could learn how
to program the stuff I want, while at
the same time beeing able to use the
book /and/ learning about Linux.
 
 Any thoughts?

 Thank you,
 Regs,

 Henry 

PS: I was unable to download the
source at sourceforge, just gave me a
blank page.
PS2: Would you kindly reply also to
me, if at all possible (I don't
subscribe to the list yet - should I?)


 
---
Acabe com aquelas janelinhas que pulam na sua tela.
AntiPop-up UOL - É grátis! 
http://antipopup.uol.com.br

-
To unsubscribe from this list: send the line "unsubscribe linux-msdos" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

^ permalink raw reply	[flat|nested] 16+ messages in thread
end of thread, other threads:[~2004-02-19 18:36 UTC | newest]

Thread overview: 16+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2004-02-13 20:12 Can I use DOSEMU for testing device driver code? Stas Sergeev
     [not found] <4034D439.5080308@edenyard.co.uk>
2004-02-19 18:36 ` Ged Haywood
  -- strict thread matches above, loose matches on Subject: below --
2004-02-15 11:15 Stas Sergeev
2004-02-12 21:53 easlab
2004-02-13  8:17 ` Edenyard
2004-02-13 12:01   ` Bart Oldeman
2004-02-14 12:52     ` Edenyard
2004-02-15  4:58       ` Ryan Underwood
2004-02-16 11:27         ` Edenyard
2004-02-17  7:52           ` Ryan Underwood
2004-02-17  9:36           ` Ged Haywood
2004-02-15  5:04 ` Ryan Underwood
2004-02-12  6:11 synthespian
2004-02-12 10:15 ` Ryan Underwood
2004-02-14 19:00   ` EL Henry
2004-02-15  4:53     ` Ryan Underwood

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox