If you correctly skip the HW init, you can try booting u-boot from u-boot ... (now, WD will hate me for bringing this up :-) ). It's possible, but unsupported operation. You might need to do some research on this matter :-)
I was thinking more along the lines of; Since I am testing a filesystem driver, to have a small test binary I can run and just feed a patch to (be it block device, or raw file) to test it can traverse, and read the contents.
But it would not be so bad to simulate that with some #ifdefs I guess.
What is the general patch acceptance around, I see ext4 wasn't accepted, what are the chances my patches would be?
Why wasn't ext4 accepted?
I have no idea. I found the patches back in Dec, and it is not in the repository. Although, I have patched it into my tree on github, it might help merging it into uboot. It does appear to work, whereas my zfs does not :)
CuBox>> zfsls usb 0:2 ** Bad partition - usb 0:2 ** CuBox>> zfsls usb 0:1 ** Bad partition - usb 0:1 ** CuBox>> zfsls usb 0:0 data abort pc : [<0063ea0c>] lr : [<0060eef0>] sp : 005ffe40 ip : 00000000 fp : 00000000 r10: 00000000 r9 : 00652a4c r8 : 005fffcc r7 : 00000000 r6 : 00000000 r5 : 007104b0 r4 : 006444a7 r3 : 00000000 r2 : 006f7b80 r1 : 00000000 r0 : ea000012 Flags: nZCv IRQs off FIQs off Mode SVC_32 Resetting CPU ...
Dang :)
Lund