diff options
author | Ben Collins <bcollins@ubuntu.com> | 2006-06-12 18:13:32 -0400 |
---|---|---|
committer | Ben Collins <bcollins@ubuntu.com> | 2006-06-12 18:13:32 -0400 |
commit | 4611ed38030a2ce3661de999c3487e5a1eed0dc0 (patch) | |
tree | bd0924844e1b5b5ccefc4ee5cf81c917b8781e5c /block/Kconfig.iosched | |
parent | 8aef63ff033fb0e7ba02d8e760d268eb0aafc58c (diff) | |
download | kernel_samsung_smdk4412-4611ed38030a2ce3661de999c3487e5a1eed0dc0.zip kernel_samsung_smdk4412-4611ed38030a2ce3661de999c3487e5a1eed0dc0.tar.gz kernel_samsung_smdk4412-4611ed38030a2ce3661de999c3487e5a1eed0dc0.tar.bz2 |
ohci1394: set address range properties
This patch supplies the API extension introduced by patch
"ieee1394: extend lowlevel API for address range properties"
with proper addresses.
Like in patch ''ohci1394, sbp2: fix "scsi_add_device failed"
with PL-3507 based devices'', 1 TeraByte is chosen as physical
upper bound. This leaves a window for the middle address range.
This choice is only relevant for adapters which actually have a
programmable pysical upper bound register. (Only ALi and
Fujitsu adapters are known for this. Most adapters have a fixed
bound at 4 GB.) The middle address range is suitable for posted
writes.
AFAIK, PCILynx does not support physical DMA nor posted writes,
therefore no equivalent change in the pcilynx driver is necessary.
There is also a driver for GP2Lynx, although not in mainline Linux.
I assume this hardware does not support these OHCI features either.
Signed-off-by: Stefan Richter <stefanr@s5r6.in-berlin.de>
Signed-off-by: Ben Collins <bcollins@ubuntu.com>
Diffstat (limited to 'block/Kconfig.iosched')
0 files changed, 0 insertions, 0 deletions