On Fri, 16 May 2014 21:19:26 +0200 Henrik Nordström <[email protected]> wrote:
> fre 2014-05-16 klockan 17:04 +0100 skrev Ian Campbell: > > On Fri, 2014-05-16 at 18:05 +0300, Siarhei Siamashka wrote: > > > The FEL SPL entry point at the address 0x2000 starts execution > > > in the ARM mode. So we need to make sure that this particular > > > code is also compiled for the ARM mode. The rest of the SPL can > > > be compiled as Thumb2 and benefit from the code size reduction. > > > > What is the saving like? > > Why is there a need to hunt bytes in FEL? Well, I could also ask why is there a need to waste bytes? Especially considering that it's just a minor tweak. > We only need the DRAM initialization code in the FEL binary. Do we have some sort of a BROM USB driver running alongside with our SPL in the FEL mode? At least the stack base is set so that we don't have too much SRAM available for SPL. When doing experiments with the DRAM initialization code, I want to be able to do various things. For example, calculating the timings (converting nanoseconds to cycles) right in the SPL instead of having this stuff pre-computed and tabulated. Another example of a moderate SRAM space user is the DRAM calibration code for finding optimal parameters. And extra debugging code with verbose messages can also use up a lot of space. Most importantly, when we are running out of space, the code starts to misbehave in unpredictable ways. It is not like we are getting a a nice and helpful error message in this case. So what's wrong with just having more headroom? -- Best regards, Siarhei Siamashka -- You received this message because you are subscribed to the Google Groups "linux-sunxi" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
