Hi, did anyone have any objections on what I had suggested in my previous message?
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 This way it will be backwards compatible, and we'll be able to slowly migrate to the new spi_host_hw.jal library. If no objections I'll go ahead with this. Matt. On Friday, October 28, 2022 at 4:21:20 AM UTC-4 [email protected] wrote: > Hoi Rob > > Of course Arduino had to solve the same problem sooner or later. > I understand very well that IIC also use M/S. > Thatβs why I going to help you if you will. > > Greetings Peter > > > > Mijn spreuk: liever kort en goed dan te uitgebreid. > > Op 27 okt. 2022 om 20:54 heeft Rob CJ <[email protected]> het volgende > geschreven: > > ο»Ώ > > Hi Peter, > > And in addition. This is also valid for IIC π. > > Kind regards, > > Rob > > ------------------------------ > *Van:* Rob CJ <[email protected]> > *Verzonden:* donderdag 27 oktober 2022 20:53 > *Aan:* [email protected] <[email protected]> > *Onderwerp:* Re: [jallib] Re: exit of master/slave? > > Hi Peter, > > The use of MISO and MOSI does not solve this for Arduino since it stands > for Master In Slave Out and Master Out Slave In π. > > So Host and Client should be the terminolgy (until these termis become a > problem ....) > > We are still undecided if we should do this or not. As far as I see it now > we have several options: > > 1. Do nothing. Wait until some JAL user has problems with the > terminology. > 2. Remove Master Slave from all libraries and sample files and change > them to host/client. This will break current projects for JAL users that > use SPI. > 3. Copy the libraries with master/slave to new libraries with host and > client. Adapt all sample files to that and add a warning to the > master/slave library that it will be deprecated (not determined when that > will happen maybe when somebody has any issues with them) but also do not > maintain these libraries anymore (no bug fixes). > > Option 3 does not break anything (yet). And of course option 1 also > doesn't. > > Kind regards, > > Rob > > > ------------------------------ > *Van:* [email protected] <[email protected]> namens ZetWeeh < > [email protected]> > *Verzonden:* dinsdag 25 oktober 2022 23:56 > *Aan:* [email protected] <[email protected]> > *Onderwerp:* RE: [jallib] Re: exit of master/slave? > > > I read the reactions on my mail about hico/hoci: from adoration of women > to freedom of speech.π > > > > I believe Microchip is very smart: don't wait till critics begin about > master/slave: > > but change it before. π€ > > Jal is going also from master/slave to host/client. When you do it: do it > good. > > Raspberry, Arduino (and so on) they all use MOSI/MISO and that has a > reason. > > > > Rob H. started this discussion also with a reason. Master/slave is an issue > > in the world of this moment. Jal is part of this constant changing world. > > And it is not important what a JAL-maker/volunteer thinks! > > The future of JAL is important. > > > > All kind of volunteers worked hard for JAL and it's not the intention that > it's becoming a dull > > old-fashioned IDE. > > > > It's to easy to say: it's a lot of work for Rob J. > > Rob J. has already made suggestions of changes. If he works it out he can > send me the names of samples and I'll change them. > > In this way all changes remains equal. > > Together with new libs JAL remains up-to-date. > > > > Peter π > > > > PS. Who will help too? > > *Van: *Rob CJ > *Verzonden: *zondag 23 oktober 2022 10:22 > *Aan: *[email protected] > *Onderwerp: *Re: [jallib] Re: exit of master/slave? > > > > Hi all, > > > > Agree. We coule makt it something gradual. > > > > I started with the ili9341.jal library. > > > > -- Define the interface alias for the ILI9341. > > alias ili9341_spi_host is spi_master_hw > > > > > > Kind regards, > > > > Rob > > > > *Van:* [email protected] <[email protected]> namens vsurducan > <[email protected]> > *Verzonden:* zondag 23 oktober 2022 08:54 > *Aan:* [email protected] <[email protected]> > *Onderwerp:* Re: [jallib] Re: exit of master/slave? > > > > 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 > > <https://groups.google.com/d/msgid/jallib/CAM%2Bj4qvWds4_KeZ%2Bu3SZmc9JVG_zfZ%3DOGuPqhXnOqbkjWQAukQ%40mail.gmail.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/GVXP195MB1637C15DB186920B5455F474E62F9%40GVXP195MB1637.EURP195.PROD.OUTLOOK.COM > > <https://groups.google.com/d/msgid/jallib/GVXP195MB1637C15DB186920B5455F474E62F9%40GVXP195MB1637.EURP195.PROD.OUTLOOK.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/B1444288-C8C7-4614-9FE2-267FA66AB8E6%40hxcore.ol > > <https://groups.google.com/d/msgid/jallib/B1444288-C8C7-4614-9FE2-267FA66AB8E6%40hxcore.ol?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/GVXP195MB16375053DD6CE9A92191CF66E6339%40GVXP195MB1637.EURP195.PROD.OUTLOOK.COM > > <https://groups.google.com/d/msgid/jallib/GVXP195MB16375053DD6CE9A92191CF66E6339%40GVXP195MB1637.EURP195.PROD.OUTLOOK.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/267e0a81-ed80-430e-9268-2ca201516ff2n%40googlegroups.com.
