From: "Gyula Matics" <gyula_matics@hp.com>
To: <parisc-linux@puffin.external.hp.com>
Subject: [parisc-linux] lasi scsi driver
Date: Thu, 2 Mar 2000 21:42:50 +0100 [thread overview]
Message-ID: <006601bf8487$e057e010$a94abc0f@hungary.hp.com> (raw)
It's only half working. It can list the devices on the bus, but that's all.
It is not working because it needs a horrible amount of cache flushing
and I still didn't get it right. (the committed code only contains enough
flushing to pass the two debugging tests)
The scsi card is running code that is in the main memory and the driver
is heavily patching that. The bigger problem is that the communication
with the card is done via a mailbox also residing in the main memory
and the driver is assuming that this mailbox is on a non-cacheable page.
I know that the architecture supports setting a page non-cacheable.
My question is if it is possible / good idea to set the mailbox page
to non-cacheable?
Gyula
ps: if you hack 53c7xx.c beware that many comments are misleading.
and generally it is a mess.
next reply other threads:[~2000-03-02 21:43 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-03-02 20:42 Gyula Matics [this message]
2000-03-02 21:19 ` [parisc-linux] lasi scsi driver Grant Grundler
2000-03-02 21:44 ` Gyula Matics
2000-03-03 0:50 ` [parisc-linux] Lasi Ethernet - update Helge Deller
2000-03-03 2:55 ` Bdale Garbee
2000-03-03 13:14 ` [parisc-linux] Lasi Ethernet - update (fixed!) Helge Deller
2000-03-03 1:34 ` [parisc-linux] lasi scsi driver Helge Deller
2000-03-03 15:52 ` willy
2000-03-03 19:10 ` Jerry Huck
2000-03-04 19:49 ` willy
2000-03-05 5:49 ` Grant Grundler
2000-03-05 14:29 ` [parisc-linux] uncacheable memory willy
2000-03-05 15:57 ` [parisc-linux] uncacheable memory (D370) rob hoppe
2000-03-05 16:05 ` willy
2000-03-06 6:26 ` uncacheable memory Grant Grundler
2000-03-05 18:34 ` [parisc-linux] lasi scsi driver Philipp Rumpf
2000-03-05 18:46 ` Philipp Rumpf
2000-03-05 21:05 ` Thomas Bogendoerfer
2000-03-07 19:33 ` Jerry Huck
2000-03-07 23:45 ` Philipp Rumpf
2000-03-08 0:33 ` Grant Grundler
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='006601bf8487$e057e010$a94abc0f@hungary.hp.com' \
--to=gyula_matics@hp.com \
--cc=parisc-linux@puffin.external.hp.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 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.