Hi, >-----Original Message----- >From: meego-dev-boun...@meego.com >[mailto:meego-dev-boun...@meego.com] On Behalf Of ext Patrick Ohly >Sent: Monday, January 31, 2011 6:01 PM >To: Tony >Cc: Kavuri Sateesh (Nokia-MS/Bangalore); Duggirala Karthik.2 >(Nokia-MS/Helsinki); meego-dev@meego.com; >tuomas.kat...@ixonos.com; Aggarwal Amit.5 >(Nokia-MS/Bangalore); kalle.aalto...@sasken.com; mhuna...@gmail.com >Subject: Re: [MeeGo-dev] Buteo MTP + gadgetfs
>The trouble is that the kernel code that supports reads and >writes for gadgetfs endpoints doesn't support non-blocking I/O >properly. The select() notification and associated >QSocketNotifier fires immediately and continuously even >without data ready to read, and a read() on the file-desciptor >blocks waiting for data even with O_NONBLOCK set. This is strange. If the fd is not set to O_NONBLOCK, then of course IO on it would block, but does that mean that if one poll()'s or does a select() on that fd, they would get notified even if there's no data to be read? This must be happening due to a bug in functionfs. >Best Regards, Patrick Ohly > >The content of this message is my personal opinion only and >although I am an employee of Intel, the statements I make here >in no way represent Intel's position on the issue, nor am I >authorized to speak on behalf of Intel on this matter. Regards, Deepak _______________________________________________ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev
