From: Jian Luo <Jian.Luo4@boschrexroth.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] u-boot: x86: interrupt mapping
Date: Wed, 20 Jul 2016 11:12:55 +0200 [thread overview]
Message-ID: <578F4097.1000604@boschrexroth.de> (raw)
In-Reply-To: <CAH9NwWd2am2-4PnZJ+-YVzkB=5kRsC43DE5wK3xEdXkseBt3fQ@mail.gmail.com>
Hi Christian,
On 20.07.2016 10:22, Christian Gmeiner wrote:
> Hi Jian,
>
>> I took some time to recall what I did by patching FSP:
>>
>> - search in every PE32 and TE image section for binary sequence
>> 81c9000100008908c6460e01
>> and change to
>> 81c9000102008908c6460e00
>>
> In the meantime I started by patching out every access to the uart bar, with
> the same result as I get with your patching strategy.
>
>> - then replace them in-place
>>
> So here is the next interesting problem. During fsp_init it looks like
> fsp copies itself
> to ram (IP 0xFFFD1C6C vs 0x3F5F64E1) and here it does a busy loop :(
I don't think it's a busy loop. This Bug?:
https://patchwork.ozlabs.org/patch/446555/
>
> At what place do you do the in-place patching? I hoped to do it at
> init_board setup.
I mean in UEFITool select the "PE32 image section", right click "Extract
body", do binary patching using your favorite hex editor, right click
"Replace body".
>> The difference can be better understand if disassemblies are compared, eg:
>> Disassembly of section .data:
>> @@ -3367,9 +3367,9 @@
>> 25fc: 05 00 05 00 00 add $0x500,%eax
>> 2601: 8b 08 mov (%eax),%ecx
>> 2603: 81 e1 ff ff f8 ff and $0xfff8ffff,%ecx
>> - 2609: 81 c9 00 01 00 00 or $0x100,%ecx
>> + 2609: 81 c9 00 01 02 00 or $0x20100,%ecx
>> What I did here is setting BAUDSEL to SYS_25MHz.
>>
>> 260f: 89 08 mov %ecx,(%eax)
>> - 2611: c6 46 0e 01 movb $0x1,0xe(%esi)
>> + 2611: c6 46 0e 00 movb $0x0,0xe(%esi)
>> Can't recall why I did this, maybe bypassing PLL altogether?
>>
>> 2615: c6 46 0f 00 movb $0x0,0xf(%esi)
>> 2619: c6 46 03 83 movb $0x83,0x3(%esi)
>> 261d: c6 46 01 00 movb $0x0,0x1(%esi)
>>
>> Since I don't rely on Topcliff UART for output, the baud rate recalculation
>> is all skipped.
>>
> The same here... I am using a pci fpga based uart.
Maybe you can try the fsp.bin I sent, to see if it runs
>
Since it's a bit off-topic, should we exchange information w/o ccing the
list?
Best regards,
*Jian Luo
DC-IA/EAH2*
Tel. +49(9352)18-4266
*Be**QIK
*
prev parent reply other threads:[~2016-07-20 9:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAH9NwWeT41sHTRmXFcKf5jR_wvGSK5BN0oxYAXa2S6E0teLX+w@mail.gmail.com>
[not found] ` <CAEUhbmVwOpKHB-JSy6p9BsS2fmj1pzh6twRN=D_JpHKjHWpCYA@mail.gmail.com>
[not found] ` <CAH9NwWf5Ssff2rwUXZzr8tZLjtOW5JH4tJZEqoegzk0JJZ7wYQ@mail.gmail.com>
[not found] ` <CAEUhbmXUQbn1rqMQZhE_3xpJ+qgtJTYcGA2BENd8nXHZ_xwozA@mail.gmail.com>
[not found] ` <CAH9NwWeqimNtkdDAPHb4tXnw5zGPU3Bfb1gJdhpMdPFjzHd7BQ@mail.gmail.com>
[not found] ` <CAEUhbmXYfzoYQROmhrZga=dMTxxn-wrad2NnTcFSoov5cuQgaw@mail.gmail.com>
[not found] ` <CAH9NwWdQj3voXzyrncr9YNDKZ6hqF_iemHd1MA3kxkuWS0A03w@mail.gmail.com>
2016-07-19 4:17 ` [U-Boot] u-boot: x86: interrupt mapping Bin Meng
2016-07-19 6:02 ` Christian Gmeiner
2016-07-19 8:03 ` Jian Luo
2016-07-19 8:10 ` Bin Meng
2016-07-19 8:27 ` Jian Luo
2016-07-19 15:21 ` Christian Gmeiner
2016-07-19 16:44 ` Jian Luo
2016-07-20 8:22 ` Christian Gmeiner
2016-07-20 9:12 ` Jian Luo [this message]
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=578F4097.1000604@boschrexroth.de \
--to=jian.luo4@boschrexroth.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