From: G. David Butler gdb@dbSystems.com
Subject: [9fans] DPT PM2041W observations
Date: Mon, 12 Jan 1998 14:52:37 -0600 [thread overview]
Message-ID: <19980112205237.KXKxf7zSqlTPmDUvY3ZDU12wmNeoZCPkBfdC5-uSjjY@z> (raw)
>Cool. Patch?
For DPO? Change wren.c to encode DPO in cmd[1].
cmd[1] = 0x10; For command queueing? It won't help the current
DPT driver since it only sends one command to the card at a
time, just like the 154x driver that came with the system.
If you want to try, set msg[1] to 0x20 and msg[2] to 0.
To use command queueing you need to be able to send multiple
commands to each *target*!
>> So why does this 4th generation card with tag queueing support
>> run slower than the 1st generation design that is over 10 years
>> old?
>
>Perhaps the driver for the 1540 is better optimized as it's been
>around longer, and it's had more work put into it. There might
Remember, I have written both drivers from scratch and each
is optimized for the controller it is talking to.
>be something in the DPT documentation that one can do with the
>card that one can't do with a 1540 ( bus on/off? ). 1540 is a
Yes I know. For the comparison I turned the 154x back to 12us
on and 2us off, to match the DPT. I usally run the 154x at
13us on 1us off.
David Butler
gdb@dbSystems.com
next reply other threads:[~1998-01-12 20:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-01-12 20:52 G.David [this message]
-- strict thread matches above, loose matches on Subject: below --
1998-01-14 22:56 Mark
1998-01-14 14:57 G.David
1998-01-12 23:18 G.David
1998-01-12 23:17 Eric
1998-01-12 20:38 Eric
1998-01-12 19:58 G.David
1998-01-12 0:19 G.David
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=19980112205237.KXKxf7zSqlTPmDUvY3ZDU12wmNeoZCPkBfdC5-uSjjY@z \
--to=9fans@9fans.net \
/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).