lkml.org 
[lkml]   [2003]   [Aug]   [13]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: C99 Initialisers
On Wed, Aug 13, 2003 at 04:29:21PM -0400, Jeff Garzik wrote:
> pci_device_tables are (and must be) at per-driver granularity. Sure the
> same card can have multiple drivers, but that doesn't really matter in
> this context, simply because I/we cannot break that per-driver
> granularity. Any solution must maintain per-driver granularity.

So you are still advocating for a KConfig enhancement?

Could you try to describe the layout of a KConfig file that you
have in mind.

I gave it a shot:

It must specify -
a) Objects file used for the driver
b) module name of the driver
c) optional object files used by that driver
d) data used by the driver, for example PCI Data?
e) other stuff?

driver MAXTOR_SATA "SATA for Maxtor IDE"
depends on LIB_SATA
kbuild
obj-$(MAXTOR_SATA) := maxtorsata.o
maxtorsata-y := libsata.o smaxtor.o
maxtorsata-$(VERBOSE_LOGGING) += maxtorlog.o
data
PCIDEVICE(X,Y)

Not complete - and no dought with some missing pieces.
Primarly to try to find out what you have in mind.

Sam
-
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/

\
 
 \ /
  Last update: 2005-03-22 13:47    [W:0.107 / U:1.472 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site