On Mon, Jan 25, 2016 at 11:15 AM, Alexandre Courbot <gnurou@xxxxxxxxx> wrote:
> On Thu, Jan 21, 2016 at 9:31 PM, Emil Velikov <emil.l.velikov@xxxxxxxxx> wrote:
>> On 21 January 2016 at 12:13, Ben Skeggs <skeggsb@xxxxxxxxx> wrote:
>>> On 01/21/2016 10:09 PM, Emil Velikov wrote:
>>>> Hi Alexandre,
>>>>
>>>> On 18 January 2016 at 06:10, Alexandre Courbot <acourbot@xxxxxxxxxx> wrote:
>>>>
>>>> [snip]
>>>>> +static const char *
>>>>> +managed_falcons_names[] = {
>>>>> + [NVKM_SECBOOT_FALCON_PMU] = "PMU",
>>>>> + [NVKM_SECBOOT_FALCON_RESERVED] = "<invalid>",
>>>> "<reserved>" perhaps ? we already have one invalid below.
>>> Does <reserved> really mean: "we don't want to tell you?" here? :)
>>>
>> That or we have some secret WIP that we're haven't decided if it'll work out :-)
>
> That's just how it appears on our end. :) But since this enum does not
> seem to be used by the hardware anyway, I will simply remove the
> "_RESERVED" entry. Thanks.
Meh, stupid me - these values also appear in the firmware files, so I
must keep the same numbering, and thus the _RESERVED entry. Sorry for
the noise.
--
To unsubscribe from this list: send the line "unsubscribe linux-tegra" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
