On Fri, 2015-08-21 at 20:17 +0200, Hauke Mehrtens wrote: > > On 08/16/2015 06:19 AM, Ian Kent wrote: > > On Tue, 2015-06-23 at 07:58 +0800, Ian Kent wrote: > >> On Mon, 2015-06-22 at 18:42 +0200, Hauke Mehrtens wrote: > >>> > >>> On 03/10/2015 04:30 AM, Ian Kent wrote: > >>>> The Netgear R8000 has a PEX8603 connected to the BCM53012 and if > >>>> it isn't configured during the bus scan the PCI layer goes crazy > >>>> trying to configure phantom devices. > >>> > >>> Could you provide some diagram how this is connected? > >> > >> I could try, when I get a chance, ascii art isn't my strong suit. > >> > >>> > >>> My current assumption is that on one of the 3 PCIe ports is this switch, > >>> so the scan will find this switch as a PCIe device, bu how does it go > >>> from there? > >> > >> I can only infer from looking at sysfs, which is what I have done. > >> > >> Perhaps I'm not correct but it looks to me that there are is a BCM53012 > >> connected with two legs, one has one wireless device, and the other has > >> a PEX8603 bridge which has two legs, each with a wireless device. > >> > >>> From the vendor driver I would assume that that the two devices behind > >>> the switch are device function 0x08 and 0x10 on the switch device. > >> > >> I'll have to reacquaint myself with the code before I respond to the > >> comments below, its been a while. > >> > >>> > >>> Can you also post the output of lspci on your device? > >> > >> Don't think I have lspci in the build I was using, I'll need to add it > >> and rebuild. That probably won't be until the weekend. > > > > OK, I've been able get a build. > > I think we do not get this into OpenWrt CC any more. You should probably > base your work on top of the new PCIe host driver in the trunk used with > kernel 4.1. > > Will you send a new Version or should I look into this?
I will, have been and continue to be quite busy so it will need to be done when I decide to have some "weekend time", ;) > > > My updated patch doesn't yet function so I've used the driver we're > > discussing here to get info. > > > > TBH, looking at this, I'm not so sure the patch is wrong now. > > > > lspci gives: > > 0000:00:00.0 PCI bridge: Broadcom Corporation Device 8012 (rev 01) > > 0000:01:00.0 Network controller: Broadcom Corporation Device aa52 (rev 01) > > 0001:00:00.0 PCI bridge: Broadcom Corporation Device 8012 (rev 01) > > 0001:01:00.0 PCI bridge: PLX Technology, Inc. Device 8603 (rev ab) > > 0001:02:01.0 PCI bridge: PLX Technology, Inc. Device 8603 (rev ab) > > 0001:02:02.0 PCI bridge: PLX Technology, Inc. Device 8603 (rev ab) > > 0001:03:00.0 Network controller: Broadcom Corporation Device aa52 (rev 01) > > 0001:04:00.0 Network controller: Broadcom Corporation Device aa52 (rev 01) > > > > and a list of /sys/bus/pci/devices on a Vendor firmware install gives: > > 0000:00:00.0 0000:00:06.0 0000:00:0b.1 0000:00:11.0 0002:01:00.0 > > 0000:00:01.0 0000:00:07.0 0000:00:0c.0 0000:00:12.0 0002:02:01.0 > > 0000:00:02.0 0000:00:08.0 0000:00:0d.0 0000:00:13.0 0002:02:02.0 > > 0000:00:03.0 0000:00:09.0 0000:00:0e.0 0001:00:00.0 0002:03:00.0 > > 0000:00:04.0 0000:00:0a.0 0000:00:0f.0 0001:01:00.0 0002:04:00.0 > > 0000:00:05.0 0000:00:0b.0 0000:00:10.0 0002:00:00.0 > > Thanks for these information. > Without your patch the PCI subsystem will find lots of strange devices > and will report broken data and does not only show nothing, is that > correct? That's exactly so. And the bridge itself isn't recognised properly because of fixup needed at initial probe. > > > which looks like the topology is the same. > > > > So, possibly, my description of how I believe the devices are connected > > is accurate. > > > > bcm8012 > > ------------ > > | | > > aa52 pex8603 > > ------- > > | | > > aa52 aa52 > > _______________________________________________ openwrt-devel mailing list [email protected] https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
