From: Jeff Garzik <jgarzik@pobox.com>
To: David Jeffery <david_jeffery@adaptec.com>
Cc: "linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>
Subject: Re: [PATCH2.5] ips 2/4: 2.4 resync
Date: Fri, 15 Aug 2003 16:56:19 -0400 [thread overview]
Message-ID: <3F3D48F3.8090405@pobox.com> (raw)
In-Reply-To: <1060951401.3259.44.camel@blackmagic>
David Jeffery wrote:
> This patch is a resync with the 6.10 driver for 2.4 and updates the 2.4
> compatability code. It adds a new wrapper function for differences
> between the 2.4 and 2.6 scsi proc interface, forces pci posting in 3
> places, corrects using a meaningless constant of 0x80 to 0, and syncs
> comments that had changed.
> @@ -257,9 +259,12 @@
> .queuecommand = ips_queue,
> .eh_abort_handler = ips_eh_abort,
> .eh_host_reset_handler = ips_eh_reset,
> + .proc_name = "ips",
> #if LINUX_VERSION_CODE > KERNEL_VERSION(2,5,0)
> + .proc_info = ips_proc_info,
> .slave_configure = ips_slave_configure,
> #else
> + .proc_info = ips_proc24_info,
> .select_queue_depths = ips_select_queue_depth,
> #endif
I wonder if you would object to removing the proc_info hook and code
completely? No big deal if the answer is "no", but overall, I would
prefer to continue the current process of trimming down procfs.
If you want to export some information that's not exported currently,
you can use sysfs attributes for that.
> @@ -4867,6 +4887,7 @@
> METHOD_TRACE("ips_enable_int_copperhead", 1);
>
> outb(ha->io_addr + IPS_REG_HISR, IPS_BIT_EI);
> + inb(ha->io_addr + IPS_REG_HISR); /*Ensure PCI Posting Completes*/
> }
>
> /****************************************************************************/
> @@ -4883,6 +4904,7 @@
> METHOD_TRACE("ips_enable_int_copperhead_memio", 1);
>
> writeb(IPS_BIT_EI, ha->mem_ptr + IPS_REG_HISR);
> + readb(ha->mem_ptr + IPS_REG_HISR); /*Ensure PCI Posting Completes*/
> }
>
> /****************************************************************************/
> @@ -4903,6 +4925,7 @@
> Oimr = readl(ha->mem_ptr + IPS_REG_I960_OIMR);
> Oimr &= ~0x08;
> writel(Oimr, ha->mem_ptr + IPS_REG_I960_OIMR);
> + readl(ha->mem_ptr + IPS_REG_I960_OIMR); /*Ensure PCI Posting Completes*/
> }
>
> /****************************************************************************/
Nice :)
Jeff
prev parent reply other threads:[~2003-08-15 20:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-15 12:43 [PATCH2.5] ips 2/4: 2.4 resync David Jeffery
2003-08-15 20:56 ` Jeff Garzik [this message]
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=3F3D48F3.8090405@pobox.com \
--to=jgarzik@pobox.com \
--cc=david_jeffery@adaptec.com \
--cc=linux-scsi@vger.kernel.org \
/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.