Lines Matching refs:we
34 ;; since etrax actually starts at address 2 when booting from flash, we
35 ;; put a nop (2 bytes) here first so we dont accidentally skip the di
46 ;; we cannot do very much! See arch/cris/README.mm
48 ;; Notice that since we're potentially running at 0x00 or 0x40 right now,
49 ;; we will get a fault as soon as we enable the MMU if we dont
52 ;; Due to a bug in Etrax-100 LX version 1 we need to map the memory
54 ;; an address. Though we can check the version register for
56 ;; be variables, so we don't. The drawback is that you can "only" map
129 ;; Now we need to sort out the segments and their locations in RAM or
136 ;; If we boot this from Flash, we want to keep the ROM filesystem in
137 ;; the flash, we want to copy the text and need to copy the data to DRAM.
138 ;; But if we boot from DRAM, we need to move the ROMFS image
142 ;; In both cases, we start in un-cached mode, and need to jump into a
143 ;; cached PC after we're done fiddling around with the segments.
148 ;; Check if we start from DRAM or FLASH by testing PC
162 ;; Put this in a suitable section where we can reclaim storage
181 ;; We need to initialze DRAM registers before we start using the DRAM
200 ;; DRAM and we never get here in the first place :))
215 ;; we don't do anything than read some bytes here.
252 ;; garbage but we do sanity checks on it, the chance that it points
279 ;; Notice that we check for cramfs magic value - which is
280 ;; the "rom fs" we'll possibly use in 2.4 if not JFFS (which does
309 lsrq 1, $r2 ; size is in bytes, we copy words