This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
cat /home/lab/Documents/petalinux/ili9341_driver_prj/build/tmp/work/zynq_generic-xilinx-linux-gnueabi/external-hdf/1.0-r0/temp/log.do_package.31337 | |
DEBUG: Executing python function extend_recipe_sysroot | |
NOTE: Direct dependencies are ['virtual:native:/run/media/lab/backup_hdd_big/petalinux/ili9341_driver_prj/components/yocto/layers/core/meta/recipes-devtools/pseudo/pseudo_git.bb:do_populate_sysroot', 'virtual:native:/run/media/lab/backup_hdd_big/petalinux/ili9341_driver_prj/components/yocto/layers/core/meta/recipes-devtools/patch/patch_2.7.6.bb:do_populate_sysroot', '/run/media/lab/backup_hdd_big/petalinux/ili9341_driver_prj/components/yocto/layers/core/meta/recipes-devtools/quilt/quilt-native_0.66.bb:do_populate_sysroot'] | |
NOTE: Installed into sysroot: [] | |
NOTE: Skipping as already exists in sysroot: ['pseudo-native', 'patch-native', 'quilt-native', 'automake-native', 'attr-native', 'autoconf-native', 'libtool-native', 'texinfo-dummy-native', 'gettext-minimal-native', 'gnu-config-native', 'm4-native'] | |
DEBUG: Py |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
# | |
# Setup script for PetaLinux development environment. | |
# | |
# Copyright (c) 1995-2013 Xilinx, Inc. All rights reserved. | |
# | |
SETTINGS_FILE='settings.sh' | |
# The right location will be replaced by the installer | |
XIL_SCRIPT_LOC="./" |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
// list: dtc -I fs /sys/firmware/devicetree/base | |
// compile with include: dtc -@ -I dts -O dtb -o spidev-overlay.dtbo -i /home/xilinx/jupyter_notebooks/spi_lcd /home/xilinx/jupyter_notebooks/spi_lcd/spidev-overlay.dts | |
/dts-v1/; | |
/plugin/; /* allow undefined label references and record them */ | |
/include/ "zynq-7000.dtsi" | |
/ { |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
/ { | |
// compatible = "linux,spidev"; | |
//compatible = "xlnx,zynq-7000"; | |
compatible = "xlnx,zynq-spi-r1p6"; | |
fragment@0 { | |
target = <&spi0>; | |
__overlay__ { | |
spidev@0 { | |
//compatible = "xlnx,zynq-7000"; |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
dtc -I fs /sys/firmware/devicetree/base | |
<stdout>: Warning (reg_format): /amba/ethernet@e000b000/ethernet-phy@1:reg: property has invalid length (4 bytes) (#address-cells == 2, #size-cells == 1) | |
<stdout>: Warning (reg_format): /axi/spi@e000d000/flash@0/partition@0:reg: property has invalid length (8 bytes) (#address-cells == 2, #size-cells == 1) | |
<stdout>: Warning (reg_format): /axi/spi@e000d000/flash@0/partition@3:reg: property has invalid length (8 bytes) (#address-cells == 2, #size-cells == 1) | |
<stdout>: Warning (reg_format): /axi/spi@e000d000/flash@0/partition@1:reg: property has invalid length (8 bytes) (#address-cells == 2, #size-cells == 1) | |
<stdout>: Warning (reg_format): /axi/spi@e000d000/flash@0/partition@2:reg: property has invalid length (8 bytes) (#address-cells == 2, #size-cells == 1) | |
<stdout>: Warning (unit_address_vs_reg): /amba/ethernet@e000b000: node has a unit name, but no reg or ranges property | |
<stdout>: Warning (unit_address_vs_reg): /memory: node has a reg or ranges property, but no unit nam |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
<stdout>: Warning (reg_format): /amba/ethernet@e000b000/ethernet-phy@1:reg: property has invalid length (4 bytes) (#address-cells == 2, #size-cells == 1) | |
<stdout>: Warning (reg_format): /axi/spi@e000d000/flash@0/partition@0:reg: property has invalid length (8 bytes) (#address-cells == 2, #size-cells == 1) | |
<stdout>: Warning (reg_format): /axi/spi@e000d000/flash@0/partition@3:reg: property has invalid length (8 bytes) (#address-cells == 2, #size-cells == 1) | |
<stdout>: Warning (reg_format): /axi/spi@e000d000/flash@0/partition@1:reg: property has invalid length (8 bytes) (#address-cells == 2, #size-cells == 1) | |
<stdout>: Warning (reg_format): /axi/spi@e000d000/flash@0/partition@2:reg: property has invalid length (8 bytes) (#address-cells == 2, #size-cells == 1) | |
<stdout>: Warning (unit_address_vs_reg): /amba/ethernet@e000b000: node has a unit name, but no reg or ranges property | |
<stdout>: Warning (unit_address_vs_reg): /memory: node has a reg or ranges property, but no unit name | |
<stdout>: Warning (unit_address_vs_reg |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
/dts-v1/; | |
/plugin/; | |
/ { | |
//compatible = "linux,spidev"; | |
compatible = "xlnx,zynq-7000"; | |
fragment@0 { | |
target = <&spi0>; | |
__overlay__ { |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Hi, | |
I am working at research lab at university and searching for most rational way to implement our open source biophysical modeling software, that could be run on web, desktop and maybe mobile. | |
I have code in Python (numpy, scipy, 3d visualization with mayavi), C++ and CUDA. | |
Also, I could use React/Plotly for UI/visualization. Is it worth choosing any cross-platform framework to implement such project? or it could be harder to maintain it than to write native code for each platform? what what do you think? maybe Flutter? | |
Sorry for posting here, this subreddit allow only posting links for me. | |
Thanks |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
# paieska google videos 'thermal lattice bolzman' | |
# Robert Straka: https://www.youtube.com/watch?v=cvYfGpiJ5ec | |
# geras review, sharma 2020: https://sci-hub.se/10.1016/j.paerosci.2020.100616 | |
# kuris cituoja: | |
# (yra apie D2Q5) Sharma 2018, Keerti Vardhan, Robert Straka, and Frederico Wanderley Tavares. "Natural convection heat transfer modeling by the cascaded thermal lattice Boltzmann method." International Journal of Thermal Sciences 134 (2018): 552-564. | |
#jei be standalone (async) serverio, paleisti reikia su: | |
#panel serve lbm.py --autoreload --dev | |
import numpy as np |