On Wed, Apr 18, 2018 at 09:05:19AM -0500, Kyle Evans wrote:
> On Tue, Jan 9, 2018 at 7:34 AM, Maxime Ripard
> wrote:
> > On Mon, Jan 08, 2018 at 09:30:57AM -0600, Kyle Evans wrote:
> >> On Thu, Jan 4, 2018 at 8:01 AM, Maxime Ripard
> >>
On Wed, Apr 18, 2018 at 09:05:19AM -0500, Kyle Evans wrote:
> On Tue, Jan 9, 2018 at 7:34 AM, Maxime Ripard
> wrote:
> > On Mon, Jan 08, 2018 at 09:30:57AM -0600, Kyle Evans wrote:
> >> On Thu, Jan 4, 2018 at 8:01 AM, Maxime Ripard
> >> wrote:
> >> > On Fri, Dec 22, 2017 at 06:11:52PM +0800,
On Tue, Jan 9, 2018 at 7:34 AM, Maxime Ripard
wrote:
> On Mon, Jan 08, 2018 at 09:30:57AM -0600, Kyle Evans wrote:
>> On Thu, Jan 4, 2018 at 8:01 AM, Maxime Ripard
>> wrote:
>> > On Fri, Dec 22, 2017 at 06:11:52PM +0800, Chen-Yu
On Tue, Jan 9, 2018 at 7:34 AM, Maxime Ripard
wrote:
> On Mon, Jan 08, 2018 at 09:30:57AM -0600, Kyle Evans wrote:
>> On Thu, Jan 4, 2018 at 8:01 AM, Maxime Ripard
>> wrote:
>> > On Fri, Dec 22, 2017 at 06:11:52PM +0800, Chen-Yu Tsai wrote:
>> >> On Fri, Dec 22, 2017 at 6:07 PM, Emmanuel Vadot
On Tue, Jan 9, 2018 at 7:34 AM, Maxime Ripard
wrote:
> On Mon, Jan 08, 2018 at 09:30:57AM -0600, Kyle Evans wrote:
>> On Thu, Jan 4, 2018 at 8:01 AM, Maxime Ripard
>> wrote:
>> > On Fri, Dec 22, 2017 at 06:11:52PM +0800, Chen-Yu
On Tue, Jan 9, 2018 at 7:34 AM, Maxime Ripard
wrote:
> On Mon, Jan 08, 2018 at 09:30:57AM -0600, Kyle Evans wrote:
>> On Thu, Jan 4, 2018 at 8:01 AM, Maxime Ripard
>> wrote:
>> > On Fri, Dec 22, 2017 at 06:11:52PM +0800, Chen-Yu Tsai wrote:
>> >> On Fri, Dec 22, 2017 at 6:07 PM, Emmanuel Vadot
On Mon, Jan 08, 2018 at 09:30:57AM -0600, Kyle Evans wrote:
> On Thu, Jan 4, 2018 at 8:01 AM, Maxime Ripard
> wrote:
> > On Fri, Dec 22, 2017 at 06:11:52PM +0800, Chen-Yu Tsai wrote:
> >> On Fri, Dec 22, 2017 at 6:07 PM, Emmanuel Vadot
>
On Mon, Jan 08, 2018 at 09:30:57AM -0600, Kyle Evans wrote:
> On Thu, Jan 4, 2018 at 8:01 AM, Maxime Ripard
> wrote:
> > On Fri, Dec 22, 2017 at 06:11:52PM +0800, Chen-Yu Tsai wrote:
> >> On Fri, Dec 22, 2017 at 6:07 PM, Emmanuel Vadot
> >> wrote:
> >> > On Fri, 22 Dec 2017 09:35:08 +0100
> >>
On Thu, Jan 4, 2018 at 8:01 AM, Maxime Ripard
wrote:
> On Fri, Dec 22, 2017 at 06:11:52PM +0800, Chen-Yu Tsai wrote:
>> On Fri, Dec 22, 2017 at 6:07 PM, Emmanuel Vadot
>> wrote:
>> > On Fri, 22 Dec 2017 09:35:08 +0100
>> > Maxime Ripard
On Thu, Jan 4, 2018 at 8:01 AM, Maxime Ripard
wrote:
> On Fri, Dec 22, 2017 at 06:11:52PM +0800, Chen-Yu Tsai wrote:
>> On Fri, Dec 22, 2017 at 6:07 PM, Emmanuel Vadot
>> wrote:
>> > On Fri, 22 Dec 2017 09:35:08 +0100
>> > Maxime Ripard wrote:
>> >
>> >> On Thu, Dec 21, 2017 at 07:09:03PM
On Fri, Dec 22, 2017 at 06:11:52PM +0800, Chen-Yu Tsai wrote:
> On Fri, Dec 22, 2017 at 6:07 PM, Emmanuel Vadot wrote:
> > On Fri, 22 Dec 2017 09:35:08 +0100
> > Maxime Ripard wrote:
> >
> >> On Thu, Dec 21, 2017 at 07:09:03PM +0100,
On Fri, Dec 22, 2017 at 06:11:52PM +0800, Chen-Yu Tsai wrote:
> On Fri, Dec 22, 2017 at 6:07 PM, Emmanuel Vadot wrote:
> > On Fri, 22 Dec 2017 09:35:08 +0100
> > Maxime Ripard wrote:
> >
> >> On Thu, Dec 21, 2017 at 07:09:03PM +0100, Emmanuel Vadot wrote:
> >> >
> >> > Hi Maxime,
> >> >
> >> >
On Fri, Dec 22, 2017 at 6:07 PM, Emmanuel Vadot wrote:
> On Fri, 22 Dec 2017 09:35:08 +0100
> Maxime Ripard wrote:
>
>> On Thu, Dec 21, 2017 at 07:09:03PM +0100, Emmanuel Vadot wrote:
>> >
>> > Hi Maxime,
>> >
>> > On Thu, 21 Dec 2017
On Fri, Dec 22, 2017 at 6:07 PM, Emmanuel Vadot wrote:
> On Fri, 22 Dec 2017 09:35:08 +0100
> Maxime Ripard wrote:
>
>> On Thu, Dec 21, 2017 at 07:09:03PM +0100, Emmanuel Vadot wrote:
>> >
>> > Hi Maxime,
>> >
>> > On Thu, 21 Dec 2017 16:26:30 +0100
>> > Maxime Ripard wrote:
>> >
>> > > Hi,
>>
On Fri, 22 Dec 2017 09:35:08 +0100
Maxime Ripard wrote:
> On Thu, Dec 21, 2017 at 07:09:03PM +0100, Emmanuel Vadot wrote:
> >
> > Hi Maxime,
> >
> > On Thu, 21 Dec 2017 16:26:30 +0100
> > Maxime Ripard wrote:
> >
> > > Hi,
On Fri, 22 Dec 2017 09:35:08 +0100
Maxime Ripard wrote:
> On Thu, Dec 21, 2017 at 07:09:03PM +0100, Emmanuel Vadot wrote:
> >
> > Hi Maxime,
> >
> > On Thu, 21 Dec 2017 16:26:30 +0100
> > Maxime Ripard wrote:
> >
> > > Hi,
> > >
> > > On Thu, Dec 21, 2017 at 09:19:24AM -0600, Kyle Evans
On Thu, Dec 21, 2017 at 07:09:03PM +0100, Emmanuel Vadot wrote:
>
> Hi Maxime,
>
> On Thu, 21 Dec 2017 16:26:30 +0100
> Maxime Ripard wrote:
>
> > Hi,
> >
> > On Thu, Dec 21, 2017 at 09:19:24AM -0600, Kyle Evans wrote:
> > > On Thu, Dec 21, 2017 at 8:55 AM,
On Thu, Dec 21, 2017 at 07:09:03PM +0100, Emmanuel Vadot wrote:
>
> Hi Maxime,
>
> On Thu, 21 Dec 2017 16:26:30 +0100
> Maxime Ripard wrote:
>
> > Hi,
> >
> > On Thu, Dec 21, 2017 at 09:19:24AM -0600, Kyle Evans wrote:
> > > On Thu, Dec 21, 2017 at 8:55 AM, Maxime Ripard
> > > wrote:
> > >
Hi Maxime,
On Thu, 21 Dec 2017 16:26:30 +0100
Maxime Ripard wrote:
> Hi,
>
> On Thu, Dec 21, 2017 at 09:19:24AM -0600, Kyle Evans wrote:
> > On Thu, Dec 21, 2017 at 8:55 AM, Maxime Ripard
> > wrote:
> > > Hi Kyle,
> > >
> >
Hi Maxime,
On Thu, 21 Dec 2017 16:26:30 +0100
Maxime Ripard wrote:
> Hi,
>
> On Thu, Dec 21, 2017 at 09:19:24AM -0600, Kyle Evans wrote:
> > On Thu, Dec 21, 2017 at 8:55 AM, Maxime Ripard
> > wrote:
> > > Hi Kyle,
> > >
> > > On Tue, Dec 19, 2017 at 03:05:23PM -0600, kevan...@ksu.edu wrote:
On Thu, Dec 21, 2017 at 11:26 PM, Maxime Ripard
wrote:
> Hi,
>
> On Thu, Dec 21, 2017 at 09:19:24AM -0600, Kyle Evans wrote:
>> On Thu, Dec 21, 2017 at 8:55 AM, Maxime Ripard
>> wrote:
>> > Hi Kyle,
>> >
>> > On Tue, Dec 19,
On Thu, Dec 21, 2017 at 11:26 PM, Maxime Ripard
wrote:
> Hi,
>
> On Thu, Dec 21, 2017 at 09:19:24AM -0600, Kyle Evans wrote:
>> On Thu, Dec 21, 2017 at 8:55 AM, Maxime Ripard
>> wrote:
>> > Hi Kyle,
>> >
>> > On Tue, Dec 19, 2017 at 03:05:23PM -0600, kevan...@ksu.edu wrote:
>> >> Allwinner a83t
On Thu, Dec 21, 2017 at 9:26 AM, Maxime Ripard
wrote:
> Hi,
>
> On Thu, Dec 21, 2017 at 09:19:24AM -0600, Kyle Evans wrote:
>> On Thu, Dec 21, 2017 at 8:55 AM, Maxime Ripard
>> wrote:
>> > Hi Kyle,
>> >
>> > On Tue, Dec 19, 2017
On Thu, Dec 21, 2017 at 9:26 AM, Maxime Ripard
wrote:
> Hi,
>
> On Thu, Dec 21, 2017 at 09:19:24AM -0600, Kyle Evans wrote:
>> On Thu, Dec 21, 2017 at 8:55 AM, Maxime Ripard
>> wrote:
>> > Hi Kyle,
>> >
>> > On Tue, Dec 19, 2017 at 03:05:23PM -0600, kevan...@ksu.edu wrote:
>> >> Allwinner a83t
Hi,
On Thu, Dec 21, 2017 at 09:19:24AM -0600, Kyle Evans wrote:
> On Thu, Dec 21, 2017 at 8:55 AM, Maxime Ripard
> wrote:
> > Hi Kyle,
> >
> > On Tue, Dec 19, 2017 at 03:05:23PM -0600, kevan...@ksu.edu wrote:
> >> Allwinner a83t has a 1 KB sid block with efuse
Hi,
On Thu, Dec 21, 2017 at 09:19:24AM -0600, Kyle Evans wrote:
> On Thu, Dec 21, 2017 at 8:55 AM, Maxime Ripard
> wrote:
> > Hi Kyle,
> >
> > On Tue, Dec 19, 2017 at 03:05:23PM -0600, kevan...@ksu.edu wrote:
> >> Allwinner a83t has a 1 KB sid block with efuse for security rootkey and
> >>
On Thu, Dec 21, 2017 at 8:55 AM, Maxime Ripard
wrote:
> Hi Kyle,
>
> On Tue, Dec 19, 2017 at 03:05:23PM -0600, kevan...@ksu.edu wrote:
>> Allwinner a83t has a 1 KB sid block with efuse for security rootkey and
>> thermal calibration data, add node to describe it.
On Thu, Dec 21, 2017 at 8:55 AM, Maxime Ripard
wrote:
> Hi Kyle,
>
> On Tue, Dec 19, 2017 at 03:05:23PM -0600, kevan...@ksu.edu wrote:
>> Allwinner a83t has a 1 KB sid block with efuse for security rootkey and
>> thermal calibration data, add node to describe it.
>>
>> a83t-sid is not currently
Hi Kyle,
On Tue, Dec 19, 2017 at 03:05:23PM -0600, kevan...@ksu.edu wrote:
> Allwinner a83t has a 1 KB sid block with efuse for security rootkey and
> thermal calibration data, add node to describe it.
>
> a83t-sid is not currently supported by nvmem/sunxi-sid, but it is
> supported in an
Hi Kyle,
On Tue, Dec 19, 2017 at 03:05:23PM -0600, kevan...@ksu.edu wrote:
> Allwinner a83t has a 1 KB sid block with efuse for security rootkey and
> thermal calibration data, add node to describe it.
>
> a83t-sid is not currently supported by nvmem/sunxi-sid, but it is
> supported in an
On Tue, Dec 19, 2017 at 03:05:23PM -0600, kevan...@ksu.edu wrote:
> Allwinner a83t has a 1 KB sid block with efuse for security rootkey and
> thermal calibration data, add node to describe it.
>
> a83t-sid is not currently supported by nvmem/sunxi-sid, but it is
> supported in an external driver
On Tue, Dec 19, 2017 at 03:05:23PM -0600, kevan...@ksu.edu wrote:
> Allwinner a83t has a 1 KB sid block with efuse for security rootkey and
> thermal calibration data, add node to describe it.
>
> a83t-sid is not currently supported by nvmem/sunxi-sid, but it is
> supported in an external driver
Allwinner a83t has a 1 KB sid block with efuse for security rootkey and
thermal calibration data, add node to describe it.
a83t-sid is not currently supported by nvmem/sunxi-sid, but it is
supported in an external driver for FreeBSD.
Signed-off-by: Kyle Evans
---
Changes in
Allwinner a83t has a 1 KB sid block with efuse for security rootkey and
thermal calibration data, add node to describe it.
a83t-sid is not currently supported by nvmem/sunxi-sid, but it is
supported in an external driver for FreeBSD.
Signed-off-by: Kyle Evans
---
Changes in v2:
- remove bogus
34 matches
Mail list logo