mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Adam Lackorzynski <al10@inf.tu-dresden.de>
To: Martin Mares <mj@suse.cz>
Cc: Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] PCI-Devices and ServerWorks chipset
Date: Tue, 23 Jan 2001 19:18:34 +0100	[thread overview]
Message-ID: <20010123191834.E15427@inf.tu-dresden.de> (raw)
In-Reply-To: <20010116181207.A1325@inf.tu-dresden.de> <20010117095221.A553@albireo.ucw.cz>
In-Reply-To: <20010117095221.A553@albireo.ucw.cz>; from mj@suse.cz on Wed, Jan 17, 2001 at 09:52:21AM +0100

On Wed Jan 17, 2001 at 09:52:21 +0100, Martin Mares wrote:
> Hello!
> 
> > The patch below (against vanilla 2.4.0) makes Linux recognize
> > PCI-Devices sitting in another PCI bus than 0 (or 1).
> > 
> > This was tested on a Netfinity 7100-8666 using a ServerWorks chipset.
> 
> I don't have the ServerWorks chipset documentation at hand, but I think your
> patch is wrong -- it doesn't make any sense to scan a bus _range_. The registers

Another possible workaround for my problem is just not to call the
fixup routine for the chipset:

--- pci-pc.c~    Thu Jun 22 16:17:16 2000
+++ pci-pc.c    Tue Jan 23 18:46:55 2001
@@ -927,7 +927,6 @@
 struct pci_fixup pcibios_fixups[] = {
        { PCI_FIXUP_HEADER,     PCI_VENDOR_ID_INTEL,    PCI_DEVICE_ID_INTEL_82451NX,    pci_fixup_i450nx },
        { PCI_FIXUP_HEADER,     PCI_VENDOR_ID_INTEL,    PCI_DEVICE_ID_INTEL_82454GX,    pci_fixup_i450gx },
-       { PCI_FIXUP_HEADER,     PCI_VENDOR_ID_SERVERWORKS,      PCI_DEVICE_ID_SERVERWORKS_HE,           pci_fixup_serverworks },
        { PCI_FIXUP_HEADER,     PCI_VENDOR_ID_SERVERWORKS,      PCI_DEVICE_ID_SERVERWORKS_LE,           pci_fixup_serverworks },
        { PCI_FIXUP_HEADER,     PCI_VENDOR_ID_SERVERWORKS,      PCI_DEVICE_ID_SERVERWORKS_CMIC_HE,      pci_fixup_serverworks },
        { PCI_FIXUP_HEADER,     PCI_VENDOR_ID_COMPAQ,   PCI_DEVICE_ID_COMPAQ_6010,      pci_fixup_compaq },

This patch is against 2.4.0-ac10. Having the above line in the PCI devices do
not occur, leaving it out they appear.



Adam
-- 
Adam                 al10@inf.tu-dresden.de
  Lackorzynski         http://a.home.dhs.org
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

      parent reply	other threads:[~2001-01-23 18:18 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-01-16 17:12 Adam Lackorzynski
2001-01-17  8:52 ` Martin Mares
2001-01-17 10:14   ` Adam Lackorzynski
2001-01-17 11:25   ` Maciej W. Rozycki
2001-01-17 21:17     ` Dan Hollis
2001-01-18  8:37       ` Maciej W. Rozycki
2001-01-18 10:01         ` Andre Hedrick
2001-01-18 11:08           ` Maciej W. Rozycki
2001-01-18 17:40             ` Andre Hedrick
2001-01-19 12:24               ` Maciej W. Rozycki
2001-01-23  3:01     ` Tim Hockin
2001-02-08  8:34       ` Martin Mares
2001-01-23 18:18   ` Adam Lackorzynski [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20010123191834.E15427@inf.tu-dresden.de \
    --to=al10@inf.tu-dresden.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mj@suse.cz \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®