From: Christoph Hellwig <hch@infradead.org>
To: Matthew Wilcox <willy@debian.org>
Cc: Andrew Vasquez <andrew.vasquez@qlogic.com>,
Linux-Kernel <linux-kernel@vger.kernel.org>,
Linux-SCSI <linux-scsi@vger.kernel.org>
Subject: Re: [ANNOUNCE] QLogic qla2xxx driver update available (v8.00.00b6).
Date: Fri, 7 Nov 2003 09:58:14 +0000 [thread overview]
Message-ID: <20031107095814.A2363@infradead.org> (raw)
In-Reply-To: <20031106175306.GG26869@parcelfarce.linux.theplanet.co.uk>; from willy@debian.org on Thu, Nov 06, 2003 at 05:53:06PM +0000
On Thu, Nov 06, 2003 at 05:53:06PM +0000, Matthew Wilcox wrote:
> >
> > o Build process -- (three module interface for the ISPs), I
> > personally like the idea of a shared library module used
> > between the different ISP drivers. Many others have voiced
> > their frustrations with the single driver-binary for each
> > ISP type that the directive from management is to have a
> > single binary for all *future* products including the
> > ISP23xx (ISP2300/ISP2310/ISP2312/ISP2322) chips.
> >
> > That unfortunately leaves ISP2100 and ISP2200 on the
> > periphery of development efforts.
>
> I wouldn't see a problem with having a structure like this:
>
> ql2100.c
> ql2200.c
> ql23xx.c
> qllib.c
>
> and linking in whichever files are selected. But you definitely only want
> to build qllib.c once.
Well, if you look at the driver you'll need all files except the firmware
anyway. And now that we have the request_firmware interface anyway I'd
bebetter to move that out of the module, at least once initramfs settles down
a bit.
The issue is more lots of tiny ifdefs - those in the C source could be easily
hidden using pdev->device comparisms (and I think I'm gonna submit a patch
for that soon, the driver already does that for ISP23XX variants without
a proper abstraction). Those in the headers are a bit more difficult as the
register layout is a bit different sometimes. But with doing these as unions
instead of ifdefs and splitted subroutines this should be managæble as well,
the feral driver already does this nicely.
--
Christoph Hellwig <hch@lst.de> - Freelance Hacker
Contact me for driver hacking and kernel development consulting
next prev parent reply other threads:[~2003-11-07 22:02 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-06 17:02 Andrew Vasquez
2003-11-06 17:53 ` Matthew Wilcox
2003-11-07 9:58 ` Christoph Hellwig [this message]
2003-11-07 9:33 ` Christoph Hellwig
-- strict thread matches above, loose matches on Subject: below --
2003-11-06 19:33 Andrew Vasquez
2003-11-07 9:39 ` Christoph Hellwig
2003-11-06 17:45 Andrew Vasquez
2003-11-06 17:59 ` Arjan van de Ven
2003-11-07 9:37 ` Christoph Hellwig
2003-11-06 17:11 Andrew Vasquez
2003-11-06 17:14 ` Jens Axboe
2003-11-06 17:43 ` Arjan van de Ven
2003-11-06 17:50 ` Jens Axboe
2003-11-06 17:55 ` Arjan van de Ven
2003-11-06 17:58 ` Jens Axboe
2003-11-05 18:39 Andrew Vasquez
2003-11-06 9:17 ` Jens Axboe
2003-11-05 1:15 Andrew Vasquez
2003-11-05 9:17 ` Mike Anderson
2003-11-06 9:36 ` Christoph Hellwig
2003-11-06 10:51 ` Christoph Hellwig
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=20031107095814.A2363@infradead.org \
--to=hch@infradead.org \
--cc=andrew.vasquez@qlogic.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=willy@debian.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®