On Samstag, 1. April 2017 20:05:37 CEST Simon Glass wrote:
> Raspberry Pi uses a DWC2 USB controller and a SMSC USB Ethernet adaptor.
> Driver model support for these is available.
> 
> This series does the following:
> - Enable CONFIG_DM_ETH and CONFIG_DM_USB on Raspberry Pi
> - Convert the MMC driver to driver model
> - Convert the video driver to driver model
> - Fixes a driver model video bug which accessed beyond the frame buffer
> - Fixes start-up of MMC with driver model (e.g. at present it does not
>     support env_fat)
> - Clean up a few loose ends
> 
> With Ethernet active the device list looks something like this:
> 
> U-Boot> dm tree
>  Class       Probed   Name
> ----------------------------------------
>  root        [ + ]    root_driver
>  simple_bus  [ + ]    |-- soc
>  gpio        [ + ]    |   |-- gpio@7e200000
>  serial      [ + ]    |   |-- serial@7e215040
>  mmc         [ + ]    |   |-- sdhci@7e300000
>  blk         [ + ]    |   |   `-- sd...@7e300000.blk
>  video       [ + ]    |   |-- hdmi@7e902000
>  vidconsole0 [ + ]    |   |   `-- hdmi@7e902000.vidconsole0
>  usb         [ + ]    |   `-- usb@7e980000
>  usb_hub     [ + ]    |       `-- usb_hub
>  usb_hub     [ + ]    |           `-- usb_hub
>  eth         [ + ]    |               `-- smsc95xx_eth
>  simple_bus  [   ]    `-- clocks
> 
> With version 4 a problem was discovered where tftpboot does not correctly
> read a file on rpi_2 and rpi_3. The cause is unknown but for now this
> series includes a work-around in the dwc2 driver. See here for details:
> 
> https://lists.denx.de/pipermail/u-boot/2017-April/285451.html

Have you seen https://lists.denx.de/pipermail/u-boot/2017-April/285546.html ?

This may fix the problem seen.

Kind regards,

Stefan

-- 
Stefan Brüns  /  Bergstraße 21  /  52062 Aachen
home: +49 241 53809034     mobile: +49 151 50412019
work: +49 2405 49936-424
_______________________________________________
U-Boot mailing list
U-Boot@lists.denx.de
https://lists.denx.de/listinfo/u-boot

Reply via email to