Thank You for your continued support and contributions!
Isn't it good advice to do that anyway?
IIRC from the discussions on IRC, a lot of ARM targets currently use long calls which makes the code slower and bigger. I think one of the most important things we could do with the MMU is to map memory regions such that they are close enough to each other to use short calls, thereby shrinking the code and speeding it up (slightly).
And , of course now that Funman has mp3 and ogg playing so nicely for me(thanks a ton by the way) how do I stay motivated
I'm spinning my wheels working on the mmu but plugging away. I can tell you a whole bunch of things that don't work and not one that does. I think the mmu is actually functioning as several people have reported success mapping memory regions to different locations. Whenever I try to enable caching however I get a mirror image lcd screen. I have tried all kinds of combinations of invalidate_cpucache, clean_dcache, clean_dcache_range etc. to no avail.In my flailing away at the problem I did come up with several questions though:It appears we have leftover room in iram, is there a reason not to use it for the stack?Do we really need the mmu functioning in the bootloader? It seems to me it overcomplicates things.And , of course now that Funman has mp3 and ogg playing so nicely for me(thanks a ton by the way) how do I stay motivated
Page created in 0.105 seconds with 17 queries.