OK, I see what you mean and will see what I can do. And indeed, SPI is on my "ligne de mire" as I need to use MSSP2 to access SD-card on Jaluino Bee board, and needs to remap SPI pins from MSSP2 module (PPS & remappable pins really are "funny").
Cheers, Seb 2011/4/15 mattschinkel <[email protected]> > > I don't understand, if there's a 2nd library, what is the purpose of > having > > constant ? > > I am just thinking for the future, if pointers get implemented someone > would only need to include one of the libs, even if they want to use > both rx/tx > > > > Do both ports use alike registers? > > > > Yes, pretty much like. In order to make my 2nd lib working, I scan the > code > > and just replace registers with the same one including the number "2" :) > > Again, this makes it easy for pointers which is why I asked. But I > guess this can be implemented later on :) > > Maybe you can put aliases at the top of each serial library so rest of > the code in both libs are the same. This will make it easier to > replace code. If one lib is changed, we will have to update the other. > How easy is it to replace all registers with "2" if part of the lib > code is changed? > > Whatever you decide for this lib should be the same for SPI & I2C. > Device files should alias TX with TX1 (same as SPI) > > It's all up to you Seb, these are only suggestions. > > 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.
