public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@mandrakesoft.com>
To: Michal Jaegermann <michal@harddata.com>
Cc: brian@worldcontrol.com, linux-kernel@vger.kernel.org
Subject: Re: tulip driver again
Date: Fri, 29 Mar 2002 14:28:38 -0500	[thread overview]
Message-ID: <3CA4C066.3020509@mandrakesoft.com> (raw)
In-Reply-To: <20020328174724.A24374@mail.harddata.com> <20020329024021.GA2887@top.worldcontrol.com> <20020328215744.A25760@mail.harddata.com>

Michal Jaegermann wrote:

>On Thu, Mar 28, 2002 at 06:40:21PM -0800, brian@worldcontrol.com wrote:
>
>>On Thu, Mar 28, 2002 at 05:47:24PM -0700, Michal Jaegermann wrote:
>>
>>>I know that this is boring and a number of my earlier reports was
>>>apparently ignored
>>>
>>There is a tulip specific discussion list, which may explain why you
>>get ignored on this forum.
>>
>
>Well, in a due time I filed pretty detailed bug reports, with dumps
>of PCI space from older working and non-working drivers and what not,
>on sourceforge where presumably a development of this driver was going.
>This was ignored there as well.
>

Currently the tulip driver is very stable for a large number of 
chipsets, but not all of them.  And there are some problems like, 
"calling this function with 1 as argument, and some chipsets work. 
 calling this function with 0 as argument, and that breaks some chipsets 
but then other chipsets are fixed."

The temporary solution is to use the latest _stable_ version of the 
driver, on http://sf.net/projects/tulip/ or use the de4x5 driver.  I am 
working on the long term solution, which is fixing the link state 
machine in the driver to actually be (a) sane and (b) workable for all 
chipsets.

This work is going to be merged into 2.5.x series _first_, then after 
it's proven stable merged back into 2.4.x as a solution for all.  But 
this takes time... in the meantime, there are the temporary solutions 
mentioned to get you by.

    Jeff







  reply	other threads:[~2002-03-29 19:30 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-03-29  0:47 tulip driver again Michal Jaegermann
2002-03-29  2:40 ` brian
2002-03-29  4:57   ` Michal Jaegermann
2002-03-29 19:28     ` Jeff Garzik [this message]
2002-03-30  0:27 ` David Ford
2002-03-30  7:38   ` Jeff Garzik
     [not found] <483868577@toto.iv>
2002-04-02  0:45 ` Peter Chubb

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=3CA4C066.3020509@mandrakesoft.com \
    --to=jgarzik@mandrakesoft.com \
    --cc=brian@worldcontrol.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=michal@harddata.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