From: Stephen Warren <swarren-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
To: Jimmy Zhang <jimmzhang-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
Cc: amartin-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org,
swarren-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org,
linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [tegrarcm PATCH v1 2/8] tegrarcm: Add support for loading cpu ucode
Date: Thu, 19 Mar 2015 13:42:45 -0600 [thread overview]
Message-ID: <550B26B5.8030903@wwwdotorg.org> (raw)
In-Reply-To: <1426639141-12060-3-git-send-email-jimmzhang-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
On 03/17/2015 06:38 PM, Jimmy Zhang wrote:
> From: Allen Martin <amartin-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
>
> The Denver CPU in Tegra132 requires microcode to be loaded before CPU
> initialization. There are two microcode files required, preboot ucode
> "preboot_cr.bin" and cpu ucode "mts_cr.bin". Add support for loading
> ucode either by the filenames or by directory name from the command line.
> Use default directory "/lib/firmware/nvidia/tegra132/denver-ucode" when
> neither filename nor directory name is given in command line.
I get conflicts when applying this patch. Is it based on the latest
github code?
(I validated this was nothing to do with my having applied patch 5 already)
next prev parent reply other threads:[~2015-03-19 19:42 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-18 0:38 [tegrarcm PATCH v1 0/8] Add T132 support Jimmy Zhang
[not found] ` <1426639141-12060-1-git-send-email-jimmzhang-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2015-03-18 0:38 ` [tegrarcm PATCH v1 1/8] tegrarcm: Add Tegra132 support Jimmy Zhang
[not found] ` <1426639141-12060-2-git-send-email-jimmzhang-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2015-03-23 9:06 ` Thierry Reding
2015-03-18 0:38 ` [tegrarcm PATCH v1 2/8] tegrarcm: Add support for loading cpu ucode Jimmy Zhang
[not found] ` <1426639141-12060-3-git-send-email-jimmzhang-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2015-03-19 19:42 ` Stephen Warren [this message]
2015-03-18 0:38 ` [tegrarcm PATCH v1 2/8] tegrarcm: Add support for loading MTS Jimmy Zhang
[not found] ` <1426639141-12060-4-git-send-email-jimmzhang-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2015-03-23 9:21 ` Thierry Reding
2015-03-18 0:38 ` [tegrarcm PATCH v1 3/8] tegrarcm: Get platform info Jimmy Zhang
[not found] ` <1426639141-12060-5-git-send-email-jimmzhang-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2015-03-23 9:27 ` Thierry Reding
2015-03-18 0:38 ` [tegrarcm PATCH v1 4/8] tegrarcm: add support for odmdata command Jimmy Zhang
[not found] ` <1426639141-12060-6-git-send-email-jimmzhang-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2015-03-19 19:37 ` Stephen Warren
2015-03-18 0:38 ` [tegrarcm PATCH v1 5/8] tegrarcm: Better usb debug messages Jimmy Zhang
[not found] ` <1426639141-12060-7-git-send-email-jimmzhang-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2015-03-19 19:40 ` Stephen Warren
2015-03-18 0:38 ` [tegrarcm PATCH v1 6/8] tegrarcm: increase USB timeout Jimmy Zhang
[not found] ` <1426639141-12060-8-git-send-email-jimmzhang-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2015-03-19 19:35 ` Stephen Warren
2015-03-19 19:46 ` [tegrarcm PATCH v1 0/8] Add T132 support Stephen Warren
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=550B26B5.8030903@wwwdotorg.org \
--to=swarren-3lzwwm7+weoh9zmkesr00q@public.gmane.org \
--cc=amartin-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org \
--cc=jimmzhang-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org \
--cc=linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=swarren-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;
as well as URLs for NNTP newsgroup(s).