That's actually within "slow but usable" range, if we don't use swap!2.16MiB/s
That's actually within "slow but usable" range, if we don't use swap!2.16MiB/s
What does weston do anywayNot to alarm anyone but I got a rootfs to successfully compile. It hangs on boot, but it compiled. God, i'm SO CLOSE!
(It had been updated to use the newest kernel and had the untested SD support. It also had weston removed because weston was being a dick to buildroot.)
https://en.wikipedia.org/wiki/Wayland_(display_server_protocol)#WestonWhat does weston do anyway
I can test on N2dsXLSo it turns out it's actually a 50/50 split between the current crash being Linux's fault or my 3DS' fault. It fails when looking at my 3DS' NAND to determine what its version and whatnot are, so I need a few others to try builds to see if they boot.
I can also test it on my N3DS XLSo it turns out it's actually a 50/50 split between the current crash being Linux's fault or my 3DS' fault. It fails when looking at my 3DS' NAND to determine what its version and whatnot are, so I need a few others to try builds to see if they boot.
I can test on N2dsXL
I can also test it on my N3DS XL
I know that, and I took that into account. It is a good benchmark for what we're doing, since we'll be reading and executing from SD while writing to swap on SD as well.FBI is not a good benchmark. It gives you approximately half of the real write speed since it has to read the CIA file while writing to files on the same SD card.
EDIT: Never mind about the loader firm question. Running it now on New 2DS XL I'm stuck here just after "[11.176000] nintendo3ds_mmc: major: 254" with just a blinking line.https://drive.google.com/open?id=1wvqLuPXpeOlFGXh7Kzv-zGmA8IVxGM4x
Device Tree boot is enabled, it should enable the proper features for each model. Send me a shot of where it hangs, if it does. Thanks, guys!
Same for me.EDIT: Never mind about the loader firm question. Running it now on New 2DS XL I'm stuck here just after "[11.176000] nintendo3ds_mmc: major: 254" with just a blinking line.
I can test anything else you want me to test if your okay with itYeah, that's what I'm experiencing. It's a driver issue, then. I'll get to work.
I can test anything else you want me to test if your okay with it
I'll post tester12 builds here occasionally, so anyone wanting to try them can and can report back freely. I appreciate it!
Speaking of, here's a new build: https://drive.google.com/open?id=1nRDD6Lcr1xJFIAxvVWlgWfGDB6RytsHS
It works long enough to login on my 3DS, but I've seemingly broken the network loopback, so there's a new error.
Yeah, that's the one I broke. It also seems I've managed to bypass the NAND error by breaking the SD/MMC driver ENTIRELY.I think I have the error but I can login.
Starting network: ip: can't find device 'lo'
FAIL
It'd be a good idea to do a full SysNAND backup too, as the driver handles interfacing with that too.Im doing a backup of my sd that's long overdue, I'll edit this post with my results soon
Ouch. I'll do a nand backup as wellYeah, that's the one I broke. It also seems I've managed to bypass the NAND error by breaking the SD/MMC driver ENTIRELY.
I would be careful using the SD card as swap. The Raspberry Pi is a great example of what can happen. It apparently smokes brand new (micro)SD cards within months.I know that, and I took that into account. It is a good benchmark for what we're doing, since we'll be reading and executing from SD while writing to swap on SD as well.