Re: [ANNOUNCE] QLogic qla2xxx driver update available (v8.00.00b6).

From: Christoph Hellwig (hch_at_infradead.org)
Date: 11/07/03

  • Next message: Jan Dittmer: "Re: test9: suspend no go"
    Date:	Fri, 7 Nov 2003 09:58:14 +0000
    To: Matthew Wilcox <willy@debian.org>
    
    

    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
    -
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to majordomo@vger.kernel.org
    More majordomo info at  http://vger.kernel.org/majordomo-info.html
    Please read the FAQ at  http://www.tux.org/lkml/
    

  • Next message: Jan Dittmer: "Re: test9: suspend no go"

    Relevant Pages

    • [2.6 patch] tmscsim: remove kernel kenel 2.2 #ifdefs
      ... The patch below removes #ifdefs for kernel 2.0 and 2.2 from the tmscsim ... MODULE_DESCRIPTION("SCSI host adapter driver for Tekram DC390 and other AMD53C974A based PCI SCSI adapters"); ... static inline int timer_pending(struct timer_list * timer) ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)
    • Re: My thoughts on the "new development model"
      ... |>>> 2.6 tree is great for gentoo users who like gcc consuming all CPU ... |>> that after a month or so of fixes etc it will be a very stable kernel ... driver for 2.6.7 for an ADSL card; a development driver for 2.6.5 for a ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)
    • Re: SL811 problem on mach-pxa
      ... It was tested with _both_ workarounds for IRQ issues; ... unlike the predecessors to this driver). ... I've had reports that one of the ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)
    • Re: sata related hang with linux-2.6
      ... IMHO there's something not quite right with the Silicon Image libata ... Perhaps the driver is enabling the hardware to generate interrupts ... before setting up the interrupt routine for it? ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)
    • Re: 2.7 (future kernel) wish
      ... > I've never seen one give a STOP error from that but I guess a bad driver ... I would like to see the HAL type crap for Linux. ... to have uniform user device control from a gui programmable means. ... To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/ ...
      (Linux-Kernel)