Hi Matt, Would it be possible to separate the slip functions from the usart routines? This way you could use transport slip over serial_hw, serial_hw_int_cts, spi or any other stream and create a truely independant library.
Joep 2010/7/11 mattschinkel <[email protected]>: >> Looks great ! I have few more questions, sometimes nitpicking... :) > > Thanks for the nitpicking, please continue :) Thanks for your interest > on this. > >> In sample, some "10" could be replace with SLIP_MTU. This makes clear what's >> the meaning of this value and avoid duplication: > > ok > >> BTW, what "(partly SLIP encrypted)" means here ? > > Some of the data has changed, because it is a slip packet. I should be > more clear. 0xC0 changes to 0xDB 0xDC during transmission. 0xDB > changes to 0xDB 0xDD > > Matt. > > -- > 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. > > -- 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.
