linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: malware@t-online.de (Michael Mueller)
To: mj@ucw.cz, linux-kernel@vger.kernel.org
Subject: Re: [2.4] PCI chipset Opti Viper M/N+
Date: Fri, 24 Oct 2003 13:38:23 +0200	[thread overview]
Message-ID: <200310241136.NAA30555@fire.malware.de> (raw)
In-Reply-To: md5:FBD343F3435F79857BDF1297AFE82D42

Hi Martin and linux-kernel readers,

I wrote:
> it should read:
>    val |= newval << (3*(pirq-1));
> 
> With this changed it still works with the PCMCIA card, but I still need
> to gain access to a CardBus card to test it with.

Ok, tested it with a LevelOne 10/100MBit CardBus card in a local
computer store. It works fine.


Michael

-- 
Linux@TekXpress
http://www-users.rwth-aachen.de/Michael.Mueller4/tekxp/tekxp.html

      parent reply	other threads:[~2003-10-24 11:38 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-24  9:56 [2.4] PCI chipset Opti Viper M/N+ Malware
2003-10-24 10:12 ` Michael Mueller
     [not found] ` <md5:FBD343F3435F79857BDF1297AFE82D42>
2003-10-24 11:38   ` Michael Mueller [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=200310241136.NAA30555@fire.malware.de \
    --to=malware@t-online.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mj@ucw.cz \
    /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;
as well as URLs for NNTP newsgroup(s).