From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@hamnavoe.com, 9fans@9fans.net
Subject: [9fans] via vt8237
Date: Sat, 5 Jul 2008 16:36:45 -0400 [thread overview]
Message-ID: <3c80dcc2e915815ac5e933e2e9e17bca@quanstro.net> (raw)
In-Reply-To: <eda9ecf20f2e6a106bce797f5dc1c284@hamnavoe.com>
i think the posted patch might not be
appropriate for controllers not having
the via controllers' problem as it is quite
quick to reset the controller if a command
takes a long time. with a properly
functioning controller, it is generally a
bad idea to do a reset with a command in
flight.
i haven't seen any other patches so i don't
know how they work.
i also took a look at the linux driver for
the same hardware and didn't find the same
reset loop. i did however find some pci
setup code specific to this chipset which
i posted some time ago
http://9fans.net/archive/2008/02/277
this code was translated from the linux.
i don't know if this was ever tried. but
it tries to attack the root of the problem,
missed interrupts, by setting some pcie
magic.
i can't try this myself as i don't have
appropriately buggy hardware.
if this doesn't work, it might make sense
to have a controller setting to optionally
check for missed interrupts.
this will allow us to still tell the difference
between an interrupt that got lost and a
controller that's gone off into the weeds.
i've put up a driver that may work if
this is the case but it's not tested due to
lack of hardware. sources is down, so it
can be accessed here:
hget http://www.quanstro.net/vtsdata.c
- erik
prev parent reply other threads:[~2008-07-05 20:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-04 4:18 venti survery results Russ Cox
2008-07-04 9:07 ` [9fans] " Richard Miller
2008-07-04 9:46 ` Kernel Panic
2008-07-04 9:54 ` Richard Miller
2008-07-04 11:03 ` Kernel Panic
2008-07-04 14:04 ` erik quanstrom
2008-07-05 21:42 ` Richard Miller
2008-07-05 20:36 ` erik quanstrom [this message]
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=3c80dcc2e915815ac5e933e2e9e17bca@quanstro.net \
--to=quanstro@quanstro.net \
--cc=9fans@9fans.net \
--cc=9fans@hamnavoe.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;
as well as URLs for NNTP newsgroup(s).