:D Yup the timers too. That's why I would like to keep that piece of code as it is and move only the serial port handling elsewhere (a different thread I)
--- On Thu, 10/21/10, Holger Hans Peter Freyther holger@freyther.de wrote:
From: Holger Hans Peter Freyther holger@freyther.de Subject: Re: osmocom on windows To: baseband-devel@lists.osmocom.org Date: Thursday, October 21, 2010, 8:09 PM
On 10/21/2010 07:00 PM, eisencah eisenach wrote:
Here's another one. Regarding the select mechanism (the one in select.c). Other then the serial port and sockets is anything else registered there? Cause I
would like to keep sockets for communication after all (but the select
function will not work on windows for serial ports handles). So I would use a different mechanism only for serial port scheduling. Cheers, Mihai.
well.. we handle the timers with it too.
Another thread is possible, but you could also do a non-blocking read of the serial port, when Select call timed out. If nothing, you'll return back to the WSASelect() and the whole process repeats. This means you do serial port handling on the time-out of the WSASelect() call.
This way you omit synchronization between threads, but if you're familiar with multithreading, go ahead :)
On 21-10-2010 19:48, eisencah eisenach wrote:
:D Yup the timers too. That's why I would like to keep that piece of code as it is and move only the serial port handling elsewhere (a different thread I)
--- On Thu, 10/21/10, Holger Hans Peter Freytherholger@freyther.de wrote:
From: Holger Hans Peter Freytherholger@freyther.de Subject: Re: osmocom on windows To: baseband-devel@lists.osmocom.org Date: Thursday, October 21, 2010, 8:09 PM
On 10/21/2010 07:00 PM, eisencah eisenach wrote:
Here's another one. Regarding the select mechanism (the one in select.c). Other then the serial port and sockets is anything else registered there? Cause I
would like to keep sockets for communication after all (but the select
function will not work on windows for serial ports handles). So I would use a different mechanism only for serial port scheduling. Cheers, Mihai.
well.. we handle the timers with it too.
Hello everybody. Managed to compile the osmocom program under windows. Could anyone send me the image for the "Hello word" program so I could try to download it into the phone (haven't got to the part where I compile the firmware bit I would want to see osmocom work). Cheers, Mihai.
--- On Fri, 10/22/10, Nordin bouchtaoui@gmail.com wrote:
From: Nordin bouchtaoui@gmail.com Subject: Re: osmocom on windows To: baseband-devel@lists.osmocom.org Date: Friday, October 22, 2010, 10:39 AM
Another thread is possible, but you could also do a non-blocking read of the serial port, when Select call timed out. If nothing, you'll return back to the WSASelect() and the whole process repeats. This means you do serial port handling on the time-out of the WSASelect() call.
This way you omit synchronization between threads, but if you're familiar with multithreading, go ahead :)
On 21-10-2010 19:48, eisencah eisenach wrote:
:D Yup the timers too. That's why I would like to keep that piece of code as it is and move only the serial port handling elsewhere (a different thread I)
--- On Thu, 10/21/10, Holger Hans Peter Freytherholger@freyther.de wrote:
From: Holger Hans Peter Freytherholger@freyther.de Subject: Re: osmocom on windows To: baseband-devel@lists.osmocom.org Date: Thursday, October 21, 2010, 8:09 PM
On 10/21/2010 07:00 PM, eisencah eisenach wrote:
Here's another one. Regarding the select mechanism (the one in select.c). Other then the serial port and sockets is anything else registered there? Cause I
would like to keep sockets for communication after all (but the select
function will not work on windows for serial ports handles). So I would use a different mechanism only for serial port scheduling. Cheers, Mihai.
well.. we handle the timers with it too.
baseband-devel@lists.osmocom.org
-
eisencah eisenach -
Nordin