From: Carsten Langgaard <carstenl@mips.com>
To: Petr Vandrovec <vandrove@vc.cvut.cz>
Cc: Thomas Bogendoerfer <tsbogend@alpha.franken.de>,
Wade Hampton <whampton@staffnet.com>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: pcnet32 (maybe more) hosed in 2.4.3
Date: Thu, 05 Apr 2001 09:26:45 +0200 [thread overview]
Message-ID: <3ACC1E35.4D2F7506@mips.com> (raw)
In-Reply-To: <20010330190137.A426@indiana.edu> <Pine.LNX.4.30.0103311541300.406-100000@fs131-224.f-secure.com> <20010403202127.A316@bacchus.dhis.org> <3ACB2323.C1653236@mips.com> <3ACB3CA5.D978EF41@staffnet.com> <3ACB8098.DFEC12D7@vc.cvut.cz> <20010404235124.B3102@alpha.franken.de> <3ACBACA5.889ECF7E@vc.cvut.cz>
Petr Vandrovec wrote:
> Thomas Bogendoerfer wrote:
> >
> > On Wed, Apr 04, 2001 at 01:14:16PM -0700, Petr Vandrovec wrote:
> > > VMware is working on implementation PCnet 32bit mode in emulation (there
> > > is no such thing now because of no OS except FreeBSD needs it). But
> > > my question is - is there some real benefit in running chip in
> > > 32bit mode?
> >
> > probably not.
> >
> > > so is 32bit mode needed for bigendian ports, or what's reasoning
> > > behind it?
> >
> > I've added 32bit mode for some IBM PowerPC machines. The firmware
> > on this machines setup the chip to DWIO and I haven't found a way
> > to switch it back to WIO.
>
> Current Linux driver switches them to 16bit mode in pcnet_probe1:
>
> pcnet_dwio_reset(); // reset to 16bit mode when in 32bit, ignore in
> 16bit mode
> pcnet_wio_reset(); // device is for sure in 16bit mode, but reset it
> again to
> // get it into known state if we were in 16bit mode
> already
>
> So you should find hardware always in 16bit mode at this point. If it
> does not work, maybe you need to xor PCNET32_WIO_* values with 2 on
> PowerPC...
I'm afraid that's not true.
The above only do a software reset and that doesn't effect the I/O mode.
Only a hardware reset effects the I/O mode.
An because any firmware might changes to 32bit mode after reset (of the whole
system), we need to support both modes.
>
> Best regards,
> Petr Vandrovec
> vandrove@vc.cvut.cz
--
_ _ ____ ___ Carsten Langgaard Mailto:carstenl@mips.com
|\ /|||___)(___ MIPS Denmark Direct: +45 4486 5527
| \/ ||| ____) Lautrupvang 4B Switch: +45 4486 5555
TECHNOLOGIES 2750 Ballerup Fax...: +45 4486 5556
Denmark http://www.mips.com
next prev parent reply other threads:[~2001-04-05 7:29 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-31 0:01 pcnet32 (maybe more) hosed in 2.4.3 Scott G. Miller
2001-03-31 0:36 ` Jeff Garzik
2001-03-31 13:58 ` Szabolcs Szakacsits
2001-04-03 18:21 ` Ralf Baechle
2001-04-04 13:35 ` Carsten Langgaard
2001-04-04 15:24 ` Wade Hampton
2001-04-04 20:14 ` Petr Vandrovec
2001-04-04 21:51 ` Thomas Bogendoerfer
2001-04-04 23:22 ` Petr Vandrovec
2001-04-05 7:26 ` Carsten Langgaard [this message]
2001-04-05 7:15 ` Carsten Langgaard
[not found] ` <2001040423 <3ACC1E35.4D2F7506@mips.com>
2001-04-05 18:27 ` Petr Vandrovec
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=3ACC1E35.4D2F7506@mips.com \
--to=carstenl@mips.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tsbogend@alpha.franken.de \
--cc=vandrove@vc.cvut.cz \
--cc=whampton@staffnet.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