On 2024-08-29 11:57:49, Marco Casaroli wrote: > > > 4. How should I test the peripherals? I don't have all the LCD displays > > and > > > the other accessories supported by RP2040 port. Should I: > > > > > > a. keep the peripherals code for LCD, etc and hope that it will work > > > (explain in the documentation that it is not tested) > > > b. just add the minimum code without those peripherals support > > > c. buy the missing stuff or find other people to test it before I open > > the > > > PR > > Best is C of course :) but noone will expect from you to buy stuff to write > > the drivers - you do it only if you want to support project using not only > > your time but also money. So go B. It's better to not have things than have > > them half cooked in buggy state (I'm looking at you zephyr). > > > > I will remove the code for stuff I cannot test right now. Not sure if full removal is good approach here. You did put some work into it. It would be shame to waste it. I think I would just go on and create separate pull request for them. You can also semi test things with logic analyzer. SPI can be tested that way. With SPI you can also connect MOSI to MISO and test communication that way. Once you confirm driver with bridging or logic analyzer you can create driver marked as EXPERIMENTAL. This will be a good indication that driver is somewhat working, but noone should expect production quality code in there.
-- .-----------------.-------------------.----------------------.-----------------. | Michal Lyszczek | Embedded C, Linux | Company Address | .-. opensource | | +48 727 564 419 | Software Engineer | Akacjowa 10a; 55-330 | oo| supporter | | https://bofc.pl `----.--------------: Brzezinka Sredzka PL | /`'\ & | | GPG FF1EBFE7E3A974B1 | Bits of Code | NIP: 813 349 58 78 |(\_;/) programer | `----------------------^--------------^----------------------^-----------------'
signature.asc
Description: PGP signature
