From: Martin Michlmayr <tbm-R+vWnYXSFMfQT0dZR+AlfA@public.gmane.org>
To: Stephen Warren <swarren-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
Cc: Thierry Reding <treding-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>,
Tomeu Vizoso
<tomeu.vizoso-ZGY8ohtN/8qB+jHODAdFcQ@public.gmane.org>,
linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
Stephen Warren <srwarren-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
Subject: Re: tegra-devfreq hangs TK1 with R21.4 u-boot
Date: Fri, 17 Jun 2016 10:34:45 -0700 [thread overview]
Message-ID: <20160617173445.GB28814@jirafa.cyrius.com> (raw)
In-Reply-To: <5764258F.3060207-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
* Stephen Warren <swarren-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org> [2016-06-17 10:30]:
> If simply using mainline U-Boot works and is an option for you, I'd
> suggest that.
Sure, that works for me.
Some background: I'm currently in the process of documenting how to
run Debian on the TK1. I wanted to give users a choice to stay with
the u-boot from R21.4 or to upgrade to a newer mainline u-boot. And
then I ran into the problems with the R21.4 u-boot I described.
I'm perfectly fine with telling users they have to upgrade to mainline
u-boot. We provide precompiled u-boot binaries for TK1 in Debian
anyway.
--
Martin Michlmayr
http://www.cyrius.com/
prev parent reply other threads:[~2016-06-17 17:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-12 3:45 tegra-devfreq hangs TK1 with R21.4 u-boot Martin Michlmayr
2016-06-12 17:15 ` Shreshtha
[not found] ` <loom.20160612T175114-608-eS7Uydv5nfjZ+VzJOa5vwg@public.gmane.org>
2016-06-12 17:31 ` Martin Michlmayr
[not found] ` <20160612173106.GA31522-IRMp5PtgtdoigzW5ZibpNwC/G2K4zDHf@public.gmane.org>
2016-06-17 16:17 ` Stephen Warren
[not found] ` <20160612034541.GA31426-IRMp5PtgtdoigzW5ZibpNwC/G2K4zDHf@public.gmane.org>
2016-06-13 5:45 ` Tomeu Vizoso
2016-06-16 16:16 ` Thierry Reding
[not found] ` <20160616161611.GC19360-EkSeR96xj6Pcmrwk2tT4+A@public.gmane.org>
2016-06-17 16:30 ` Stephen Warren
[not found] ` <5764258F.3060207-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
2016-06-17 17:34 ` Martin Michlmayr [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=20160617173445.GB28814@jirafa.cyrius.com \
--to=tbm-r+vwnyxsfmfqt0dzr+alfa@public.gmane.org \
--cc=linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=srwarren-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org \
--cc=swarren-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org \
--cc=tomeu.vizoso-ZGY8ohtN/8qB+jHODAdFcQ@public.gmane.org \
--cc=treding-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org \
/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