Hi, I work on u-boot for Octeon based boards. I found some variables to be at address more than uboot_end.
Isin't everything expected to be within uboot_end which is defined by loader script. Can someone explain why do I see variables outside of uboot_end and what impact can this have. If I look in uboot.map I see these variables belonging to some special area called .scommon. What's that??? Regds. Nits bfcac42c A uboot_end bfcac430 C __abi32 bfcac434 C packets_sent bfcac438 C loopback_dev bfcac440 C coremask_iter_first_core bfcac448 C boot_cycle_adjustment bfcac450 C coremask_iter_core bfcac454 C coremask_iter_mask bfcac458 C coremask_to_run bfcac45c C phy_mem_list_head bfcac460 C pci_cons_desc_addr bfcac468 C monitor_flash_len bfcac46c C usb_scan_dev bfcac470 C NetArpWaitTry bfcac474 C NetArpWaitPacketMAC bfcac478 C NetOurEther bfcac480 C NetOurIP bfcac484 C NetPingIP bfcac488 C NetServerIP bfcac48c C NetArpWaitTxPacketSize bfcac490 C NetArpWaitReplyIP bfcac494 C NetArpWaitTxPacket bfcac498 C NetArpWaitPacketIP bfcac49c C NetState bfcac4a0 C NetIPID bfcac4a4 C NetRxPkt bfcac4a8 C NetRxPktLen bfcac4ac C NetBootFileXferSize bfcac4b0 C NetArpWaitTimerStart bfcac4b4 C BootpTry bfcac4b8 C BootpID bfcac4bc C RarpTry bfcac4c0 C dp_last_size bfcac4c4 C dp_last_addr bfcac4c8 C mm_last_size bfcac4cc C mm_last_addr bfcac4d0 C usb_root_hub_devnum bfcac4d8 C usb_started bfcac4dc C usb_multi_root_hub bfcac4e0 C usb_num_root_hub bfcac4e4 C dev_usb_index bfcac4e8 C ___strtok bfcac4ec C urb_finished
_______________________________________________ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
