From mboxrd@z Thu Jan  1 00:00:00 1970
From: Chee, Tien Fong <tien.fong.chee@intel.com>
Date: Mon, 11 Jun 2018 12:42:07 +0000
Subject: [U-Boot] [PATCH v2 3/3] common: Generic loader for file system
In-Reply-To: <81b8f03b-a5d3-4883-a3bc-f1f010f187d3@denx.de>
References: <1527138244-16058-1-git-send-email-tien.fong.chee@intel.com>
 <1527138244-16058-4-git-send-email-tien.fong.chee@intel.com>
 <d4b11d38-e679-5299-f871-b9fe846903e5@denx.de>
 <1528344245.10642.1.camel@intel.com>
 <f9c5aa67-6640-2951-39e2-0d8ca5047a6c@denx.de>
 <1528360598.10642.8.camel@intel.com>
 <f5f14f18-7d44-65e0-883f-201175c537e7@denx.de>
 <1528364720.10642.15.camel@intel.com>
 <ee6ba83e-790f-6ff9-5de6-06b643b17a7d@denx.de>
 <1528366318.10642.19.camel@intel.com>
 <0115d042-8f5d-45ff-5605-7343b051db12@denx.de>
 <1528693318.9950.5.camel@intel.com>
 <cbb66bda-9157-940f-0dbe-8ea2bf219d52@denx.de>
 <1528717995.9614.6.camel@intel.com>
 <81b8f03b-a5d3-4883-a3bc-f1f010f187d3@denx.de>
Message-ID: <1528720926.9614.10.camel@intel.com>
List-Id: <u-boot.lists.denx.de>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
To: u-boot@lists.denx.de

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:
> > > [...]
> > > > 
> > > > 
> > > > > 
> > > > > 
> > > > > > 
> > > > > > 
> > > > > > > 
> > > > > > > 
> > > > > > > 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
> > > > > > DTS. May be i am wrong.
> > > > > There should be no FW loader in the DTS. Why would there be
> > > > > one ?
> > > > > 
> > > >  I added DTS support for user to define storage type and
> > > > default
> > > > partition. So you want me to remove the DTS?
> > > > Removing the DTS, then user can only set storage type and
> > > > partition
> > > > through dev instance. So, this design OK for you?
> > > How does Linux do it ?
> > > 
> > 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 loading firmware with
> > 1. Storage type and partition specified in DTS, but storage type
> > can
> > be overridden dev instance and partition through U-boot variable
> > environment.
> > 
> > Or:
> > 
> > 2. Storage type can be set through dev instance, and partition
> > through
> > U-boot variable environment. No DTS is required.
> And why can we not do as Linux does ?
> 
Because we don't have root file system, but i have mimicked the search
path in our variable environment, but with both storage type and
partition.