public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Tony Luck <tony.luck@gmail.com>
To: "David S. Miller" <davem@davemloft.net>
Cc: linville@tuxdriver.com, kaos@sgi.com, greg@kroah.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 23:33:57 -0700	[thread overview]
Message-ID: <12c511ca050917233313418638@mail.gmail.com> (raw)
In-Reply-To: <20050917.232304.31192760.davem@davemloft.net>

> It fixes the problem, but it's a hack, and I, perhaps like Tony,
> personally would like to know why the these IA64 systems break for
> such a simple operation such as writing some base registers with
> values we've probed already.

It does sound odd[1] that you can't rewrite the BARs to the values that
they should already have.  But I'm willing to wait to see what SGI's
solution that fixes this inside arch/ia64/sn/ looks like before making
any judgements.

-Tony

[1] odd == PCI spec violating?

  reply	other threads:[~2005-09-18  6:34 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
2005-09-18  6:23             ` David S. Miller
2005-09-18  6:33               ` Tony Luck [this message]
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=12c511ca050917233313418638@mail.gmail.com \
    --to=tony.luck@gmail.com \
    --cc=davem@davemloft.net \
    --cc=greg@kroah.com \
    --cc=kaos@sgi.com \
    --cc=linux-ia64@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linville@tuxdriver.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