Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@pobox.com>
To: Andrew Morton <akpm@osdl.org>
Cc: Martin Michlmayr <tbm@cyrius.com>,
	linux-mips@linux-mips.org, grundler@parisc-linux.org
Subject: Re: Tulip RaQ2 64 Bit Fix
Date: Mon, 16 Jan 2006 20:36:55 -0500	[thread overview]
Message-ID: <43CC4A37.9050502@pobox.com> (raw)
In-Reply-To: <20060116172320.1e6d3cfd.akpm@osdl.org>

Andrew Morton wrote:
> Martin Michlmayr <tbm@cyrius.com> wrote:
> 
>>* Jim Gifford <maillist@jg555.com> [2006-01-16 08:27]:
>>
>>>>>>The attached patch allows the tulip driver to work with the RaQ2's
>>>>>>network adapter. Without the patch under a 64 bit build, it will
>>>>>>never negotiate and will drop packets. This driver is part of
>>>>>>Linux Parisc, by Grant Grundler. It's currently in -mm, but Jeff
>>>>>>Garzick will not apply it to the main tree.
>>>>>>     
>>>>>
>>>>>Why?
>>>
>>>Jeff Garzick refuses to apply it do to spinlocks. Andrew Morton is
>>>including in his tree because it fixes issue with Parisc and with
>>>MIPS based builds. So it's kinda of what is the right thing to do. I
>>>also use this driver on my x86 builds, and it actually performs
>>>better. Here is a little history of how Grant made the driver.
>>>
>>>Grant Grundler is the network maintainer for Parisc Linux.  He
>>>discovered that the tulip driver didn't perform that well. He
>>>researched the manufactures documentation and found out how to fix
>>>the driver to work to its optimum performance. He did this back in
>>>2003, has submitted it to Jeff Garzick several times with no
>>>response. Around late 2004, I started to do test builds on 64 bit on
>>>my RaQ2 and discovered that the driver would not auto-negotiate
>>>transfer speeds. Talked to numerous people, then someone put me in
>>>touch with Grant. I tested the driver for about 2 weeks, ask Grant
>>>why it wasn't sent upstream, he told me about the spinlock issue. I
>>>then contacted Andrew Morton, explained everything as I am here, and
>>>he agreed it was needed and tried to get Jeff to add it. Jeff sends
>>>back a one liner say doing to it's use of spinlocks it's not
>>>accepted.
>>
>>Andrew, do you think that issue will be resolved in some way at some
>>point?
>>
> 
> 
> This has been hanging around for too long.  We need to get it over the hump.
> 
> Jeff, can you please suggest how this patch should be altered to make it
> acceptable?

Answer hasn't changed since this was last discussed:  sleep, rather than 
delay for an extra-long time.  That's the only hurdle for the tulip 
patches you keep resending.

Francois Romieu even had an untested patch that attempted this, somewhere.

	Jeff

  reply	other threads:[~2006-01-17  1:33 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-05  5:18 Tulip RaQ2 64 Bit Fix Jim Gifford
2005-12-05 11:44 ` Ralf Baechle
2006-01-16 16:03   ` Martin Michlmayr
2006-01-16 16:27     ` Jim Gifford
2006-01-16 16:58       ` Martin Michlmayr
2006-01-17  1:23         ` Andrew Morton
2006-01-17  1:36           ` Jeff Garzik [this message]
2006-01-17  2:35             ` Grant Grundler
2006-01-17  2:29               ` Andrew Morton
2006-01-17  2:29                 ` Andrew Morton
2006-01-16 20:35       ` Grant Grundler

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=43CC4A37.9050502@pobox.com \
    --to=jgarzik@pobox.com \
    --cc=akpm@osdl.org \
    --cc=grundler@parisc-linux.org \
    --cc=linux-mips@linux-mips.org \
    --cc=tbm@cyrius.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