• Home
  • History
  • Annotate
Name Date Size #Lines LOC

..--

KconfigD18-Mar-20121.1 KiB5845

MakefileD18-Mar-2012400 119

READMED18-Mar-2012956 2015

TODOD18-Mar-201296 43

bcma_private.hD18-Mar-20121.4 KiB5637

core.cD18-Mar-20122.9 KiB128104

driver_chipcommon.cD18-Mar-20124.2 KiB158118

driver_chipcommon_pmu.cD18-Mar-20127.7 KiB311245

driver_mips.cD18-Mar-20126.2 KiB257192

driver_pci.cD18-Mar-20125.6 KiB239179

driver_pci_host.cD18-Mar-2012289 156

host_pci.cD18-Mar-20127 KiB293234

host_soc.cD18-Mar-20123.6 KiB184147

main.cD18-Mar-20128.6 KiB377298

scan.cD18-Mar-201212.2 KiB490403

scan.hD18-Mar-20121.7 KiB5748

sprom.cD18-Mar-20128.3 KiB248188

README

1Broadcom introduced new bus as replacement for older SSB. It is based on AMBA,
2however from programming point of view there is nothing AMBA specific we use.
3
4Standard AMBA drivers are platform specific, have hardcoded addresses and use
5AMBA standard fields like CID and PID.
6
7In case of Broadcom's cards every device consists of:
81) Broadcom specific AMBA device. It is put on AMBA bus, but can not be treated
9   as standard AMBA device. Reading it's CID or PID can cause machine lockup.
102) AMBA standard devices called ports or wrappers. They have CIDs (AMBA_CID)
11   and PIDs (0x103BB369), but we do not use that info for anything. One of that
12   devices is used for managing Broadcom specific core.
13
14Addresses of AMBA devices are not hardcoded in driver and have to be read from
15EPROM.
16
17In this situation we decided to introduce separated bus. It can contain up to
1816 devices identified by Broadcom specific fields: manufacturer, id, revision
19and class.
20