From: Chee, Tien Fong <tien.fong.chee@intel.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 1/2] common: Generic file system firmware loader
Date: Tue, 7 Nov 2017 09:03:58 +0000 [thread overview]
Message-ID: <1510045437.2479.10.camel@intel.com> (raw)
In-Reply-To: <25cf9828-2888-45a7-5df5-2d879460e6f8@denx.de>
On Isn, 2017-11-06 at 11:56 +0100, Marek Vasut wrote:
> On 11/06/2017 05:15 AM, Chee, Tien Fong wrote:
> >
> > On Ahd, 2017-11-05 at 17:43 +0100, Marek Vasut wrote:
> > >
> > > On 11/02/2017 09:20 AM, Chee, Tien Fong wrote:
> > > >
> > > >
> > > > On Rab, 2017-11-01 at 10:26 +0100, Marek Vasut wrote:
> > > > >
> > > > >
> > > > > On 11/01/2017 10:18 AM, tien.fong.chee at intel.com wrote:
> > > > > >
> > > > > >
> > > > > >
> > > > > > From: Tien Fong Chee <tien.fong.chee@intel.com>
> > > > > >
> > > > > > Generic firmware loader framework contains some common
> > > > > > functionality
> > > > > > which is factored out from splash loader. It is reusable by
> > > > > > any
> > > > > > specific driver file system firmware loader. Specific
> > > > > > driver
> > > > > > file
> > > > > > system
> > > > > > firmware loader handling can be defined with both weak
> > > > > > function
> > > > > > fsloader_preprocess and fs_loading.
> > > > > >
> > > > > > Signed-off-by: Tien Fong Chee <tien.fong.chee@intel.com>
> > > > > > ---
> > > > > > common/Makefile | 1 +
> > > > > > common/load_fs.c | 217
> > > > > > ++++++++++++++++++++++++++++++++++++++++++++++++++++++
> > > > > > include/load_fs.h | 38 ++++++++++
> > > > > > 3 files changed, 256 insertions(+)
> > > > > > create mode 100644 common/load_fs.c
> > > > > > create mode 100644 include/load_fs.h
> > > > > [...]
> > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > > +int flash_select_fs_dev(struct flash_location *location)
> > > > > Why does everything have flash_ prefix ?
> > > > >
> > > > I can remove the flash_ prefix, this generic FS loader should
> > > > support
> > > > for all filesystem instead of flash.
> > > >
> > > > >
> > > > >
> > > > > I also mentioned the API should copy the linux firmware
> > > > > loader
> > > > > API.
> > > > >
> > > > If i'm not mistaken, you are referring firmware loader API in
> > > > this
> > > > link https://github.com/torvalds/linux/blob/f007cad159e99fa2acd
> > > > 3b2e
> > > > 9364
> > > > fbb32ad28b971/drivers/base/firmware_class.c#L1264.
> > > >
> > I would like to confirm with you whether we are talking to the same
> > API
> > above?
> https://www.kernel.org/doc/html/v4.13/driver-api/firmware/index.html
>
> first link on google btw . You might be able to avoid the firmware
> structure.
>
After assessment, i found that Linux loader is not suitable for fpga
loader as fpga loader need
1) Able to program FPGA image in SPL chunk bu chunk with small memory
allocatted.
2) Name of FPGA image defined in DTS, and path of FPGA image in FAT and
UBI partition.
Linux loader is strongly designed based on Linux environment, always
assume having RFF, env support(which SPL don't have), sysfs and udev
feature.
Thanks.
> [...]
>
next prev parent reply other threads:[~2017-11-07 9:03 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-01 9:18 [U-Boot] [PATCH 0/2] Creating generic file system firmware loader tien.fong.chee at intel.com
2017-11-01 9:18 ` [U-Boot] [PATCH 1/2] common: Generic " tien.fong.chee at intel.com
2017-11-01 9:26 ` Marek Vasut
2017-11-02 8:20 ` Chee, Tien Fong
2017-11-05 16:43 ` Marek Vasut
2017-11-06 4:15 ` Chee, Tien Fong
2017-11-06 10:56 ` Marek Vasut
2017-11-07 9:03 ` Chee, Tien Fong [this message]
2017-11-07 9:34 ` Marek Vasut
2017-11-09 6:04 ` Chee, Tien Fong
2017-11-09 7:05 ` Marek Vasut
2017-11-09 7:09 ` Chee, Tien Fong
2017-11-09 10:00 ` Lukasz Majewski
2017-11-09 10:31 ` Marek Vasut
2017-11-10 9:05 ` Chee, Tien Fong
2017-11-10 10:04 ` Marek Vasut
2017-11-13 4:31 ` Chee, Tien Fong
2017-11-16 8:09 ` Chee, Tien Fong
2017-11-16 8:11 ` Marek Vasut
2017-11-01 9:18 ` [U-Boot] [PATCH 2/2] common: Convert splash FS loader to use generic FS " tien.fong.chee at intel.com
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=1510045437.2479.10.camel@intel.com \
--to=tien.fong.chee@intel.com \
--cc=u-boot@lists.denx.de \
/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