Re: Call for e1000phy(4) testers.

On Friday 01 December 2006 03:01, Scott Long wrote:
> >   I have tried your e1000phy patch as well as msk.diff.HEAD on an Acer
> > Aspire 5583 WXMi laptop:
> > 
> > mskc0_at_pci2:0:0:    class=0x020000 card=0x01101025 chip=0x435211ab 
> > rev=0x14 hdr=0x00
> >     vendor   = 'Marvell Semiconductor (Was: Galileo Technology Ltd)'
> >     class    = network
> >     subclass = ethernet
> > 
> >   It seems that device_attach always returns 6 regardless 
> > hw.pci.enable_msi[x]
> > is 1 or 0:
> > 
> > mskc0: <Marvell Yukon 88E8038 Gigabit Ethernet> irq 10 at device 0.0 on 
> > pci2
> > mskc0: MSI count : 2
> > pcib2: mskc0 requested unsupported memory range 0-0xffffffff (decoding 
> > 0-0, 0-0)
> > mskc0: 0x4000 bytes of rid 0x10 res 3 failed (0, 0xffffffff).
> > mskc0: Lazy allocation of 0x4 bytes rid 0x14 type 4 at 0x1000
> > mskc0: unknown device: id=0xff, rev=0x0f
> > device_attach: mskc0 attach returned 6
> > 
> 
> This is a resource allocation problem with the PCI BAR on the card. 
> Either your BIOS isn't setting it up correctly, or FreeBSD is doing
> something freakishly wrong.  Does your BIOS have a switch for 'Plug N 
> Play OS" or something to that effect?

It looks like the PCI-PCI bridge has no resources assigned and I think we 
currently don't handle recursively walking up the tree to get resources.

-- 
John Baldwin