Ivan Kokshaysky wrote:
Actually, it should be something like this (also untested).
Ivan.
--- a/drivers/pci/quirks.c
+++ b/drivers/pci/quirks.c
@@ -1690,6 +1690,14 @@ static void __devinit quirk_p64h2_1k_io(struct pci_dev
*dev)
}
DECLARE_PCI_FIXUP_HEADER(PCI_VENDOR_ID_INTEL, 0x1460,
On Wed, May 23, 2007 at 08:10:54PM -0700, Jesse Barnes wrote:
> > +/* Give unknown D-Link network adapters a proper class */
> > +static void __devinit quirk_dlink_unknown(struct pci_dev *dev)
> > +{
> > + if (dev->class = PCI_CLASS_UNKNOWN)
>
> Err, == of course. Obviously I didn't test this.
On Wednesday, May 23, 2007 8:08:23 Jesse Barnes wrote:
> On Wednesday, May 23, 2007 5:20:46 Wayne Sherman wrote:
> > Ivan Kokshaysky wrote:
> > > No, it won't help. The 1M range (ff50-ff5f) is more than
> > > enough.
> >
> > Good catch, I didn't look close enough at the allocations of the d
On Wednesday, May 23, 2007 5:20:46 Wayne Sherman wrote:
> Ivan Kokshaysky wrote:
> > No, it won't help. The 1M range (ff50-ff5f) is more than enough.
>
> Good catch, I didn't look close enough at the allocations of the devices
> under the bridge.
>
> > The reason why the D-Link resource is
Ivan Kokshaysky wrote:
No, it won't help. The 1M range (ff50-ff5f) is more than enough.
Good catch, I didn't look close enough at the allocations of the devices
under the bridge.
The reason why the D-Link resource is not getting assigned is rather
interesting: as Wayne wrote
Here
On Tue, May 22, 2007 at 04:31:22PM -0700, Jesse Barnes wrote:
> On Tuesday, May 22, 2007, Wayne Sherman wrote:
> > If so, the D-Link is not being mapped into the
> > right region, and the bridge it is behind does not have enough memory
> > assigned to it (ff50-ff5f : PCI Bus #02).
>
> Sou
On Tuesday, May 22, 2007, Wayne Sherman wrote:
> So these devices are already occupying the space that the D-Link wants:
>
> 00:01.0 PCI bridge: ATI Technologies Inc RS480 PCI Bridge
> 01:05.0 VGA compatible controller: ATI Technologies Inc RS482 [Radeon
> Xpress 200]
>
> But, the D-Link NIC is beh
Jesse Barnes wrote:
Can you dump the memory BAR for this device? I guess lspci hides it by
default. You may also be able to see it using 'od -t
x4 /sys/devices/pci\:00/:02:02.0/config'.
The D-Link NIC is sitting behind this bridge:
"00:14.4 PCI bridge: ATI Technologies Inc SB600 PC
On Monday, May 21, 2007, Wayne Sherman wrote:
> Jesse Barnes wrote:
> > There's a recent thread about PCI resource assignment (sounds like
> > your BIOS might be buggy btw, or you're somehow running out of space),
> > search for the title "PCI bridge range sizing bug". You may need the
> > kernel
Jesse Barnes wrote:
There's a recent thread about PCI resource assignment (sounds like your
BIOS might be buggy btw, or you're somehow running out of space), search
for the title "PCI bridge range sizing bug". You may need the kernel to
reassign the resource for your NIC before you can use it.
On Monday, May 21, 2007, System Design Works wrote:
> The kernel has a problem allocating resources for my PCI NIC. Here is
> what the kernel is reporting:
>
> # uname -a
> Linux wopr 2.6.20-gentoo-r8 #7 SMP Sun May 20 20:56:56 PDT 2007 i686 AMD
> Athlon(tm) 64 X2 Dual Core Processor 3800+ Authent
11 matches
Mail list logo
