@PulkoMandy I have made corrections to the proposal
And are there any other changes to be made in the proposal.?
I have tried to include major key points from the mentioned documents in page no 1.
Hey @PulkoMandy I have made changes as suggested in the feedback. I primarily have used eMMC specification, SD specification. So I have mentioned the respective sections as references.
Are there any additional changes that I need to make.? I tried including all the major points hopefully it is not too lengthy.
I have like a general doubt, in driver development or atleast specific to my patch, if at all we write correct logic we cant directly merge it right? We need to first validate the behaviour on hardware, I dont have any flexible hawdware where I run image and mimic behaviour and validate it and you cant do this on QEMU also right.?
https://review.haiku-os.org/c/haiku/+/10523
I think it’s quite complete now. I just added a comment in the intro section about treating GSoC as full-time employment and wether we should set up an extended length project lasting until november. Tell us if that would help since you seem to have a heavy schedule for the summer months.
If you have time now, rather than working on the proposal I think you could work more on the code contributions (getting your first patches ready and perhaps adding more).
You can’t validate your changes on every possible hardware setup anyways.
So, test as much as you can with QEMU, mention that in the commit message or in review comments so we know how far this has been tested. If you can, test both SD and eMMC, to make sure SD card support isn’t broken by your changes at least on QEMU.
The code will then be merged after all review is done. If someone hits a problem after that, they’ll open a ticket on Trac and we’ll assign it to you. Merged code only gets into the nightly builds, and people using those are doing so to test the latest features and identify problems early (people who want some peace of mind and less problems should use the latest beta release instead).
Thank you, I will update the proposal according to the latest comment .
With regard to to the patches I will finish the ongoing one and start focusing on the initialisation sequence of eMMC. I will try testing them QEMU , update the test results on commit message and share the screenshot of syslogs here
@PulkoMandy I had a small query that I have commented on the proposal, can you please guide me on that.
Hey everybody, I am finding it difficult to test changes on the qemu. Here are the ways I tried to do.
- After making any change I am trying to build the entire , but this is taking a lot of time on my computer.
- I tried loading the updated driver into an already downloaded image, but I couldn’t find proper resources or steps to do this correctly.
Are there any other ways I can test my changes on qemu
Hi did you try the following?
For the first build:
jam -q -j4 @nightly-raw
Then to update one target:
jam -q -j4 @nightly-raw update sdhci
Has there been any updates on this Does the EMMC work finally?