Currently the Win4Lin access to the serial ports is via the "Mserial"
driver modules. This is hardwired for standard COM1 and COM2:
COM1: IRQ4 and 3f8-3ff
COM2: IRQ3 and 2f8-2ff
Currently there is no way to change these settings so creating
new nodes or definitions will not have an effect.
There are no COM3 or COM4 setings in the driver.
-David
Direct attachment currently only works with IO ports. IRQ is not supported.
(This is only used for attaching the parallel ports or the game port.)
David Toso wrote:
>
> I apologise in advance for the long message, but I'd like to avoid giving
> misleading information or ambigous context in my questions.
>
> I am trying to use a PalmIII with Win4Lin on my IBM 770ED Thinkpad
> notebook, but have not been able to get this configuration working.
>
> I *have* read all the documentation, knowledge-base answers, and Win4Lin
> mailing list archives covering the areas of: serial ports, palm pilots,
> dos/win device configuration.
>
> I'll admit now that my MS-Windows experience is *MUCH* less than my
> Unix/Linux experience, but have had no real problems with configuring
> Win4Lin until now. I had earlier backed up my /var/win4lin and $HOME/win
> directories, and after each of the unsuccesful changes, I reverted the
> installation to a fully working state (without serial support).
>
> The Thinkpad claims com1 (io=0x3f8-0x3ff, irq=4 --> /dev/ttyS0) for its
> InfraRed port, and I need to be able to use that port as well, so I don't
> have the option of disabling the port (I have been testing this
> installation with the IR port configured, but not in use).
>
> When I modprobe the serial.o module, the first detected port is com3
> (io=0x3e8-0x3ef, irq=4 --> /dev/ttyS2).
>
> I have verified that this port is functioning under linux, by doing:
> cat /dev/ttyS2
> then using the palm (Symbol Palm 1500), I run the "serial port test" in
> the in the Diagnostics application. I can see the data sent ("This is a
> test.") by the palm in the linux console running 'cat'.
>
> I realise (correct english spelling) that there may be a problem with irq
> conflicts due to both devices using the same interupt, however, linux
> seems very happy to allocate it. I have also tried using 'setserial' to
> manually reconfigure com3 to use irq 3 -- it worked in linux, but it made
> no difference to Win4Lin.
>
> I have installed (correctly I believe) the Windows side of the serial port
> device, and all attempts reading/writing Com3 (direct, virtual), and Com1
> (direct remapped) have failed with an error like "incorrect file
> permissions on device". (I'll redo that configuration if anyone needs the
> exact error - sorry). As per the knowledge-base answers, I did change the
> permissions on the (/dev and /var/win4lin/mrgdev -- all permutations)
> devices to 0777, but no prize.
>
> I have tried experimenting with the "Custom" class of devices in "Device
> Definition", adding via both "Direct attach" and "Virtual attach". I've
> tried all of this with and without the serial.o module loaded (just in
> case some Win4Lin kernel code prefers to allocate the irq's etc).
>
> I've tried removing the Com1 and Com2 tokens, then creating a "direct
> attatchment" with "irq 4" remapped to "irq 4", and "io port 0x3e8-0x3ef"
> remapped to "io port 0x3f8-0x3ff). Result: "ERROR: Could not allocate
> interrupt vector 4"
>
> I've tried creating character special devices (using mknod) for com3/4
> under /var/win4lin/mrgdev/vpi and /var/win4lin/mrgdev/ppi (so that their
> entries follow the major/minor device sequence, and so that they have the
> same naming conventions and file permissions).
>
> I'm at the end of what I can do myself without some sort of interface
> documentation for the Win4Lin kernel modules... hell I'll even write my
> own kernel modules if it will alleviate this problem, but I hold no hope
> of ever seeing that documentation, as the Win4Lin kernel modules,
> replacement windows executables, drivers and dlls are the sum total of the
> Trelos's/Netraverse's intellectual property (that I can see from mu
> perhaps limited perspective) in the Win4Lin product.
>
> I'm now becoming desparate, and would apreciate *ANY* help I can find from
> this list.
>
> David Toso.
>
> PS: Another, non-urgent matter (maybe for the kernel mailing list): does
> anyone know to transparently redirect serial ports to TCP/IP sockets in
> both Linux and Windows? I am working on a product which has serial
> communications occuring between a PalmOS application and a Win32 program.
> (It does work in windows, but my laptop is a single-boot linux box, and
> thats how it will stay.) So I would like to try having the Win32 program
> running under Win4lin talk directly to the PalmOS application running
> under the Palm Pilot emulator (poser) -- any ideas?
>
> _______________________________________________
> Win4Lin-users mailing list
> [EMAIL PROTECTED]
> https://lists.netraverse.com/mailman/listinfo/win4lin-users
_______________________________________________
Win4Lin-users mailing list
[EMAIL PROTECTED]
https://lists.netraverse.com/mailman/listinfo/win4lin-users
