From: "'hch@infradead.org'" <hch@infradead.org>
To: "Mukker, Atul" <Atulm@lsil.com>
Cc: "'hch@infradead.org'" <hch@infradead.org>,
'James Bottomley' <James.Bottomley@SteelEye.com>,
"'linux-kernel@vger.kernel.org'" <linux-kernel@vger.kernel.org>,
linux-scsi@vger.kernel.org,
"'marcelo.tosatti@cyclades.com'" <marcelo.tosatti@cyclades.com>,
Matt_Domsch@dell.com
Subject: Re: ANNOUNCE: megaraid driver version 2.10.1
Date: Wed, 14 Jan 2004 09:22:05 +0000 [thread overview]
Message-ID: <20040114092205.B28333@infradead.org> (raw)
In-Reply-To: <0E3FA95632D6D047BA649F95DAB60E57033BC2C3@exa-atlanta.se.lsil.com>; from Atulm@lsil.com on Tue, Jan 13, 2004 at 04:39:12PM -0500
On Tue, Jan 13, 2004 at 04:39:12PM -0500, Mukker, Atul wrote:
> The changes in 2.6.1 are rather extensive, so it would be sometime before
> kernel 2.6.1 version of megaraid is sync'ed against megaraid-2.10.1. Also,
> we would like to backport the PCI hotplug changes to 2.4.x kernel megaraid
> as well.
The problem with backporting is that the 2.4 scsi layer is not hot-plug aware,
so while you can make the driver detect a newly inserted or removed HBA there's
no way to tell the SCSI midlayer.
> +#ifdef SCSI_HAS_HOST_LOCK
> +# if LINUX_VERSION_CODE <= KERNEL_VERSION(2,4,9)
> + /* This is the Red Hat AS2.1 kernel */
> + adapter->host_lock = &adapter->lock;
> + host->lock = adapter->host_lock;
> +# elif LINUX_VERSION_CODE < KERNEL_VERSION(2,6,0)
> + /* This is the later Red Hat 2.4 kernels */
> + adapter->host_lock = &adapter->lock;
> + host->host_lock = adapter->host_lock;
> +# else
> + /* This is the 2.6 and later kernel series */
> + adapter->host_lock = &adapter->lock;
> + scsi_set_host_lock(&adapter->lock);
> +# endif
> +#else
> + /* And this is the remainder of the 2.4 kernel series */
> adapter->host_lock = &io_request_lock;
> +#endif
This is horribly ugly, but not your faul. Any chance you could hide
it into some macro ala megaraid_set_host_lock(adapter, host).
Also note that in 2.6 scsi_set_host_lock should and could easily be avoided,
just let your adapter->host_lock point to host->host_lock.
> if((adapter->flag & BOARD_64BIT)&&(sizeof(dma_addr_t) == 8))
> {
> - pci_set_dma_mask(pdev, 0xffffffffffffffff);
> + pci_set_dma_mask(pdev, 0xffffffffffffffffULL);
This needs error return checking. Again this no regression from the previous
version, could you please fix it in the next update?
next prev parent reply other threads:[~2004-01-14 9:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-13 21:39 ANNOUNCE: megaraid driver version 2.10.1 Mukker, Atul
2004-01-14 9:22 ` 'hch@infradead.org' [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-01-30 15:03 Mukker, Atul
2004-01-30 15:40 ` Jeff Garzik
2004-01-10 13:52 Xose Vazquez Perez
2004-01-09 23:54 Mukker, Atul
2004-01-11 14:06 ` 'hch@infradead.org'
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=20040114092205.B28333@infradead.org \
--to=hch@infradead.org \
--cc=Atulm@lsil.com \
--cc=James.Bottomley@SteelEye.com \
--cc=Matt_Domsch@dell.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=marcelo.tosatti@cyclades.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.