crasbe
crasbe
So this was quite a rabbit hole. No matter what I did I could not reproduce the issue... It turns out that Linux Mint had an old version of codespell....
The last PR adds a new test for the mtd_spi_nor driver which tests the security features. Contrary to what I wrote in the first post, you can trigger the P_FAIL...
@benpicco You reviewed the original PR, could you take a quick look at this to give me some guidance on the previous question? You don't have to review this PR...
I implemented the Pseudomodule solution and IMO it is way more elegant than the original idea and scales a lot better. One thing that became clear is that the ISSI...
I think this PR is already quite extensive and beyond the originally intended scope, so I would like to postpone adding the timeout tasks for now to a separate PR.
Is there anything I can do to help with the review process? Perhaps split off the test program (minus the security tests) to a seperate PR? I could send out...
I don't really understand why the tests fail now, the changes I did are unrelated to the failures (all except for the busy_wait_us(1000000) in tests/drivers/mtd_spi_nor/main.c). It would appear that most...
@maribu I absolutely agree with you. As I said, the delay was just a little help for me to catch the actual test output. However, considering that no other tests...
> @crasbe: do you want to tackle the missing timeouts (waiting on status change) (from your TODOs)? want to prepare the interfaces to be able to fail? ignore them (for...
This took a bit longer than I anticipated to get back to it, but other things happened. I think we have an elegant solution now. The code introduces a new...