From: Denys Dmytriyenko <denys@ti.com>
To: Jacob Stiffler <j-stiffler@ti.com>
Cc: "meta-arago@arago-project.org" <meta-arago@arago-project.org>
Subject: Re: k2 ramfs missing firmwre
Date: Fri, 9 Sep 2016 13:36:59 -0400 [thread overview]
Message-ID: <20160909173659.GW29658@edge> (raw)
In-Reply-To: <bf4e78a8-7aba-110c-53fe-4fad4c23b10f@ti.com>
On Fri, Sep 09, 2016 at 09:31:25AM -0400, Jacob Stiffler wrote:
> Hi,
>
> The K2 ramfs is missing the firmwares necessary to boot up. The K2
> ramfs is simply the tisdk-server-rootfs-image in cpio.gz format.
>
> These firmwares are available in the k2-initramfs image. However,
> when u-boot is configured for ramfs, the initramfs is not loaded
> prior to booting. Therefore it seems that the firmwares in the
> k2-initramfs should also be available in the
> tisdk-server-rootfs-image. Is this correct? Would this cause any
> conflict with other boot methods which do use the initramfs?
>
> If these firmwares can go into the tisdk-server-rootfs-image, which
> would be the most appropriate pacakgegroup?
Jake,
Those firmware images are already there in the rootfs, regardless of the
format - they are being pulled by kernel dependencies individually:
$ xz -dc tisdk-server-rootfs-image-k2hk-evm-20160909112210.rootfs.cpio.xz | cpio -t 'lib/firmware/ks2*'
lib/firmware/ks2_gbe_serdes.bin
lib/firmware/ks2_pa_pdsp2_classify1.bin
lib/firmware/ks2_pa_pdsp1_classify1.bin
lib/firmware/ks2_pa_pdsp0_classify1.bin
lib/firmware/ks2_pa_pdsp3_classify2.bin
lib/firmware/ks2_xgbe_serdes.bin
lib/firmware/ks2_pcie_serdes.bin
lib/firmware/ks2_pa_pdsp5_pam.bin
lib/firmware/ks2_pa_pdsp4_pam.bin
1488976 blocks
$ xz -dc tisdk-server-rootfs-image-k2e-evm-20160909063519.rootfs.cpio.xz | cpio -t 'lib/firmware/ks2*'
lib/firmware/ks2_gbe_serdes.bin
lib/firmware/ks2_pa_in4_pdsp0.bin
lib/firmware/ks2_pa_eg2_pdsp0.bin
lib/firmware/ks2_pa_in4_pdsp1.bin
lib/firmware/ks2_pa_in3_pdsp0.bin
lib/firmware/ks2_pa_in0_pdsp0.bin
lib/firmware/ks2_pa_eg0_pdsp2.bin
lib/firmware/ks2_pa_eg0_pdsp1.bin
lib/firmware/ks2_pa_in1_pdsp0.bin
lib/firmware/ks2_pa_post_pdsp0.bin
lib/firmware/ks2_pa_in2_pdsp0.bin
lib/firmware/ks2_pa_in1_pdsp1.bin
lib/firmware/ks2_xgbe_serdes.bin
lib/firmware/ks2_pcie_serdes.bin
lib/firmware/ks2_pa_in0_pdsp1.bin
lib/firmware/ks2_pa_eg1_pdsp0.bin
lib/firmware/ks2_pa_post_pdsp1.bin
lib/firmware/ks2_pa_eg0_pdsp0.bin
1460743 blocks
What's missing? Although, I don't see qmss one...
--
Denys
next prev parent reply other threads:[~2016-09-09 17:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-09 13:31 k2 ramfs missing firmwre Jacob Stiffler
2016-09-09 17:36 ` Denys Dmytriyenko [this message]
2016-09-09 17:42 ` Jacob Stiffler
2016-09-09 17:45 ` Denys Dmytriyenko
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=20160909173659.GW29658@edge \
--to=denys@ti.com \
--cc=j-stiffler@ti.com \
--cc=meta-arago@arago-project.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.