diff options
author | Jeff Garzik <jeff@garzik.org> | 2007-03-09 10:54:42 -0500 |
---|---|---|
committer | Jeff Garzik <jeff@garzik.org> | 2007-04-28 14:15:59 -0400 |
commit | 8cdfb29c0cd8018f92214c11c631d8926f4cb032 (patch) | |
tree | d4a74d25c301e4c045ca21c45dbcbeadde234548 /kernel | |
parent | e424675f152572d8d2365e351b90bfd81686a150 (diff) | |
download | kernel_samsung_aries-8cdfb29c0cd8018f92214c11c631d8926f4cb032.zip kernel_samsung_aries-8cdfb29c0cd8018f92214c11c631d8926f4cb032.tar.gz kernel_samsung_aries-8cdfb29c0cd8018f92214c11c631d8926f4cb032.tar.bz2 |
libata/IDE: remove combined mode quirk
Both old-IDE and libata should be able handle all controllers and
devices found using normal resource reservation methods.
This eliminates the awful, low-performing split-driver configuration
where old-IDE drove the PATA portion of a PCI device, in PIO-only mode,
and libata drove the SATA portion of the /same/ PCI device, in DMA mode.
Typically vendors would ship SATA hard drive / PATA optical
configuration, which would lend itself to slow (PIO-only) CD-ROM
performance.
For Intel users running in combined mode, it is now wholly dependent on
your driver choice (potentially link order, if you compile both drivers
in) whether old-IDE or libata will drive your hardware.
In either case, you will get full performance from both SATA and PATA
ports now, without having to pass a kernel command line parameter.
Signed-off-by: Jeff Garzik <jeff@garzik.org>
Diffstat (limited to 'kernel')
-rw-r--r-- | kernel/resource.c | 21 |
1 files changed, 0 insertions, 21 deletions
diff --git a/kernel/resource.c b/kernel/resource.c index bdb55a3..9bd14fd 100644 --- a/kernel/resource.c +++ b/kernel/resource.c @@ -213,27 +213,6 @@ int request_resource(struct resource *root, struct resource *new) EXPORT_SYMBOL(request_resource); /** - * ____request_resource - reserve a resource, with resource conflict returned - * @root: root resource descriptor - * @new: resource descriptor desired by caller - * - * Returns: - * On success, NULL is returned. - * On error, a pointer to the conflicting resource is returned. - */ -struct resource *____request_resource(struct resource *root, struct resource *new) -{ - struct resource *conflict; - - write_lock(&resource_lock); - conflict = __request_resource(root, new); - write_unlock(&resource_lock); - return conflict; -} - -EXPORT_SYMBOL(____request_resource); - -/** * release_resource - release a previously reserved resource * @old: resource pointer */ |