From: s-jaschke@t-online.de (Stefan Jaschke)
To: Francois Romieu <romieu@cogenit.fr>
Cc: linux-kernel@vger.kernel.org
Subject: Re: epic100 error
Date: Fri, 20 Apr 2001 13:30:59 +0200 [thread overview]
Message-ID: <01042013305902.07156@antares> (raw)
In-Reply-To: <20010417184552.A6727@core.devicen.de> <01042010222601.06730@antares> <20010420122507.A32759@se1.cogenit.fr>
In-Reply-To: <20010420122507.A32759@se1.cogenit.fr>
On Friday 20 April 2001 12:25, Francois Romieu wrote:
> Summary:
> Arnd Bergmann:
> orig epic100 "DMA mapped epic100 (any version)"
> (<=2.4.0-ac9)
> VT8363 ok fscked but ok after bios update
>
> Daniel Nofftz:
> 2.4.2 2.4.3
> VT82C595 ok fscked. (no mention of bios experience)
>
> Oliver Teuber:
> 2.2.19 2.4.3-ac7
> VT82C598 ok fscked
>
> Romieu:
> 2.2.xx 2.4.[123]
> 82443BX ok ok
Stefan Jaschke:
2.2.xx 2.4.0 2.4.3 2.4.4-pre4
AMD 761 ok ok fails fails
# lspci
00:01.0 PCI bridge: Advanced Micro Devices [AMD] AMD-751 [Irongate] AGP Bridge (rev 01)
00:08.0 Ethernet controller: Standard Microsystems Corp [SMC] 83C170QF (rev 08)
> What happen's if you compile 2.4.2 epic100 driver in a 2.4.3 tree (I) ?
I'll try this asap.
Stefan
--
Stefan R. Jaschke <stefan@jaschke-net.de>
http://www.jaschke-net.de
next prev parent reply other threads:[~2001-04-20 11:31 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-17 16:45 epic100 error Oliver Teuber
2001-04-17 20:34 ` Stefan Jaschke
[not found] ` <20010418204021.A14531@se1.cogenit.fr>
2001-04-20 8:22 ` Stefan Jaschke
2001-04-20 10:25 ` Francois Romieu
2001-04-20 11:30 ` Stefan Jaschke [this message]
2001-04-20 14:05 ` Stefan Jaschke
2001-04-20 14:33 ` Francois Romieu
2001-04-20 15:57 ` Stefan Jaschke
2001-04-20 16:45 ` Francois Romieu
2001-04-20 20:13 ` Stefan Jaschke
2001-04-20 11:09 ` Stefan Jaschke
2001-04-20 11:33 ` Jeff Garzik
2001-04-20 12:07 ` Stefan Jaschke
2001-04-20 8:14 ` Arnaldo Carvalho de Melo
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=01042013305902.07156@antares \
--to=s-jaschke@t-online.de \
--cc=linux-kernel@vger.kernel.org \
--cc=romieu@cogenit.fr \
--cc=stefan@jaschke-net.de \
/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