From: Jan-Benedict Glaw <jbglaw@lug-owl.de>
To: Jim Gifford <maillist@jg555.com>
Cc: Linux MIPS List <linux-mips@linux-mips.org>
Subject: Re: 64bit compile of tulip driver
Date: Tue, 29 Mar 2005 21:52:08 +0200 [thread overview]
Message-ID: <20050329195208.GH17725@lug-owl.de> (raw)
In-Reply-To: <4249A5EE.9070006@jg555.com>
[-- Attachment #1: Type: text/plain, Size: 1278 bytes --]
On Tue, 2005-03-29 11:01:02 -0800, Jim Gifford <maillist@jg555.com>
wrote in message <4249A5EE.9070006@jg555.com>:
> Under 32bit the tulip driver works fine, but under 64 bit it gives me a
> lot of grief.
>
> First off it continually sends data out the network interface and never
> negotiates is speed and duplex.
> Second in the log files all I see is an uninformative message
> 0000:00:07.0: tulip_stop_rxtx() failed
>
> Here is all the bootup information differences I can find on the driver
> 64 bit
> Dec 31 16:01:29 lfs tulip0: ***WARNING***: No MII transceiver found!
> Dec 31 16:01:29 lfs tulip1: ***WARNING***: No MII transceiver found!
> 32 bit
> Dec 31 16:01:16 lfs tulip0: MII transceiver #1 config 1000 status 7809
> advertising 01e1
> Dec 31 16:01:16 lfs tulip1: MII transceiver #1 config 1000 status 7809
> advertising 01e1.
That's all wrongly wrapped around. However, where's the patch?
MfG, JBG
--
Jan-Benedict Glaw jbglaw@lug-owl.de . +49-172-7608481 _ O _
"Eine Freie Meinung in einem Freien Kopf | Gegen Zensur | Gegen Krieg _ _ O
fuer einen Freien Staat voll Freier Bürger" | im Internet! | im Irak! O O O
ret = do_actions((curr | FREE_SPEECH) & ~(NEW_COPYRIGHT_LAW | DRM | TCPA));
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
prev parent reply other threads:[~2005-03-29 19:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-29 19:01 64bit compile of tulip driver Jim Gifford
2005-03-29 19:52 ` Jan-Benedict Glaw [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=20050329195208.GH17725@lug-owl.de \
--to=jbglaw@lug-owl.de \
--cc=linux-mips@linux-mips.org \
--cc=maillist@jg555.com \
/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