From: Richard Hirst <rhirst@linuxcare.com>
To: parisc-linux@thepuffingroup.com
Subject: [parisc-linux] sym53c8xx.c now works with 53c875 on parisc
Date: Fri, 23 Jun 2000 12:31:15 +0100 [thread overview]
Message-ID: <20000623123115.K922@linuxcare.com> (raw)
Hi,
I have fixed a couple of problems with parisc dynamic dma code so that
sym53c8xx.c now works on the 53c875 (on-board FWSCSI on my B180L).
The config options I used are:
CONFIG_SCSI_SYM53C8XX=y
CONFIG_SCSI_NCR53C8XX_DEFAULT_TAGS=8
CONFIG_SCSI_NCR53C8XX_MAX_TAGS=32
CONFIG_SCSI_NCR53C8XX_SYNC=20
# CONFIG_SCSI_NCR53C8XX_PROFILE is not set
CONFIG_SCSI_NCR53C8XX_IOMAPPED=y
The main problem was that xxx_alloc_consistent() should return a
virtual address that is aligned to a power of 2 boundary equivalent
to the size requested. We used get_vm_area() which doesn't worry about
alignment of returned areas. I have got round this by introducing a
new get_aligned_vm_area() function in mm/vmalloc.c, but I guess that
is probably only temporary until we decide on the proper solution.
Other archs use get_free_pages and so avoid this problem.
Suggestions, anyone?
Richard
reply other threads:[~2000-06-23 11:30 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20000623123115.K922@linuxcare.com \
--to=rhirst@linuxcare.com \
--cc=parisc-linux@thepuffingroup.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