From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 0/4] Add support for stm32f429-discovery board
Date: Thu, 26 Mar 2015 10:07:55 -0400 [thread overview]
Message-ID: <20150326140755.GA32541@bill-the-cat> (raw)
In-Reply-To: <55140DE5.5080504@wp.pl>
On Thu, Mar 26, 2015 at 02:47:17PM +0100, Kamil Lulko wrote:
> On 25/03/15 17:58, Tom Rini wrote:
> >On Wed, Mar 25, 2015 at 01:07:47PM +0900, Chanwoo Choi wrote:
> >>Hi Kamil,
> >>
> >>I tested this patch-set in STM32 Discovery board. After applied this
> >>patch-set on latest u-boot, I could not see the normal u-boot log. I
> >>saw broken console log. I used the USART1 port (pa9, pa10 gpio pin).
> >>
> >>Could you give me a tip to resolve this issue?
> >I bet this needs changes similar to b81bdf6 as that was a similar
> >problem I believe. In short, DM needs to be enabled now.
> >
> >>Best Regards,
> >>Chanwoo Choi
> >>
> >>2015? 3? 1? ???, Kamil Lulko<rev13@wp.pl>?? ??? ???:
>
> I have tested this patch set again with 2015.04-rc4-gf643d92 and
> serial works without any problems.
>
> Chanwoo, you mention STM32 Discovery board - this patch set supports
> only STM32F429 Discovery (it should work on SDRAM-less boards but
> not without modifications). Other than that the only thing I can
> think of is configuration of the UART<>USB converter.
>
> Tom, does this mean changes are required for this patchset to be
> accepted? I have more things queued up (like moving some of SDRAM
> configuration bits out of the board code or LCD display support) but
> I would prefer to have some kind of assurance that this will not go
> into /dev/null eventually :)
Right now the patches don't apply cleanly due to 68145d4c but it's an
easy enough fixup by hand. I plan to apply the current series after the
2015.04 release. If you want to start posting stuff that depends on the
initial series being applied that's fine. Thanks!
--
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: Digital signature
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20150326/c7974c6a/attachment.sig>
prev parent reply other threads:[~2015-03-26 14:07 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-01 11:44 [U-Boot] [PATCH 0/4] Add support for stm32f429-discovery board Kamil Lulko
2015-03-01 11:44 ` [U-Boot] [PATCH 1/4] ARM: Add ARMv7-M support Kamil Lulko
2015-03-05 15:32 ` Tom Rini
2015-03-30 22:06 ` Andreas Färber
2015-04-01 0:55 ` Tom Rini
2015-04-23 13:14 ` [U-Boot] [U-Boot,1/4] " Tom Rini
2015-03-01 11:44 ` [U-Boot] [PATCH 2/4] ARMv7M: Add STM32F4 support Kamil Lulko
2015-03-05 15:34 ` Tom Rini
2015-04-23 13:14 ` [U-Boot] [U-Boot,2/4] " Tom Rini
2015-03-01 11:44 ` [U-Boot] [PATCH 3/4] stm32f4: Add serial driver Kamil Lulko
2015-03-05 15:34 ` Tom Rini
2015-04-23 13:14 ` [U-Boot] [U-Boot,3/4] " Tom Rini
2015-03-01 11:44 ` [U-Boot] [PATCH 4/4] stm32f4: Add support for stm32f429-discovery board Kamil Lulko
2015-03-05 15:35 ` Tom Rini
2015-04-23 13:14 ` [U-Boot] [U-Boot, " Tom Rini
2015-03-25 4:07 ` [U-Boot] [PATCH 0/4] " Chanwoo Choi
2015-03-25 16:58 ` Tom Rini
2015-03-26 13:47 ` Kamil Lulko
2015-03-26 14:07 ` Tom Rini [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=20150326140755.GA32541@bill-the-cat \
--to=trini@konsulko.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox