On Wed, Dec 19, 2012 at 3:07 PM, Pavan <pavanpatil.elec...@gmail.com> wrote: > Hi, > > i need to configure u-boot-2013.01.rc2 for my custom board, that > is completely based on beaglebone Rev A3,i have mux.h file according to my > hardware i am not understanding the codeflow of beaglebone for include the > mux.h. > > i have some extra hardware on my board,but first i need to understand the > codeflow for beaglebone then only i can change the all required files > according to my hardware. > > Can you please tell me which are the files i need to change? or u-boot is > using pin-mux for baglebone?
No > I checked the file include/configs/am335x_evm.h and also in board/ti/am335x > directory the mux.c is there,but i didn't understand the codeflow properly? As you can see mux.c provides pinmuxes for dedicated hardware parts like UART, I2C etc. In enable_board_pin_mux() u-boot decides what board it is running on and activates relevant hardware parts. main line kernel makes the same. This was different for am3517 though. Yegor _______________________________________________ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
