hi Vasi, 2010/11/20 funlw65(Vasi) <[email protected]>
> Hi Matt, > > On Nov 20, 6:23 am, mattschinkel <[email protected]> wrote: > > Then how would your program know if the usb port is connected? > > > > That is easy, Windows is emitting some funny sounds and in Linux you > see that using dmesg and this way "I" know. Then, my firmware react on > PC software host... or, if is about sending data continuous, the start > is marked some how for the software host. > So, do you need another board that checks these sounds etc... in order the other to know the other can send/receive data ? :) More seriously, the PIC has to know when connection is available, in a programmatical way. I wasn't aware you had this problem. This is pretty weird, and knowing a (very) little about Albert's way of programming, I'm quite sure he did put this line for a specific purpose. As I said, there may be a problem while PC host is configuring the USB device. What does dmesg says (full log from pluging, configuring, comm, to unpluging) ? > > Toon reported that is not working and didn't worked also for me... how > you will react on that? I got stuck on the same loop and program > worked without that so I never used since then (it is an old issue, > what libs are you using now?). I think I remember Sebastien said > something about that... but I may be wrong. > I think this was about AT chars under Linux kernel < 2.6.32. Not related to the line status. Cheers, Seb -- You received this message because you are subscribed to the Google Groups "jallib" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/jallib?hl=en.
