public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@mandrakesoft.com>
To: Roberto Nibali <ratz@tac.ch>
Cc: Ion Badulescu <ionut@cs.columbia.edu>,
	linux-kernel@vger.kernel.org, Donald Becker <becker@scyld.com>,
	Andrew Morton <andrewm@uow.edu.au>
Subject: Re: Fix for Donald Becker's DP83815 network driver (v1.07)
Date: Fri, 20 Apr 2001 12:19:49 -0400	[thread overview]
Message-ID: <3AE061A5.FDB4CD5C@mandrakesoft.com> (raw)
In-Reply-To: <Pine.LNX.4.33.0104200301380.5165-100000@age.cs.columbia.edu> <3AE05F5A.7942C824@tac.ch>

Roberto Nibali wrote:
> 
> > This was a special case, which btw had nothing to do with the starfire
> > driver itself. The user needed to support more than 8 eth ports, which
> > 2.2 complains about, and more than 16 eth ports, which 2.2 simply doesn't
> > allow without further changes.
> 
> I made the changes and I was able to load 4 quadboards, 2 3com cards and
> 1 eepro100 (onboard) and I did some tests and it works fine. However the
> starfire driver seems not to initialize more then 4 quadboards. I put in
> 5 and he doesn't initialize it and the others don't work although they
> get initialized.

If all five show up in 'lspci', then starfire driver should be able to
register all five.  [if it doesn't, it is probably a starfire bug]

If only four show up in lspci, that sounds more like a PCI core problem

-- 
Jeff Garzik      | The difference between America and England is that
Building 1024    | the English think 100 miles is a long distance and
MandrakeSoft     | the Americans think 100 years is a long time.
                 |      (random fortune)

  reply	other threads:[~2001-04-20 16:20 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-04-17 15:58 Fix for Donald Becker's DP83815 network driver (v1.07) Steve Hill
2001-04-17 16:16 ` Roberto Nibali
2001-04-17 16:30   ` Steve Hill
2001-04-17 17:12     ` Roberto Nibali
2001-04-18 10:25     ` Ion Badulescu
2001-04-18 11:32       ` Steve Hill
2001-04-18 15:14         ` Tim Hockin
2001-04-18 20:33         ` Ion Badulescu
2001-04-18 20:40           ` Steve Hill
2001-04-19 10:54           ` Roberto Nibali
2001-04-19 13:06           ` Roberto Nibali
2001-04-20  5:48             ` Ion Badulescu
2001-04-20  6:30               ` Jeff Garzik
2001-04-20  7:09                 ` Ion Badulescu
2001-04-20  7:31                   ` Jeff Garzik
2001-04-20  9:49                     ` Ion Badulescu
2001-04-20  9:57                       ` Jeff Garzik
2001-04-20 10:05                         ` Ion Badulescu
2001-04-20 16:10                           ` Roberto Nibali
2001-04-20 16:19                             ` Jeff Garzik [this message]
2001-04-20 16:50                               ` Roberto Nibali
2001-04-20 19:27                                 ` Ion Badulescu
2001-04-20  9:03               ` Roberto Nibali
2001-04-20  9:42                 ` Ion Badulescu
2001-04-20 10:12                   ` Roberto Nibali

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=3AE061A5.FDB4CD5C@mandrakesoft.com \
    --to=jgarzik@mandrakesoft.com \
    --cc=andrewm@uow.edu.au \
    --cc=becker@scyld.com \
    --cc=ionut@cs.columbia.edu \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ratz@tac.ch \
    /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