I agree with Matt. I think this is a fake issue, Perhaps Rob Hammerling needed to see you at work and plugged you in the socket. :) ( deep respect for Rob, just an innocent joke) One guy from Microchip was not attentive and changed the terms to sound good for his ears ( definitely his and not her, women are attentive). I really like hoci and hico. :0) People with a deep sense of humor here.
On Sat, Oct 22, 2022 at 9:56 PM Matthew Schinkel <[email protected]> wrote: > I think we're going the wrong way with this whole thing. > > I don't see how we are going to keep the new naming out of new files, and > I hope we aren't planning to send nasty emails to everyone that puts the > word slave in their lib/sample. That would be quite bad for Jallib. Instead > of us changing everything, maybe we should only change this where microchip > and other chip vendors have. > > The reason for the change should be "to match the vendors wording". Not to > remove it completely, because that can't be enforced due to freedom of > speech and will prevent some from adding files to Jallib. The person making > the library can name it as they please. > > Can we list all libraries containing the terms master/slave, then note > which are not matching the vendors wording? > > Since microchip is using host/client for SPI, I think we should keep > spi_master_hw.jal, but replace it's contents with only a few lines like: > include spi_host_hw > alias spi_master_hw is spi_host_hw > > Some vendors still refer to it as spi master/host and some as spi > slave/client. Therefore we should keep both a spi_host and a spi_master > library. > > Nobody owns Jallib, therefore nobody should enforce this new wording. Our > policy should be "try to use the vendors wording, but it's up to the > creator". > > I think this solution should work better for everyone. > > Peter, I don't think we'll be making any other changes to SPI naming, this > seems to be enough change for now. > > Matt. > > On Wednesday, October 12, 2022 at 1:36:57 PM UTC-4 Rob Hamerling wrote: > >> >> Hi guys, >> >> Like similar changes in other places, I see in the Microchip datasheets >> that the terms 'master' and 'slave' are being replaced by 'host' and >> 'client'. Seems a positive and desirable change to me. I would like to >> suggest to follow Microchip in this for Jallib. I'm afraid this is not a >> simple operation. It is not only about file names, but also related >> 'includes' in samples. But it will also have effects on existing user >> programs! What are your thoughts about this? >> >> Regards, Rob >> >> -- >> *Rob H*amerling, Vianen, NL >> > -- > You received this message because you are subscribed to the Google Groups > "jallib" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/jallib/3d96f421-f2a8-4536-8d29-9f1ddaccfaden%40googlegroups.com > <https://groups.google.com/d/msgid/jallib/3d96f421-f2a8-4536-8d29-9f1ddaccfaden%40googlegroups.com?utm_medium=email&utm_source=footer> > . > -- You received this message because you are subscribed to the Google Groups "jallib" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jallib/CAM%2Bj4qvWds4_KeZ%2Bu3SZmc9JVG_zfZ%3DOGuPqhXnOqbkjWQAukQ%40mail.gmail.com.
