public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: hch@infradead.org
Cc: andrew.vasquez@qlogic.com, linux-scsi@vger.kernel.org,
	linux-kernel@vger.kernel.org, James.Bottomley@SteelEye.com,
	ema@debian.org
Subject: Re: Major qla2xxx regression on sparc64
Date: Wed, 18 Apr 2007 13:10:54 -0700 (PDT)	[thread overview]
Message-ID: <20070418.131054.70219428.davem@davemloft.net> (raw)
In-Reply-To: <20070418171346.GA16471@infradead.org>

From: Christoph Hellwig <hch@infradead.org>
Date: Wed, 18 Apr 2007 18:13:46 +0100

> Note that I expect Sun put in the invalid ROM intentionally, as we have
> similar cases with other cards that have totally messed up ROMs in
> Sun-branded versions.  Personally I think that's an utterly bad decision
> from Sun's side, but we'll have to live with this.

The way configuration paramters are provided on Sun systems is via
openfirmware properties, this is how they do everything and that is
why they never setup the NVRAMs on various chips.

This happens on PowerPC too.  One of many examples is determining the
clock parameters of the ATI Radeon graphics card, it's provided as an
openfirmware property not in some config area in the BIOS.

We can either be anti-social and _demand_ that these systems get their
NVRAMs fixed, which in reality will never happen and is totally
unreasonable, or we can say ok this is how we get the information we
need on these platforms we'll look for it there.

  parent reply	other threads:[~2007-04-18 20:10 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-16  8:02 Major qla2xxx regression on sparc64 David Miller
2007-04-16 16:37 ` Andrew Vasquez
2007-04-16 19:37   ` David Miller
2007-04-16 19:59     ` David Miller
2007-04-16 20:08     ` Andrew Vasquez
2007-04-16 21:10       ` Andrew Vasquez
2007-04-16 22:08         ` David Miller
2007-04-16 22:25           ` Andrew Vasquez
2007-04-16 22:29             ` David Miller
2007-04-16 23:28               ` Andrew Vasquez
2007-04-16 23:41                 ` David Miller
2007-04-16 23:47                   ` Andrew Vasquez
2007-04-17  0:05                     ` David Miller
2007-04-17  2:41                       ` Andrew Vasquez
2007-04-17  5:02                         ` David Miller
2007-04-17 18:28                           ` Seokmann Ju
2007-04-17 18:56                             ` David Miller
2007-04-18 17:16                             ` Christoph Hellwig
2007-04-18 20:12                               ` David Miller
2007-04-18 17:13       ` Christoph Hellwig
2007-04-18 17:28         ` Andrew Vasquez
2007-04-18 20:13           ` David Miller
2007-04-19 17:15             ` Andrew Vasquez
2007-04-18 20:10         ` David Miller [this message]
2007-04-22 14:31           ` Christoph Hellwig

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=20070418.131054.70219428.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=James.Bottomley@SteelEye.com \
    --cc=andrew.vasquez@qlogic.com \
    --cc=ema@debian.org \
    --cc=hch@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    /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