Hi Michal, On Fri, Jul 20, 2018 at 3:09 AM Michal Simek <mon...@monstr.eu> wrote: > On 13.7.2018 17:44, Luis Araneda wrote: > > [...] > > +CONFIG_DM_I2C=y > > +CONFIG_SYS_I2C_CADENCE=y > > +CONFIG_MMC_SDHCI=y > > +CONFIG_MMC_SDHCI_ZYNQ=y > > +CONFIG_SPI_FLASH=y > > +CONFIG_SPI_FLASH_BAR=y > > +CONFIG_SPI_FLASH_SPANSION=y > > +CONFIG_PHY_REALTEK=y > > +CONFIG_ZYNQ_GEM=y > > +CONFIG_DEBUG_UART_ZYNQ=y > > +CONFIG_ZYNQ_SERIAL=y > > +CONFIG_ZYNQ_QSPI=y > > +CONFIG_USB=y > > +CONFIG_USB_EHCI_HCD=y > > +CONFIG_USB_ULPI_VIEWPORT=y > > +CONFIG_USB_ULPI=y > > +CONFIG_USB_STORAGE=y > > +CONFIG_USB_GADGET=y > > +CONFIG_USB_GADGET_MANUFACTURER="Xilinx" > > +CONFIG_USB_GADGET_VENDOR_NUM=0x03fd > > +CONFIG_USB_GADGET_PRODUCT_NUM=0x0300 > > +CONFIG_CI_UDC=y > > +CONFIG_USB_GADGET_DOWNLOAD=y > > +CONFIG_USB_FUNCTION_THOR=y > > +CONFIG_DISPLAY=y > > Not sure if make sense to enable this CONFIG_DISPLAY but the rest is fine.
Probably not, I selected it because the Zybo had it selected. I'll remove it for v2. Additionally, for v2 I'll will be using the zynq_i2c driver (not DM) because the I2C peripherals on this board are connected like the Zybo. For more details, refer to the reply of "[PATCH 4/4] arm: zynq: use i2c cadence DM driver" Thanks, Luis Araneda. _______________________________________________ U-Boot mailing list U-Boot@lists.denx.de https://lists.denx.de/listinfo/u-boot
