On Mon, 2018-06-11 at 13:38 -0600, Simon Glass wrote:
> Hi,
>
> On 11 June 2018 at 08:15, Marek Vasut wrote:
> >
> > On 06/11/2018 04:13 PM, Chee, Tien Fong wrote:
> > >
> > > On Mon, 2018-06-11 at 16:03 +0200, Marek Vasut wrote:
> > > >
> > > > On 06/11/2018 03:55 PM, Chee, Tien Fong wrote:
>
Hi,
On 11 June 2018 at 08:15, Marek Vasut wrote:
> On 06/11/2018 04:13 PM, Chee, Tien Fong wrote:
>> On Mon, 2018-06-11 at 16:03 +0200, Marek Vasut wrote:
>>> On 06/11/2018 03:55 PM, Chee, Tien Fong wrote:
>>> [...]
>
>>
>>>
Linux firmware loading method is diff
On 06/11/2018 04:13 PM, Chee, Tien Fong wrote:
> On Mon, 2018-06-11 at 16:03 +0200, Marek Vasut wrote:
>> On 06/11/2018 03:55 PM, Chee, Tien Fong wrote:
>> [...]
>>>
>
>>
>>>
>>> Linux firmware loading method is different with this
>>> Linux loading firmware with
>>> 1.
On Mon, 2018-06-11 at 16:03 +0200, Marek Vasut wrote:
> On 06/11/2018 03:55 PM, Chee, Tien Fong wrote:
> [...]
> >
> > >
> > > >
> > > > >
> > > > > >
> > > > > > Linux firmware loading method is different with this
> > > > > > Linux loading firmware with
> > > > > > 1. Firmware search paths -
On 06/11/2018 03:55 PM, Chee, Tien Fong wrote:
[...]
> Linux firmware loading method is different with this
> Linux loading firmware with
> 1. Firmware search paths - which is hardcoded in root file
> system
> 2. Built-in firmware - part of kernel binaries
>
> This patch
On Mon, 2018-06-11 at 15:38 +0200, Marek Vasut wrote:
> On 06/11/2018 02:42 PM, Chee, Tien Fong wrote:
> >
> > On Mon, 2018-06-11 at 13:55 +0200, Marek Vasut wrote:
> > >
> > > On 06/11/2018 01:53 PM, Chee, Tien Fong wrote:
> > > >
> > > >
> > > > On Mon, 2018-06-11 at 11:39 +0200, Marek Vasut
On 06/11/2018 02:42 PM, Chee, Tien Fong wrote:
> On Mon, 2018-06-11 at 13:55 +0200, Marek Vasut wrote:
>> On 06/11/2018 01:53 PM, Chee, Tien Fong wrote:
>>>
>>> On Mon, 2018-06-11 at 11:39 +0200, Marek Vasut wrote:
On 06/11/2018 07:01 AM, Chee, Tien Fong wrote:
[...]
>
>
On Mon, 2018-06-11 at 13:55 +0200, Marek Vasut wrote:
> On 06/11/2018 01:53 PM, Chee, Tien Fong wrote:
> >
> > On Mon, 2018-06-11 at 11:39 +0200, Marek Vasut wrote:
> > >
> > > On 06/11/2018 07:01 AM, Chee, Tien Fong wrote:
> > > [...]
> > > >
> > > >
> > > > >
> > > > >
> > > > > >
> > > >
On 06/11/2018 01:53 PM, Chee, Tien Fong wrote:
> On Mon, 2018-06-11 at 11:39 +0200, Marek Vasut wrote:
>> On 06/11/2018 07:01 AM, Chee, Tien Fong wrote:
>> [...]
>>>
>
>>
>> This is a configuration. You do not need (new) a DT
>> compatible
>> for
>> that.
>> So why
On Mon, 2018-06-11 at 11:39 +0200, Marek Vasut wrote:
> On 06/11/2018 07:01 AM, Chee, Tien Fong wrote:
> [...]
> >
> > >
> > > >
> > > > >
> > > > > This is a configuration. You do not need (new) a DT
> > > > > compatible
> > > > > for
> > > > > that.
> > > > > So why is the DT compatible even
On 06/11/2018 07:01 AM, Chee, Tien Fong wrote:
[...]
This is a configuration. You do not need (new) a DT compatible
for
that.
So why is the DT compatible even needed in the FW loader at all ?
>>> I thought DT compatible is used by driver to find the fs_loader
>>> node in
>>
On Thu, 2018-06-07 at 12:29 +0200, Marek Vasut wrote:
> On 06/07/2018 12:11 PM, Chee, Tien Fong wrote:
> >
> > On Thu, 2018-06-07 at 11:50 +0200, Marek Vasut wrote:
> > >
> > > On 06/07/2018 11:45 AM, Chee, Tien Fong wrote:
> > > >
> > > >
> > > > On Thu, 2018-06-07 at 10:41 +0200, Marek Vasut
On 06/07/2018 12:11 PM, Chee, Tien Fong wrote:
> On Thu, 2018-06-07 at 11:50 +0200, Marek Vasut wrote:
>> On 06/07/2018 11:45 AM, Chee, Tien Fong wrote:
>>>
>>> On Thu, 2018-06-07 at 10:41 +0200, Marek Vasut wrote:
On 06/07/2018 10:36 AM, Chee, Tien Fong wrote:
>
>
> On Thu, 2
On Thu, 2018-06-07 at 11:50 +0200, Marek Vasut wrote:
> On 06/07/2018 11:45 AM, Chee, Tien Fong wrote:
> >
> > On Thu, 2018-06-07 at 10:41 +0200, Marek Vasut wrote:
> > >
> > > On 06/07/2018 10:36 AM, Chee, Tien Fong wrote:
> > > >
> > > >
> > > > On Thu, 2018-06-07 at 08:51 +0200, Marek Vasut
On 06/07/2018 11:45 AM, Chee, Tien Fong wrote:
> On Thu, 2018-06-07 at 10:41 +0200, Marek Vasut wrote:
>> On 06/07/2018 10:36 AM, Chee, Tien Fong wrote:
>>>
>>> On Thu, 2018-06-07 at 08:51 +0200, Marek Vasut wrote:
On 06/07/2018 06:04 AM, Chee, Tien Fong wrote:
>
>
> On Wed, 2
On Thu, 2018-06-07 at 10:41 +0200, Marek Vasut wrote:
> On 06/07/2018 10:36 AM, Chee, Tien Fong wrote:
> >
> > On Thu, 2018-06-07 at 08:51 +0200, Marek Vasut wrote:
> > >
> > > On 06/07/2018 06:04 AM, Chee, Tien Fong wrote:
> > > >
> > > >
> > > > On Wed, 2018-06-06 at 10:39 +0200, Marek Vasut
On 06/07/2018 10:36 AM, Chee, Tien Fong wrote:
> On Thu, 2018-06-07 at 08:51 +0200, Marek Vasut wrote:
>> On 06/07/2018 06:04 AM, Chee, Tien Fong wrote:
>>>
>>> On Wed, 2018-06-06 at 10:39 +0200, Marek Vasut wrote:
On 05/24/2018 07:04 AM, tien.fong.c...@intel.com wrote:
>
>
>
On Thu, 2018-06-07 at 08:51 +0200, Marek Vasut wrote:
> On 06/07/2018 06:04 AM, Chee, Tien Fong wrote:
> >
> > On Wed, 2018-06-06 at 10:39 +0200, Marek Vasut wrote:
> > >
> > > On 05/24/2018 07:04 AM, tien.fong.c...@intel.com wrote:
> > > >
> > > >
> > > > From: Tien Fong Chee
> > > >
> > > >
On 06/07/2018 06:04 AM, Chee, Tien Fong wrote:
> On Wed, 2018-06-06 at 10:39 +0200, Marek Vasut wrote:
>> On 05/24/2018 07:04 AM, tien.fong.c...@intel.com wrote:
>>>
>>> From: Tien Fong Chee
>>>
>>> This is file system generic loader which can be used to load
>>> the file image from the storage in
On Wed, 2018-06-06 at 10:39 +0200, Marek Vasut wrote:
> On 05/24/2018 07:04 AM, tien.fong.c...@intel.com wrote:
> >
> > From: Tien Fong Chee
> >
> > This is file system generic loader which can be used to load
> > the file image from the storage into target such as memory.
> > The consumer drive
On 05/24/2018 07:04 AM, tien.fong.c...@intel.com wrote:
> From: Tien Fong Chee
>
> This is file system generic loader which can be used to load
> the file image from the storage into target such as memory.
> The consumer driver would then use this loader to program whatever,
> ie. the FPGA device
21 matches
Mail list logo
