public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "John W. Linville" <linville@tuxdriver.com>
To: Greg KH <greg@kroah.com>
Cc: Tony Luck <tony.luck@gmail.com>, Keith Owens <kaos@sgi.com>,
	linux-kernel@vger.kernel.org, linux-ia64@vger.kernel.org
Subject: Re: 2.6.14-rc1 breaks tg3 on ia64
Date: Sat, 17 Sep 2005 12:46:52 -0400	[thread overview]
Message-ID: <20050917164649.GC19854@tuxdriver.com> (raw)
In-Reply-To: <20050917161617.GA23171@kroah.com>

On Sat, Sep 17, 2005 at 09:16:17AM -0700, Greg KH wrote:
> On Sat, Sep 17, 2005 at 11:59:14AM -0400, John W. Linville wrote:
> > On Sat, Sep 17, 2005 at 08:47:03AM -0700, Tony Luck wrote:

> > > Anyone know anything more about this problem?  I'm not seeing it
> > > on any of my systems ... so perhaps it only affects cards with a
> > > PCI bridge on them, or cards that haven't already been initialized
> > > by EFI.
> > 
> > I posted a patch on Wednesday:
> > 
> > 	http://www.ussg.iu.edu/hypermail/linux/kernel/0509.1/2193.html
> > 
> > The original reporter (Keith Owens <kaos@sgi.com>) confirmed this
> > patch to fix the problem.
> 
> Yes, and a number of people objected to that patch.  Care to respond to
> them?

Care to check your email? :-)

	http://www.ussg.iu.edu/hypermail/linux/kernel/0509.1/2267.html

Basically, the concerns raised are non-issues.	The new patch
merely limits the BAR restoration to those situations where it is
truly needed.  Anything broken in that situation was broken before
the original patch as well.

The only other point was that this particular ia64 hardware is
broken if you can't rewrite its BARs.  That may well be, but we can
accomodate it w/o losing the intent of the original patch.

Tony's post indicates that this is not a generic ia64 problem.  If you
want a patch along the lines of what Dave Miller and Ivan Kokshaysky
advocate (i.e. something in the pci access routines for this box),
then Keith or someone else w/ knowledge of (and access to) this box
will need to step forward w/ a patch or at least some information.

John
-- 
John W. Linville
linville@tuxdriver.com

  parent reply	other threads:[~2005-09-17 16:47 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-13  5:22 2.6.14-rc1 breaks tg3 on ia64 Keith Owens
2005-09-13  5:37 ` David S. Miller
2005-09-13  6:17   ` Keith Owens
2005-09-13  6:47     ` David S. Miller
2005-09-13  6:48     ` Keith Owens
2005-09-13  6:59     ` Greg KH
2005-09-13  7:27       ` Keith Owens
2005-09-17 15:47         ` Tony Luck
2005-09-17 15:59           ` John W. Linville
2005-09-17 16:16             ` Greg KH
2005-09-17 16:34               ` Jack Steiner
2005-09-17 16:48                 ` John W. Linville
2005-09-17 16:46               ` John W. Linville [this message]
2005-09-18  6:23             ` David S. Miller
2005-09-18  6:33               ` Tony Luck
2005-09-18 11:44               ` Jack Steiner
     [not found] <20050919204523.GD15838@sgi.com>
2005-09-19 22:43 ` Mike Habeck
2005-09-20  1:14   ` David S. Miller

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=20050917164649.GC19854@tuxdriver.com \
    --to=linville@tuxdriver.com \
    --cc=greg@kroah.com \
    --cc=kaos@sgi.com \
    --cc=linux-ia64@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tony.luck@gmail.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