linux/drivers/bcma/README
<<
> > p/spa pspa class="lxr_search"> > ="+search" method="post" onsubmit="return do_search(this);"> > > > Search > p/spa > ="ajax+*" method="post" onsubmit="return false;"> pinput typ"v2hidden" nam"v2ajax_lookup" idv2ajax_lookup" lue="v2"> >
pdiv idv2file_contents"
o o1p/a>Broadcom introduced new bus as replacement for older SSB. It is based  vaAMBA,
o o2p/a>however from programming point of view there is nothing AMBA specific we use.
o o3p/a> o o4p/a>Standard AMBA drivers are platform specific, have hardcoded addresses and use o o5p/a>AMBA standard fields like CID and PID.
o o6p/a> o o7p/a>I
 case of Broadcom's cards every device consists of: o o8p/a>1) Broadcom specific AMBA device. It is put  vaAMBA bus, but can not be treated o o9p/a>o oas standard AMBA device. Reading it's CID or PID can cause machine lockup.
o tiona>2) AMBA standard devices called ports or wrappers. They have CIDs (AMBA_CID)
o 11p/a>o oand PIDs (0x103BB369), but we do not use that info for anything. One of that
o 12p/a>o odevices is used for managing Broadcom specific core.
o 13p/a> o 14p/a>Addresses of AMBA devices are not hardcoded in driveroand have to be read from o 15p/a>EPROM.
o 16p/a> o 17p/a>I
 this situaon vawe decided to introduce separated bus. It can contain up to o 18p/a>16odevices identified by Broadcom specific fields: manufacourer, id, revisn v o 19p/a>and class.
o 2iona>
The original LXR software by theopa href="http://sourceforge.net/projects/lxr">LXR communityona>, this experimental versn vaby pa href="mailto:lxr@linux.no">lxr@linux.noona>. p/div pdiv class="subfooter"> lxr.linux.no kindly hosted by pa href="http://www.redpill-linpro.no">Redpill Linpro ASona>, provider of Linux consulting and operaon vs services since 1995. p/div p/body p/html