<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>i.MX ProcessorsのトピックSPI driver Sabre lite</title>
    <link>https://community.nxp.com/t5/i-MX-Processors/SPI-driver-Sabre-lite/m-p/222904#M15118</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I'm trying the nitrogen6x build for the Sabre lite board and trying to enable the SPIdev driver (In Yocto).&lt;/P&gt;&lt;P&gt;I have changed the alias in the board-mx6_nitrogen6x.c file and also updated the defconfig (I think it's the right one) to enable SPIDEV etc.&lt;/P&gt;&lt;P&gt;But I still don't see spidev under /dev directory.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Is there anything else I'm missing here?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I managed to get it work when I was using sabrelite as "MACHINE", for about 2 months ago.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Niklas&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 11 Feb 2014 03:02:54 GMT</pubDate>
    <dc:creator>niklasmolin</dc:creator>
    <dc:date>2014-02-11T03:02:54Z</dc:date>
    <item>
      <title>SPI driver Sabre lite</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/SPI-driver-Sabre-lite/m-p/222904#M15118</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I'm trying the nitrogen6x build for the Sabre lite board and trying to enable the SPIdev driver (In Yocto).&lt;/P&gt;&lt;P&gt;I have changed the alias in the board-mx6_nitrogen6x.c file and also updated the defconfig (I think it's the right one) to enable SPIDEV etc.&lt;/P&gt;&lt;P&gt;But I still don't see spidev under /dev directory.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Is there anything else I'm missing here?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I managed to get it work when I was using sabrelite as "MACHINE", for about 2 months ago.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Niklas&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 11 Feb 2014 03:02:54 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/SPI-driver-Sabre-lite/m-p/222904#M15118</guid>
      <dc:creator>niklasmolin</dc:creator>
      <dc:date>2014-02-11T03:02:54Z</dc:date>
    </item>
    <item>
      <title>Re: SPI driver Sabre lite</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/SPI-driver-Sabre-lite/m-p/222905#M15119</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Niklas,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The default kernel configuration has support for SPI. You can validate this by looking in /proc/mtd to see the flash partitions and you can run "hexdump -c /dev/mtd0r0" to see the content of SPI-NOR.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;It seems that you're asking about userspace SPI access though (/dev/spi...). This isn't included in the standard kernel configuration, and you'd need to enable it by running "bitbake -c menuconfig linux-boundary".&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I wonder why you're doing this though. Are you hooking up a different SPI device through other pins? If so, you'll need to change the pin-muxing for the SPI and chip-select pins and add another SPI bus to the system as shown here:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &lt;A href="https://github.com/boundarydevices/linux-imx6/blob/boundary-imx_3.0.35_4.1.0/arch/arm/mach-mx6/board-mx6_nitrogen6x.c#L399" title="https://github.com/boundarydevices/linux-imx6/blob/boundary-imx_3.0.35_4.1.0/arch/arm/mach-mx6/board-mx6_nitrogen6x.c#L399"&gt;linux-imx6/arch/arm/mach-mx6/board-mx6_nitrogen6x.c at boundary-imx_3.0.35_4.1.0 · boundarydevices/linux-imx6 · GitHub&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If you're doing this level of kernel hacking, I'd strongly recommend building the kernel outside of Yocto, so that you have a proper git repository backing your efforts. &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 11 Feb 2014 13:03:30 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/SPI-driver-Sabre-lite/m-p/222905#M15119</guid>
      <dc:creator>EricNelson</dc:creator>
      <dc:date>2014-02-11T13:03:30Z</dc:date>
    </item>
    <item>
      <title>Re: SPI driver Sabre lite</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/SPI-driver-Sabre-lite/m-p/222906#M15120</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Eric.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks for you reply.&lt;/P&gt;&lt;P&gt;This was definitely helpful, since we just wanted to access the flash to do some tests.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Niklas&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 13 Feb 2014 15:28:56 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/SPI-driver-Sabre-lite/m-p/222906#M15120</guid>
      <dc:creator>niklasmolin</dc:creator>
      <dc:date>2014-02-13T15:28:56Z</dc:date>
    </item>
  </channel>
</rss>

