From: "Heiko Stübner" <heiko@sntech.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 0/4] Veyron Speedy / ASUS C201 fixes
Date: Fri, 29 Mar 2019 14:56:16 +0100 [thread overview]
Message-ID: <1778546.6QJ9oY325i@diego> (raw)
In-Reply-To: <20190322191436.6268-1-urjaman@gmail.com>
Hi Urja,
Am Freitag, 22. März 2019, 20:14:32 CET schrieb Urja Rannikko:
> Just saying: I'm not familiar with this stuff so i might've misunderstood
> something in my commit messages, but anyways i managed to make it boot.
>
> There's more stuff than just these, but i decided I'd keep it short...
> If you want to know my full setup, you can check out my gh repo for now:
> https://github.com/urjaman/u-boot/commits/c201-stuff
>
> Notably I did include http://patchwork.ozlabs.org/patch/1040541/ in my
> tree when testing (rk3288 pinctrl patch that was linked to on
> the previous thread i found about the veyron speedy being broken).
>
> The one thing that I havent yet fixed is that the USB host port on
> the otg-capable controller (near screen) doesn't work - one guess i have
> is that the dwc2 host driver doesn't force it into host mode...
> (It doesn't even read dr_mode ...)
>
> Urja Rannikko (4):
> pinctrl: exit pinconfig_post_bind if there are no subnodes
> rk3288-board: remove pinctrl call for debug uart
> rk3288-board: cosmetic: document selecting RK PWM
> dw_mmc: turn on the IO supply
In my u-boot list archive I only see the list itself als recipient.
You may want to resend your series with actual maintainers in Cc
so that they actually see your patches :-) .
Similar to the kernel, uboot also has a scripts/get_maintainer.pl
script to give you a list of applicable maintainers (Philipp and Simon
in this case)
Heiko
next prev parent reply other threads:[~2019-03-29 13:56 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-22 19:14 [U-Boot] [PATCH 0/4] Veyron Speedy / ASUS C201 fixes Urja Rannikko
2019-03-22 19:14 ` [U-Boot] [PATCH 1/4] pinctrl: exit pinconfig_post_bind if there are no subnodes Urja Rannikko
2019-03-30 21:18 ` Simon Glass
2019-04-21 18:41 ` [U-Boot] [U-Boot, " Philipp Tomsich
2019-04-23 14:33 ` Philipp Tomsich
2019-03-22 19:14 ` [U-Boot] [PATCH 2/4] rk3288-board: remove pinctrl call for debug uart Urja Rannikko
2019-03-30 21:18 ` Simon Glass
2019-03-31 21:54 ` Urja Rannikko
2019-04-21 18:41 ` [U-Boot] [U-Boot, " Philipp Tomsich
2019-04-23 14:33 ` Philipp Tomsich
2019-03-22 19:14 ` [U-Boot] [PATCH 3/4] rk3288-board: cosmetic: document selecting RK PWM Urja Rannikko
2019-03-30 21:18 ` Simon Glass
2019-03-31 21:46 ` Urja Rannikko
2019-03-22 19:14 ` [U-Boot] [PATCH 4/4] dw_mmc: turn on the IO supply Urja Rannikko
2019-03-29 14:09 ` Heiko Stübner
2019-03-31 19:45 ` Urja Rannikko
2019-04-02 8:25 ` Heiko Stuebner
2019-04-01 17:44 ` [U-Boot] [PATCH v2] " Urja Rannikko
2019-04-11 20:07 ` Urja Rannikko
2019-05-13 12:25 ` Urja Rannikko
2019-05-13 12:54 ` Heiko Stuebner
2019-05-13 13:25 ` [U-Boot] [PATCH v3] " Urja Rannikko
2019-05-18 16:08 ` Simon Glass
2019-05-20 7:03 ` Peng Fan
2019-07-26 7:06 ` Kever Yang
2019-07-30 0:47 ` Peng Fan
2019-03-29 13:56 ` Heiko Stübner [this message]
2019-03-31 19:34 ` [U-Boot] [PATCH 0/4] Veyron Speedy / ASUS C201 fixes Urja Rannikko
2019-03-31 20:44 ` Heiko Stübner
2019-03-31 22:19 ` Urja Rannikko
2019-04-11 20:14 ` Urja Rannikko
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=1778546.6QJ9oY325i@diego \
--to=heiko@sntech.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