dimtass

Members
  • Content Count

    3
  • Joined

  • Last visited

Everything posted by dimtass

  1. Hi @balbes150, sorry for late response, but I'm on long holidays and I'll be back in a couple of months. Currently my access to internet is limited. Anyway, I can't test the HDMI right now, but in yocto recipes there are two kind of images/distros. The one is console only and the other is with graphics support. Therefore, depending the image build you're triggering there are different things that are build in the background. That means that there might be some patches or a DT for u-boot/kernel that are different depending the image. Therefore, you need to find the prope
  2. Thanks balbes150, nice one. I get Igor's concerns going the binary way. I've tested the Yocto meta-tegra layer a few weeks ago and I got a bootable image. @balbes150 This is the layer here: https://github.com/madisongh/meta-tegra This is the yocto recipe that makes the kernel: https://github.com/madisongh/meta-tegra/blob/master/recipes-kernel/linux/linux-tegra_4.9.bb This is the defconfig file for nano (tegra210): https://github.com/madisongh/meta-tegra/tree/master/recipes-kernel/linux/linux-tegra-4.9/tegra210 Th
  3. Hi all, I've come upon a weird thing and I wanted to verify that I don't so something wrong. I've build a custom kernel module which is a PWM led device with an SPI interface. If I use the spidev, then everything works fine and I'm able to control the led. But when I'm using a custom device-tree and load the module then when I'm calling the `spi_write()` function then I'm getting an error (-22). The external device is actually an arduino nano that implements an I2C IIO light measurement device, using a dual light dependent resistor. Also I'm u