From mboxrd@z Thu Jan 1 00:00:00 1970 From: Marek Vasut Date: Thu, 20 Sep 2012 00:56:19 +0200 Subject: [U-Boot] [PATCH 1/6] h2200: Add support for iPAQ h2200 In-Reply-To: <505A4C8B.2010605@gmail.com> References: <1348083538-16123-1-git-send-email-luk0104@gmail.com> <201209200042.55201.marex@denx.de> <505A4C8B.2010605@gmail.com> Message-ID: <201209200056.19950.marex@denx.de> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de Dear ?ukasz Da?ek, > On 20.09.2012 00:42, Marek Vasut wrote: > > Dear ?ukasz Da?ek, > > > >> On 20.09.2012 00:01, Marek Vasut wrote: > >>> Yes, GCC/GAS generate 0xeafffffe (b 0x9098). > >>> > >>> Can you tell me why? Can I left .word? > >>> Why is the jump offset 0x9098 ? > >> > >> I figured out that 0xeafffffe is a loop (b -4) > > > > ldr pc, pc, #-4 > > > >> but I don't know > >> why toolchain generate b -4 instead of b 0x1000 and I don't > >> know how to fix it (without .word). > > > > I don't follow, sorry. How did you even get to 0xeafffffe ? > > My point is that GCC/GAS generate 0xeafffffe instead of 0xea0003fe when > I use 'b 0x1000'. How did you get to 0x1000 ? > That's why I use directive .word 0xea0003fe Check some arm instruction quick ref for what 0xea0003fe really is and if it really is necessary or anything else work just fine as well. > instead of > asm instruction 'b 0x1000'. But I don't know that: Can I leave that .word > directive or I can not. > > Another question: I asked in cover letter question about tools. Can I add > them in h2200 directory or should I put them somwhere else? I didn't receive the cover letter. > ?ukasz Da?ek Best regards, Marek Vasut