All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kai Krakow <kai@kaishome.de>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Jeff Garzik <jeff@garzik.org>, linux-ide@vger.kernel.org
Subject: Re: [PATCH] pata_sis: Remove bogus cable match
Date: Mon, 8 Dec 2008 12:13:56 +0100	[thread overview]
Message-ID: <200812081213.56499.kai@kaishome.de> (raw)
In-Reply-To: <20081206002705.46052575@lxorguk.ukuu.org.uk>

Am Samstag, 06. Dezember 2008 schrieb Alan Cox:

> On Fri, 05 Dec 2008 15:31:40 -0500
>
> Jeff Garzik <jeff@garzik.org> wrote:
> > Alan Cox wrote:
> > > From: Alan Cox <alan@redhat.com>
> > >
> > > Some systems report SIS 5513 as both vendor/id and subvendor/id string.
> > > In that case we can't distinguish the system by the id svid/sdid and in
> > > fact the entry here breaks some boxes. At some point we need to find
> > > another way to detect the Targa Visionary 1000, until then this a hang
> > > for some users with lower performance for others.
> > >
> > > Closes: #12092
> > >
> > > Signed-off-by: Alan Cox <alan@redhat.com>
> >
> > Should that last sentence be "this SOLVES a hang"?
> >
> > As it is currently worded, it is unclear what we are trading off with
> > this patch...
>
> I missed out the word "trades" ...

Is there away to bypass this bogus-detection and force the driver into using 
high-speed mode on the short 40-wire cable? Maybe by introducing a 
kernel/module parameter? Or is it there? I found nothing in the docs.

Can I provide any information you need to properly detect the Targa Visionary 
1000?

Thanks,
Kai

  reply	other threads:[~2008-12-08 11:16 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-05 19:41 [PATCH] pata_sis: Remove bogus cable match Alan Cox
2008-12-05 20:31 ` Jeff Garzik
2008-12-06  0:27   ` Alan Cox
2008-12-08 11:13     ` Kai Krakow [this message]
2008-12-08 11:39       ` Alan Cox
2008-12-09  5:48 ` Jeff Garzik

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=200812081213.56499.kai@kaishome.de \
    --to=kai@kaishome.de \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=jeff@garzik.org \
    --cc=linux-ide@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.