Experimental Physics and Industrial Control System
|
On Sep 30, 2015, at 10:31 AM, Mark Rivers <[email protected]> wrote:
The code in question is in the Windows-specific driver file (drvAsynSerialPortWin32.c), so it is already Windows-specific. We are not adding OS-specific code to a generic driver.
Oops — I forgot that windows didn’t use the Posix termios code.
I don’t like users having to put 6 backslash characters into the device name, where everywhere else in Windows they just say COM10. I agree with Peter’s suggestion that we don’t need a special case for COM1-COM9. I propose the following: - If the device name passed to drvAsynSerialPortConfigure starts with ‘\’ then assume the user has used a device name, and use it directly. - If the device name does not begin with ‘\’ then prepend “\\.\”.
That sounds ideal.
|
- Replies:
- Re: Serial port COM10: not work? Torsten Bögershausen
- References:
- Serial port COM10: not work? Heesterman, Peter J
- Re: Serial port COM10: not work? Jack
- RE: Serial port COM10: not work? Mark Rivers
- Re: Serial port COM10: not work? Eric Norum
- RE: Serial port COM10: not work? Mark Rivers
- Navigate by Date:
- Prev:
RE: Serial port COM10: not work? Mark Rivers
- Next:
RE: New sequencer releases Mark Rivers
- Index:
1994
1995
1996
1997
1998
1999
2000
2001
2002
2003
2004
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
<2015>
2016
2017
2018
2019
2020
2021
2022
2023
2024
- Navigate by Thread:
- Prev:
RE: Serial port COM10: not work? Mark Rivers
- Next:
Re: Serial port COM10: not work? Torsten Bögershausen
- Index:
1994
1995
1996
1997
1998
1999
2000
2001
2002
2003
2004
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
<2015>
2016
2017
2018
2019
2020
2021
2022
2023
2024
|
ANJ, 16 Dec 2015 |
·
Home
·
News
·
About
·
Base
·
Modules
·
Extensions
·
Distributions
·
Download
·
·
Search
·
EPICS V4
·
IRMIS
·
Talk
·
Bugs
·
Documents
·
Links
·
Licensing
·
|