Hi,

I'm new here, never participated, anyway, I also plan to boot linux from QSPI.

My use case is a bit different, I'll be using a module with QSPI and gigabytes 
of DDR, and the first use case is to stream the output of the PL part on USB or 
Ethernet. I think I can just get rid of eMMC in my design.

I think it would be nice to maintain a standard image to boot on QSPI only.


Thanks

________________________________
From: [email protected] 
<[email protected]> on behalf of Philip Balister 
<[email protected]>
Sent: Tuesday, January 22, 2019 4:21:43 PM
To: [email protected]
Subject: [meta-xilinx] Minized support

I finally replaced the provided u-boot with something based of the
version in thud.

Usually issues, no ps7 files source tree and had to enable SPL and
change some settings. I suppose I should go ahead and send those
upstream. Always nice to have the default build work :)

I'm looking at changing the kernel to a fitImge and building a ramdisk
image for qspi. I'd like to boot from qspi, format the emmc and untar a
file system (from usb) into the emmc. Finally boot from a kernel on the
emmc. Does this sound worth upstreaming to meta-xilinx-contrib, or shold
I just carry it locally?

Philip
--
_______________________________________________
meta-xilinx mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/meta-xilinx
-- 
_______________________________________________
meta-xilinx mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/meta-xilinx

Reply via email to