From: Mateusz Kulikowski <mateusz.kulikowski@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] arm: at91: support for the Calao USB-A9263 board (based on AT91SAM9263)
Date: Mon, 28 Oct 2013 22:30:58 +0100 [thread overview]
Message-ID: <526ED792.6070203@gmail.com> (raw)
In-Reply-To: <526DEEAB.4090403@atmel.com>
Hi Bo Shen,
Thanks for the check, please see below.
On 28.10.2013 05:57, Bo Shen wrote:
> Hi Mateusz Kulikowski,
> Add Andreas in loop.
>
> On 10/28/2013 03:34, Mateusz Kulikowski wrote:
(...)
>> + /*
>> + * Disable pull-up on:
>> + * RXDV (PC25) => PHY normal mode (not Test mode)
>> + * ERX0 (PE25) => PHY ADDR0
>> + * ERX1 (PE26) => PHY ADDR1 => PHYADDR = 0x0
>> + *
>> + * PHY has internal pull-down
>> + */
>> + writel(1 << 25, &pio->pioc.pudr);
>> + writel((1 << 25) | (1 << 26), &pio->pioe.pudr);
>
> Use GPIO API instead of hard code.
Should I also update (in separate patch) at91sam9263ek board
(code is the same there, bad side is - I don't have that board to test)?
>> +
>> +#define CONFIG_SYS_TEXT_BASE 0x23f00000
>
> This address should be considered as u-boot is top down map, so if your system only 64MiB, there is only 1MiB left.
I don't understand something here:
- this address is hardcoded in AT91bootstrap (as well as image size - 0x31000),
- I can change it, but it will not boot on "stock" board - should we force
people to recompile AT91bootstrap if they want to use new U-Boot?
or
- Should I add low-level initialization to boot U-Boot from Dataflash
without AT91bootstrap (this is a bit more work)?
or
- There is another way I'm not aware of (perhaps relocate U-Boot in RAM)?
Best Regards,
Mateusz Kulikowski
next prev parent reply other threads:[~2013-10-28 21:30 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-27 19:34 [U-Boot] [PATCH] arm: at91: support for the Calao USB-A9263 board (based on AT91SAM9263) Mateusz Kulikowski
2013-10-28 4:57 ` Bo Shen
2013-10-28 21:30 ` Mateusz Kulikowski [this message]
2013-10-29 5:20 ` Heiko Schocher
2013-10-30 18:03 ` Mateusz Kulikowski
2013-10-29 5:24 ` Bo Shen
2013-10-29 5:54 ` Heiko Schocher
2013-10-30 18:17 ` Mateusz Kulikowski
2013-10-29 6:26 ` Andreas Bießmann
2013-10-29 6:35 ` Heiko Schocher
2013-10-29 9:12 ` Andreas Bießmann
2013-11-01 19:26 ` Mateusz Kulikowski
2013-11-04 9:36 ` Andreas Bießmann
2013-11-01 23:19 ` [U-Boot] [PATCH v2] " Mateusz Kulikowski
2013-11-11 11:03 ` Andreas Bießmann
2013-11-12 8:53 ` Heiko Schocher
2013-11-28 21:29 ` Mateusz Kulikowski
2013-11-29 11:31 ` Andreas Bießmann
2013-12-02 22:30 ` [U-Boot] [PATCH v3] " Mateusz Kulikowski
2013-12-09 12:39 ` [U-Boot] [U-Boot, " 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=526ED792.6070203@gmail.com \
--to=mateusz.kulikowski@gmail.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.