public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: Matthias Andree <ma@dt.e-technik.uni-dortmund.de>
To: Peter Missel <peter.missel@onlinehome.de>
Cc: Matthew Wilcox <matthew@wil.cx>, linux-scsi@vger.kernel.org
Subject: Re: SYM8xx_2 driver ignores certain EEPROM settings
Date: Sat, 01 Jan 2005 23:16:43 +0100	[thread overview]
Message-ID: <m3pt0okd6c.fsf@merlin.emma.line.org> (raw)
In-Reply-To: <200412311620.44488.peter.missel@onlinehome.de> (Peter Missel's message of "Fri, 31 Dec 2004 16:20:44 +0100")

Peter Missel <peter.missel@onlinehome.de> writes:

> I'm fine with the additional safety from the Domain Validation. Nonetheless, 
> the driver shouldn't validate speeds and/or transfer widths that have been 
> forbidden by the user.
> Another example (which I can't verify right now) is negotiation width. 
> External HDD enclosures might be connected through a Narrow cable but 
> actually contain a Wide drive. That'll be one thing where the user would use 
> the SCSI BIOS to limit the particular unit to Narrow. This however would 
> possibly be caught by the DM failing.

No external enclosure necessary. There are also wide chips with only
narrow connectors, for instance, on the Tekram DC-310U, DC-390U boards -
they use a SYM53C860 or SYM53C875, a wide capable chip, but provide only
narrow (50-pin) connectors. I last tried some 2.4.X kernel on such a
setup, and haven't used the DC-390U in a long time (I replaced it by a
DC-390F) - so I cannot test at this time.

-- 
Matthias Andree

  reply	other threads:[~2005-01-01 22:16 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200412311343.42484.peter.missel@onlinehome.de>
2004-12-31 14:53 ` SYM8xx_2 driver ignores certain EEPROM settings Matthew Wilcox
2004-12-31 15:01   ` James Bottomley
2004-12-31 15:20   ` Peter Missel
2005-01-01 22:16     ` Matthias Andree [this message]
2005-01-02  0:28       ` Peter Missel
2005-01-02  0:40         ` Matthias Andree
2005-01-02  1:03           ` Matthew Wilcox
2005-01-02  9:58             ` Peter Missel
2005-02-26 19:34   ` Peter Missel
2005-04-08 22:57     ` Peter Missel
2005-04-09 14:02       ` Matthew Wilcox
2005-04-09 21:44         ` Peter Missel
2005-04-18 17:55           ` Peter Missel
2005-05-04 21:47           ` SYM8xx_2 sync speed negotiation Peter Missel
2005-06-18 21:52             ` Peter Missel
2005-06-19 10:45               ` endless loop problem with SYM8xx_2: unexpected disconnect Christian Werner

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=m3pt0okd6c.fsf@merlin.emma.line.org \
    --to=ma@dt.e-technik.uni-dortmund.de \
    --cc=linux-scsi@vger.kernel.org \
    --cc=matthew@wil.cx \
    --cc=peter.missel@onlinehome.de \
    /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