From: Petr Vandrovec <vandrove@vc.cvut.cz>
To: Carsten Langgaard <carstenl@mips.com>
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 11:27:47 -0700 [thread overview]
Message-ID: <3ACCB923.645F42E4@vc.cvut.cz> (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> <2001040423 <3ACC1E35.4D2F7506@mips.com>
Carsten Langgaard wrote:
>
> Petr Vandrovec wrote:
> > 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
> 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.
Oops. I misinterpreted what code does. Really stupid hardware.
Thanks,
Petr Vandrovec
vandrove@vc.cvut.cz
prev parent reply other threads:[~2001-04-05 18: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
2001-04-05 7:15 ` Carsten Langgaard
[not found] ` <2001040423 <3ACC1E35.4D2F7506@mips.com>
2001-04-05 18:27 ` Petr Vandrovec [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=3ACCB923.645F42E4@vc.cvut.cz \
--to=vandrove@vc.cvut.cz \
--cc=carstenl@mips.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tsbogend@alpha.franken.de \
--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