mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Albert D. Cahalan" <acahalan@cs.uml.edu>
To: trini@kernel.crashing.org (Tom Rini)
Cc: acahalan@cs.uml.edu (Albert D. Cahalan), linux-kernel@vger.kernel.org
Subject: Re: tulip driver problem
Date: Mon, 6 Aug 2001 16:16:48 -0400 (EDT)	[thread overview]
Message-ID: <200108062016.f76KGmG117015@saturn.cs.uml.edu> (raw)
In-Reply-To: <20010806100319.C833@cpe-24-221-152-185.az.sprintbbd.net> from "Tom Rini" at Aug 06, 2001 10:03:19 AM

Tom Rini writes:
> On Mon, Aug 06, 2001 at 12:19:10PM -0400, Albert D. Cahalan wrote:

>> This is the Force PowerCore 6750 single-board computer with
>> a PowerPC processor and the DEC 21143 Ethernet chip.
>
> Just wondering, but when booting 2.4.x, do you see something like:
> "Unknown bridge resource %d: assuming transparent"
> for the tulip?

Nope. The closest is "Memory resource not set for host bridge 0".

This is the VME 6750 BTW, not the CompactPCI 6750.
I'll put my IRQ table adjustments below, in case they are wrong.

Right now, a 2.4.8-pre4 boot gives this:

ip_conntrack (2048 buckets, 16384 max)
ip_tables: (c)2000 Netfilter core team
NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.
Looking up port of RPC 100003/2 on 172.16.101.112
eth0: Setting half-duplex based on MII#1 link partner capability of 0021.
NETDEV WATCHDOG: eth0: transmit timed out
NETDEV WATCHDOG: eth0: transmit timed out
NETDEV WATCHDOG: eth0: transmit timed out
NETDEV WATCHDOG: eth0: transmit timed out

That "eth0: Setting half-duplex" line doesn't show if I use the
other driver or forget to adjust the IRQ mappings; the rest is
the same no matter what.


        static char pci_irq_table[][4] =
        /*
         *      PCI IDSEL/INTPIN->INTLINE
         *      A       B       C       D
         */
        {
                {11,    14,     5,      10},    /* IDSEL 24 - Universe II */
                {0,     0,      0,      0},     /* IDSEL 25 - unused */
                {10,    11,     14,     5},     /* IDSEL 26 - Winbond */
                {10,    11,     14,     5},     /* IDSEL 27 - DEC 21143 */
                {14,    5,      10,     11},    /* IDSEL 28 - PMC I */
                {11,    14,     5,      10},    /* IDSEL 29 - PMC II */
                {0,     0,      0,      0},     /* IDSEL 30 - unused */
#if 0
                {9,     10,     11,     12},    /* IDSEL 24 - DEC 21554 */
                {10,    0,      0,      0},     /* IDSEL 25 - DEC 21143 */
                {11,    12,     9,      10},    /* IDSEL 26 - PMC I */
                {12,    9,      10,     11},    /* IDSEL 27 - PMC II */
                {0,     0,      0,      0},     /* IDSEL 28 - unused */
                {0,     0,      9,      0},     /* IDSEL 29 - unused */
                {0,     0,      0,      0},     /* IDSEL 30 - Winbond */
#endif
                };

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

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-06 16:19 Albert D. Cahalan
2001-08-06 17:03 ` Tom Rini
2001-08-06 20:16   ` Albert D. Cahalan [this message]
2001-08-07 10:44     ` Lech Szychowski
2001-08-07 14:59       ` Colonel
2001-08-06 16:35 chen, xiangping
2001-08-07  2:32 Colonel
2001-08-07  3:44 ` Tom Rini

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=200108062016.f76KGmG117015@saturn.cs.uml.edu \
    --to=acahalan@cs.uml.edu \
    --cc=linux-kernel@vger.kernel.org \
    --cc=trini@kernel.crashing.org \
    /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®