* k2 ramfs missing firmwre
@ 2016-09-09 13:31 Jacob Stiffler
2016-09-09 17:36 ` Denys Dmytriyenko
0 siblings, 1 reply; 4+ messages in thread
From: Jacob Stiffler @ 2016-09-09 13:31 UTC (permalink / raw)
To: meta-arago@arago-project.org
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?
Thank you,
Jake
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: k2 ramfs missing firmwre
2016-09-09 13:31 k2 ramfs missing firmwre Jacob Stiffler
@ 2016-09-09 17:36 ` Denys Dmytriyenko
2016-09-09 17:42 ` Jacob Stiffler
0 siblings, 1 reply; 4+ messages in thread
From: Denys Dmytriyenko @ 2016-09-09 17:36 UTC (permalink / raw)
To: Jacob Stiffler; +Cc: meta-arago@arago-project.org
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
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: k2 ramfs missing firmwre
2016-09-09 17:36 ` Denys Dmytriyenko
@ 2016-09-09 17:42 ` Jacob Stiffler
2016-09-09 17:45 ` Denys Dmytriyenko
0 siblings, 1 reply; 4+ messages in thread
From: Jacob Stiffler @ 2016-09-09 17:42 UTC (permalink / raw)
To: Denys Dmytriyenko; +Cc: meta-arago@arago-project.org
On 9/9/2016 1:36 PM, Denys Dmytriyenko wrote:
> 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...
That is the one that is missing. Thank you for pointing out that these
firmwares are kernel dependencies. I knew that at one time...
I will submit a patch.
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: k2 ramfs missing firmwre
2016-09-09 17:42 ` Jacob Stiffler
@ 2016-09-09 17:45 ` Denys Dmytriyenko
0 siblings, 0 replies; 4+ messages in thread
From: Denys Dmytriyenko @ 2016-09-09 17:45 UTC (permalink / raw)
To: Jacob Stiffler; +Cc: meta-arago@arago-project.org
On Fri, Sep 09, 2016 at 01:42:02PM -0400, Jacob Stiffler wrote:
>
>
> On 9/9/2016 1:36 PM, Denys Dmytriyenko wrote:
> >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...
> That is the one that is missing. Thank you for pointing out that
> these firmwares are kernel dependencies. I knew that at one time...
>
> I will submit a patch.
Oh, I already did, once I noticed qmss was missing. Let me know if anything
else is missing or incorrect. Thanks.
--
Denys
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2016-09-09 17:45 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2016-09-09 13:31 k2 ramfs missing firmwre Jacob Stiffler
2016-09-09 17:36 ` Denys Dmytriyenko
2016-09-09 17:42 ` Jacob Stiffler
2016-09-09 17:45 ` Denys Dmytriyenko
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.