public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@mandrakesoft.com>
To: Juergen Wolf <JuWo@N-Club.de>
Cc: Francois Romieu <romieu@cogenit.fr>, linux-kernel@vger.kernel.org
Subject: Re: Problem with SMC Etherpower II + kernel newer 2.4.2
Date: Fri, 06 Jul 2001 08:34:18 -0400	[thread overview]
Message-ID: <3B45B04A.9A85ECA0@mandrakesoft.com> (raw)
In-Reply-To: <Pine.LNX.4.30.0107021014230.15054-100000@flash.datafoundation.com> <3B42DEC2.AAB1E65B@N-Club.de> <20010704145752.A29311@se1.cogenit.fr> <3B456D45.FBF10C1A@N-Club.de> <20010706134421.B20614@se1.cogenit.fr> <3B45AEBD.8D0599E3@N-Club.de>

Juergen Wolf wrote:
> 
> Francois Romieu wrote:
> >
> > Could you try 2.4.6 with just this modification: ?
> >
> 
> hm, looks like thats really the point. After applying your diff file
> everything works fine.

Does it work with this line?

outl(0x12, ioaddr + MIICfg);

-- 
Jeff Garzik      | A recent study has shown that too much soup
Building 1024    | can cause malaise in laboratory mice.
MandrakeSoft     |

  reply	other threads:[~2001-07-06 12:34 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-07-02 11:55 Problem with SMC Etherpower II + kernel newer 2.4.2 Juergen Wolf
2001-07-02 14:18 ` John Jasen
2001-07-04  9:15   ` Juergen Wolf
2001-07-04 12:57     ` Francois Romieu
2001-07-06  7:48       ` Juergen Wolf
2001-07-06 11:44         ` Francois Romieu
2001-07-06 12:27           ` Juergen Wolf
2001-07-06 12:34             ` Jeff Garzik [this message]
2001-07-06 12:51               ` Juergen Wolf
2001-07-06 12:59             ` [PATCH] " Jeff Garzik
2001-07-06 15:04               ` Francois Romieu
2001-07-03  9:31 ` Florian Schmitt
2001-07-03 14:57   ` Olivier Sessink
2001-07-04  9:19   ` Francois Romieu
2001-07-04 15:30     ` Florian Schmitt

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=3B45B04A.9A85ECA0@mandrakesoft.com \
    --to=jgarzik@mandrakesoft.com \
    --cc=JuWo@N-Club.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=romieu@cogenit.fr \
    /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