On Fri, May 30, 2008 at 09:47:59AM +0200, Giovanni Maruzzelli wrote:
>Thanks Christopher, thanks Dave,
>
>the last snapshot (cygwin1-20080529.dll.bz2) works perfectly both with
>/dev/ttyS5 and /dev/com6
Interesting. Thanks for the verification.
cgf
--
Unsubscribe info: http://cygwin.com/ml
Thanks Christopher, thanks Dave,
the last snapshot (cygwin1-20080529.dll.bz2) works perfectly both with
/dev/ttyS5 and /dev/com6
Cheers,
Giovanni
On Thu, May 29, 2008 at 7:12 PM, Christopher Faylor
<[EMAIL PROTECTED]> wrote:
> On Thu, May 29, 2008 at 07:02:40PM +0200, Giovanni Maruzzelli wrote:
Thank you Christopher!!
I'll try the snapshot tomorrow as soon as I'll be back in office and
then I'll report back.
On Thu, May 29, 2008 at 7:12 PM, Christopher Faylor
<[EMAIL PROTECTED]> wrote:
> On Thu, May 29, 2008 at 07:02:40PM +0200, Giovanni Maruzzelli wrote:
>>Correction, my last post w
Christopher Faylor wrote on 29 May 2008 17:52:
> On Thu, May 29, 2008 at 05:15:00PM +0100, Dave Korn wrote:
>> Giovanni Maruzzelli wrote on 29 May 2008 16:41:
>>
>>> Thanks a lot Dave!
>>>
>>> Seems that it is looking for a \Device\Serial5
>>
>> Ouch. That's a problem. Not all serial devices
On Thu, May 29, 2008 at 07:02:40PM +0200, Giovanni Maruzzelli wrote:
>Correction, my last post was ambiguous:
>
>.\\com6 gives me "Device or resource busy", while all other com*
>give me "not existing".
>So, it is definitely better, it finds something! But do not yet works.
This is a red herr
Correction, my last post was ambiguous:
.\\com6 gives me "Device or resource busy", while all other com*
give me "not existing".
So, it is definitely better, it finds something! But do not yet works.
> Opening and read/writing to COM6 with native win32 API (readfile
etc) works well, both
On Thu, May 29, 2008 at 05:15:00PM +0100, Dave Korn wrote:
>Giovanni Maruzzelli wrote on 29 May 2008 16:41:
>
>> Thanks a lot Dave!
>>
>> Seems that it is looking for a \Device\Serial5
>
> Ouch. That's a problem. Not all serial devices use the same name format.
So what format do they use?
>
.\\com6 gives me "Device or resource busy", while all other com*
give me "not existing".
So, it is definitely better. But do not yet works. Opening and
read/writing to it with native win32 API works (readfile etc)
following is the relevant strace:
67 36177 [main] ciapa 756 open: open (\
Giovanni Maruzzelli wrote on 29 May 2008 16:41:
> Thanks a lot Dave!
>
> Seems that it is looking for a \Device\Serial5
Ouch. That's a problem. Not all serial devices use the same name format.
Although it's not strictly supported, you might be able to work around it
by using ".\\com6"
Thanks a lot Dave!
Seems that it is looking for a \Device\Serial5
This is the relevant part from strace on Vista:
39 36235 [main] ciapa 3780 open: open (/dev/ttyS5, 0xC002)^M
47 36282 [main] ciapa 3780 normalize_posix_path: src /dev/ttyS5^M
38 36320 [main] ciapa 3780 normalize_po
Giovanni Maruzzelli wrote on 29 May 2008 16:12:
> Errno reports just "no such file or directory".
> Same if you try something like "echo ATH > /dev/ttyS5"
>
> Probably some 1.7 initialization is not done in the same way as in 1.5.25.
>
> It is a sad situation for me:
> with 1.5.25 waveinopen cra
Ooops (I got the doubt Dave were joking :-))
Errno reports just "no such file or directory".
Same if you try something like "echo ATH > /dev/ttyS5"
Probably some 1.7 initialization is not done in the same way as in 1.5.25.
It is a sad situation for me:
with 1.5.25 waveinopen crashes (but it work
Giovanni Maruzzelli wrote on 29 May 2008 15:27:
> Hi Dave,
>
> thank you for the answer.
>
> You mean that this is a bug into 1.7?
My answer was slightly tongue in cheek! :) But yes, it's very likely
you've uncovered a bug in 1.7 - it is work-in-progress after all. There
might be an issue i
Hi Dave,
thank you for the answer.
You mean that this is a bug into 1.7?
Below the errno checking test case ;-)
=
#include
#include
#include
#include
#include
#include
#include
int main (int argc, char* argv[])
{
struct termios params;
int tty;
tty = open ("/dev/ttyS5", O_RDWR |
Giovanni Maruzzelli wrote on 29 May 2008 13:59:
> I cannot see the serial ports (/dev/ttyS*), it seems that they do not
> exist under Vista (tried both as a user with admin rights and as
> Administrator, and tried also with AUC disabled).
>
> Is this a known bug?
What, not checking errno?
> i
On Sun, Apr 23, 2006 at 08:26:02PM +0200, Oliver Vecernik wrote:
>But I can even list ports that definitely do not exist:
>
>$ ls /dev/ttyS1
>/dev/ttyS1
>...
>$ ls /dev/ttyS15
>/dev/ttyS15
>
> The only physical ports that really exists are `/dev/ttyS0' and
>`/dev/ttyS3'. Is this the expected beha
Christopher Faylor schrieb:
> Actually, "ls /dev/ttyS3" *does* display proper information. It is "ls /dev"
> which does not show all virtual devices.
You're absolutely right:
$ ls /dev
log=
But I can even list ports that definitely do not exist:
$ ls /dev/ttyS1
/dev/ttyS1
...
$ ls /dev/tty
On Sun, Apr 23, 2006 at 04:44:46PM +0200, Oliver Vecernik wrote:
>Dave Korn schrieb:
>>Trying to mix win32 perl and cygwin is a recipe for tears. Sure, use
>>CPAN modules, that is of course a good idea; but if the *nix one
>>doesn't work under cygwin, fixing it or rolling your own or even just
>>u
On 23 April 2006 15:45, Oliver Vecernik wrote:
> Dave Korn schrieb:
>> Trying to mix win32 perl and cygwin is a recipe for tears. Sure, use
>> CPAN modules, that is of course a good idea; but if the *nix one doesn't
>> work under cygwin, fixing it or rolling your own or even just using the
>> b
Dave Korn schrieb:
> Trying to mix win32 perl and cygwin is a recipe for tears. Sure, use CPAN
> modules, that is of course a good idea; but if the *nix one doesn't work under
> cygwin, fixing it or rolling your own or even just using the bog-standard file
> i/o features in perl is definitely fa
On 23 April 2006 15:26, Alexander J. Herrmann wrote:
> And what is the final answer? Is there a
>
> /dev/ttySx
> in Cygwin which can be used in Perl or C, even if I can not see it with ls?
> Alex
Oh, blimey, didn't you see that! Igor already answered it: the answer is
yes, the /dev directory
And what is the final answer? Is there a
/dev/ttySx
in Cygwin which can be used in Perl or C, even if I can not see it with ls?
Alex
Dave Korn wrote:
On 23 April 2006 05:44, David Christensen wrote:
Dave Korn wrote:
Well then, that's a really good argument for just using the built
On 23 April 2006 05:44, David Christensen wrote:
> Dave Korn wrote:
>> Well then, that's a really good argument for just using the builtin
>> access that cygwin provides through /dev/ttySx instead, isn't it?
>> The way Oliver's original post reads suggests that he was just thrown
>> off by not see
Dave Korn wrote:
> Well then, that's a really good argument for just using the builtin
> access that cygwin provides through /dev/ttySx instead, isn't it?
> The way Oliver's original post reads suggests that he was just thrown
> off by not seeing any devices under the virtual /dev dir, but that
> d
On 22 April 2006 06:26, David Christensen wrote:
> Oliver Vecernik wrote
>> I'd like to use the serial port from perl on my notebook.
>
> Try the Win32::SerialPort Perl module:
>
> http://members.aol.com/Bbirthisel/SerialPort.html
>
>
> I used it in the past and it worked great, but I had
Oliver Vecernik wrote
> I'd like to use the serial port from perl on my notebook.
Try the Win32::SerialPort Perl module:
http://members.aol.com/Bbirthisel/SerialPort.html
I used it in the past and it worked great, but I had to use ActiveState Perl
rather than Cygwin Perl.
HTH,
David
--
On Fri, 21 Apr 2006, Oliver Vecernik wrote:
> Hi,
>
> I'd like to use the serial port from perl on my notebook. This port is
> connected via an usb-adapter and referred as COM4: on Windows. I
> couldn't find any /dev/ttySx and I'm not sure if this is even supported.
> Is this possible under Cyg
27 matches
Mail list logo
