Xiaofan Chen wrote:
> "C:\embedinc\com>pic_read -SIO 1 -hex read.hex
> fixme:comm:GetCommProperties (0x44 0x7789ed50 )
> fixme:comm:SetupComm insize 2048 outsize 2048 unimplemented stub
>
> ...
>
> Therefore I think Wine's serial support is not so good.

Yeah, it's a good clue when it says "fix me".

I'm a bit surprised that it's complaining about a call to GetCommProperties,
since that's pretty main stream.  The SetupComm call is a bit more unusual
in that I specifically try to set the input and output buffers to at least
2K bytes.  This isn't actually required by the PICPRG software, but is done
deep down in the serial line support of my OS interface layer.  A while back
I had problems on some systems that decided to provide only very small
serial buffers.  I then changed my low level Windows interface to always
request 2Kbytes.  There is a way for Windows to tell the app to stick it,
and my software can handle that.  That would sound like an easy expedient
for Wine.  It can use a fixed size and just refuse requests to change it.


******************************************************************
Embed Inc, Littleton Massachusetts, (978) 742-9014.  #1 PIC
consultant in 2004 program year.  http://www.embedinc.com/products
-- 
http://www.piclist.com PIC/SX FAQ & list archive
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist