public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Markus Lidel <Markus.Lidel@shadowconnect.com>
To: "David S. Miller" <davem@davemloft.net>
Cc: akpm@osdl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/5] I2O: SPARC fixes
Date: Wed, 16 Nov 2005 13:25:50 +0100	[thread overview]
Message-ID: <437B254E.9040909@shadowconnect.com> (raw)
In-Reply-To: <20051115.132836.41612515.davem@davemloft.net>

Hello,

David S. Miller wrote:
> From: Markus Lidel <Markus.Lidel@shadowconnect.com>
>>+config I2O_LCT_NOTIFY_ON_CHANGES
>>+	bool "Enable LCT notification"
>>+	depends on I2O
>>+	default y
>>+	---help---
>>+	  Only say N here if you have a I2O controller from SUN. The SUN
>>+	  firmware doesn't support LCT notification on changes. If this option
>>+	  is enabled on such a controller the driver will hang up in a endless
>>+	  loop. On all other controllers say Y.
>>+
>>+	  If unsure, say Y.
>>+
> 
> This should be detected at runtime, and that is easily done.
> You can use the PCI device to get at the firmware device
> node, and use that to look for a firmware device node property
> that identifies it as a card from Sun.
> Usually the "name" property has some identifying string in it.
> Sometimes there is a property with the string "fcode" in it and you
> could look for that as well.

OK, i'll look at it... Thanks for the hint!



Best regards,


Markus Lidel
------------------------------------------
Markus Lidel (Senior IT Consultant)

Shadow Connect GmbH
Carl-Reisch-Weg 12
D-86381 Krumbach
Germany

Phone:  +49 82 82/99 51-0
Fax:    +49 82 82/99 51-11

E-Mail: Markus.Lidel@shadowconnect.com
URL:    http://www.shadowconnect.com

  reply	other threads:[~2005-11-16 12:25 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-15  9:31 [PATCH 2/5] I2O: SPARC fixes Markus Lidel
2005-11-15 21:28 ` David S. Miller
2005-11-16 12:25   ` Markus Lidel [this message]
2005-11-16 19:18     ` David S. Miller
2005-11-17  8:12       ` Markus Lidel
2005-11-19  1:07       ` Markus Lidel
2005-11-19  1:22         ` David S. Miller
2005-11-19  3:30           ` Alan Cox
2005-11-19  4:37             ` David S. Miller
2005-11-19 13:18               ` Alan Cox
2005-11-20 21:38                 ` Markus Lidel
2005-11-20 21:42               ` Markus Lidel
2005-11-20 22:52                 ` Al Viro
2005-11-20 23:07                   ` Al Viro
2005-11-20 23:21                     ` Al Viro
2005-11-21  0:48                       ` Markus Lidel
2005-11-21  1:20                         ` Al Viro
2005-11-21  3:38                         ` Al Viro
2005-11-21  8:46                           ` Markus Lidel

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=437B254E.9040909@shadowconnect.com \
    --to=markus.lidel@shadowconnect.com \
    --cc=akpm@osdl.org \
    --cc=davem@davemloft.net \
    --cc=linux-kernel@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