From: Marek Vasut <marex@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 1/6] h2200: Add support for iPAQ h2200
Date: Thu, 20 Sep 2012 00:56:19 +0200 [thread overview]
Message-ID: <201209200056.19950.marex@denx.de> (raw)
In-Reply-To: <505A4C8B.2010605@gmail.com>
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
next prev parent reply other threads:[~2012-09-19 22:56 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-19 19:38 [U-Boot] [PATCH 0/6] iPAQ h2200 support Łukasz Dałek
2012-09-19 19:38 ` [U-Boot] [PATCH 1/6] h2200: Add support for iPAQ h2200 Łukasz Dałek
2012-09-19 21:02 ` Marek Vasut
[not found] ` <505A3B2B.6080907@gmail.com>
2012-09-19 21:43 ` Marek Vasut
2012-09-19 21:54 ` Łukasz Dałek
2012-09-19 22:01 ` Marek Vasut
2012-09-19 22:16 ` Łukasz Dałek
2012-09-19 22:42 ` Marek Vasut
2012-09-19 22:51 ` Łukasz Dałek
2012-09-19 22:56 ` Marek Vasut [this message]
2012-09-19 23:07 ` Łukasz Dałek
2012-09-19 23:09 ` Marek Vasut
2012-09-19 23:20 ` Łukasz Dałek
2012-09-19 23:25 ` Marek Vasut
2012-09-19 23:36 ` Łukasz Dałek
2012-09-19 23:43 ` Marek Vasut
2012-09-19 23:51 ` Łukasz Dałek
2012-09-20 0:06 ` Marek Vasut
2012-09-20 5:49 ` Joe Hershberger
2012-09-20 12:14 ` Marek Vasut
2012-09-22 17:02 ` Łukasz Dałek
2012-09-22 17:04 ` Marek Vasut
2012-09-22 17:16 ` Łukasz Dałek
2012-09-22 18:00 ` Marek Vasut
2012-09-22 18:07 ` Łukasz Dałek
2012-09-22 18:21 ` Marek Vasut
2012-09-22 18:34 ` Łukasz Dałek
2012-09-22 18:37 ` Marek Vasut
2012-09-22 18:47 ` Łukasz Dałek
2012-09-19 19:38 ` [U-Boot] [PATCH 2/6] pxa25x: Add USB Ethernet driver Łukasz Dałek
2012-09-19 21:03 ` Marek Vasut
[not found] ` <505A386D.7080302@gmail.com>
2012-09-19 21:39 ` Marek Vasut
2012-09-19 19:38 ` [U-Boot] [PATCH 3/6] pxa: Add some stuff to examine cpu model and rev Łukasz Dałek
2012-09-19 21:04 ` Marek Vasut
2012-09-19 19:38 ` [U-Boot] [PATCH 4/6] usbether: Fixed bug when using with PXA25X chips Łukasz Dałek
2012-09-19 19:38 ` [U-Boot] [PATCH 5/6] usbether: Define CONFIG_USB_ETH_{CDC,SUBSET} Łukasz Dałek
2012-09-19 19:38 ` [U-Boot] [PATCH 6/6] usbether: Removed DEV_CONFIG_{CDC,SUBSET} Łukasz Dałek
2012-09-19 23:10 ` [U-Boot] [PATCH 0/6] iPAQ h2200 support Marek Vasut
2012-09-20 6:36 ` Andreas Bießmann
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=201209200056.19950.marex@denx.de \
--to=marex@denx.de \
--cc=u-boot@lists.denx.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox