On Wed, Apr 5, 2017 at 11:50 AM, Robert Nelson <robertcnel...@gmail.com> wrote: > On Wed, Apr 5, 2017 at 11:14 AM, Peter Robinson <pbrobin...@gmail.com> wrote: >> "On Thu, Mar 30, 2017 at 8:29 PM, Robert Nelson <robertcnel...@gmail.com> >> wrote: >>> BeagleBone Black Wireless is clone of the BeagleBone Black (BBB) with >>> the Ethernet replaced by a TI wl1835 wireless module. >>> >>> This board can be indentified by the BWAx value after A335BNLT (BBB) >>> in the at24 eeprom: >>> BWAx [aa 55 33 ee 41 33 33 35 42 4e 4c 54 42 57 41 35 |.U3.A335BNLTBWA5|] >>> >>> http://beagleboard.org/black-wireless >>> https://github.com/beagleboard/beaglebone-black-wireless >>> >>> firmware: >>> https://github.com/beagleboard/beaglebone-black-wireless/tree/master/firmware >>> wl18xx mac address: >>> /proc/device-tree/ocp/ethernet@4a100000/slave@4a100200/mac-address >>> >>> Signed-off-by: Robert Nelson <robertcnel...@gmail.com> >>> CC: Tom Rini <tr...@konsulko.com> >>> CC: Jason Kridner <jkrid...@beagleboard.org> >>> CC: Will Newton <wi...@resin.io> >>> --- >>> board/ti/am335x/board.c | 7 +++++++ >>> include/configs/am335x_evm.h | 2 ++ >> >> Shouldn't this also update "CONFIG_OF_LIST="am335x-evm am335x-bone >> am335x-boneblack am335x-evmsk am335x-bonegreen am335x-icev2"" in >> configs/am335x_evm_defconfig ans possibly other am33xx_ configs? > > Hi Peter, > > Currently these patches rely on "CONFIG_OF_CONTROL" being disabled > (non-device-tree boot, aka the old boot method), after we resync with > kernel.org's ti/omap device tree changes. We can go back and enable > device-tree boot for these new devices.
and side note, with CONFIG_OF_CONTROL enabled with these patches, they'll still just use "am335x-boneblack.dtb" in spl/device-tree boot mode.. Since they share the black's eeprom base identifier. Regards, -- Robert Nelson https://rcn-ee.com/ _______________________________________________ U-Boot mailing list U-Boot@lists.denx.de https://lists.denx.de/listinfo/u-boot