linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "David S. Miller" <davem@dm.cobaltmicro.com>
To: Geert.Uytterhoeven@cs.kuleuven.ac.be
Cc: davies@maniac.ultranet.com, becker@cesdis1.gsfc.nasa.gov,
	linux-kernel@vger.rutgers.edu, linuxppc-dev@lists.linuxppc.org
Subject: Re: de4x5 vs. tulip on PPC
Date: Wed, 20 Jan 1999 23:58:04 -0800	[thread overview]
Message-ID: <199901210758.XAA14846@dm.cobaltmicro.com> (raw)
In-Reply-To: <Pine.LNX.4.03.9901202221410.28223-100000@mercator.cs.kuleuven.ac.be> (message from Geert Uytterhoeven on Wed, 20 Jan 1999 22:28:13 +0100 (CET))


   Date: 	Wed, 20 Jan 1999 22:28:13 +0100 (CET)
   From: Geert Uytterhoeven <Geert.Uytterhoeven@cs.kuleuven.ac.be>

   On my machine, de4x5.c works, while tulip.c doesn't.

   Machine is a CHRP/PPC box, Ethernet is 21041 based D-Link DE-530CT.

 ...

   So at least the Ethernet HW address is in the wrong endiannes for tulip.c.

   Are there people who can use tulip.c on a big endian machine?

Nope, I gave up a long time ago using anything other than de4x5.c on
sparc machines. 

Later,
David S. Miller
davem@dm.cobaltmicro.com

[[ This message was sent via the linuxppc-dev mailing list. Replies are ]]
[[ not forced back to the list, so be sure to  Cc linuxppc-dev  if your ]]
[[ reply is of general interest. To unsubscribe from linuxppc-dev, send ]]
[[ the message 'unsubscribe' to linuxppc-dev-request@lists.linuxppc.org ]]

  reply	other threads:[~1999-01-21  7:58 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-01-20 21:28 de4x5 vs. tulip on PPC Geert Uytterhoeven
1999-01-21  7:58 ` David S. Miller [this message]
1999-01-21 17:32 ` Alain RICHARD

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=199901210758.XAA14846@dm.cobaltmicro.com \
    --to=davem@dm.cobaltmicro.com \
    --cc=Geert.Uytterhoeven@cs.kuleuven.ac.be \
    --cc=becker@cesdis1.gsfc.nasa.gov \
    --cc=davies@maniac.ultranet.com \
    --cc=linux-kernel@vger.rutgers.edu \
    --cc=linuxppc-dev@lists.linuxppc.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;
as well as URLs for NNTP newsgroup(s).