public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@mandrakesoft.com>
To: Matthias Andree <matthias.andree@stud.uni-dortmund.de>
Cc: Linux-Kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: 2.4.5 still breaks dhcpcd with 8139too
Date: Fri, 01 Jun 2001 13:44:17 -0400	[thread overview]
Message-ID: <3B17D471.D636E208@mandrakesoft.com> (raw)
In-Reply-To: <20010529215647.A3955@greenhydrant.com> <3B147F80.31EC7520@mandrakesoft.com> <20010531104437.C10057@emma1.emma.line.org>

Matthias Andree wrote:
> 
> On Wed, 30 May 2001, Jeff Garzik wrote:
> 
> > > I see that Alan has reverted back to the 2.4.3 driver for his ac-series for
> > > other reasons, hopefully either the old driver will going in to 2.4.6 or the
> > > new one will get fixed?
> >
> > I've got one of the two problems fixed here at the test lab, and am
> > working on the second.  Hopefully this week I'll have this sorted out,
> > and a driver for you guys to test.
> 
> Will that 8139too be able to share its IRQ with a bttv card (Hauppauge
> WinTV in my case)? With 2.2.19, it's currently possible, at least after
> unloading and reloading the 8139too module, but it's a no-go with 2.4.5.

Can you be more explicit than "no-go"?  8139too should share interrupts
just fine.

-- 
Jeff Garzik      | Disbelief, that's why you fail.
Building 1024    |
MandrakeSoft     |

  reply	other threads:[~2001-06-01 17:44 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-05-30  4:56 2.4.5 still breaks dhcpcd with 8139too David Rees
2001-05-30  5:05 ` Jeff Garzik
2001-05-30  5:21   ` David Rees
2001-05-31  8:44   ` Matthias Andree
2001-06-01 17:44     ` Jeff Garzik [this message]
2001-06-01 18:31       ` Matthias Andree
2001-06-06 23:52         ` RTL8139, IRQ sharing, etc Matthias Andree

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=3B17D471.D636E208@mandrakesoft.com \
    --to=jgarzik@mandrakesoft.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=matthias.andree@stud.uni-dortmund.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