Re: [PATCH 3/6] PCI legacy I/O port free driver (take2) - Add device_flagsinto pci_device_id

[Jeff Garzik]

Andi Kleen wrote:
> On Tuesday 21 February 2006 22:10, Greg KH wrote:
>
> > On Tue, Feb 21, 2006 at 09:59:51PM +0100, Andi Kleen wrote:
> >
> > > On Tuesday 21 February 2006 21:56, Greg KH wrote:
> > >
> > >
> > > > I don't think you can add fields here, after the driver_data field.  It
> > > > might mess up userspace tools a lot, as you are changing a userspace
> > > > api.
> > >
> > > User space should look at the ASCII files (modules.*), not the binary
> > > As long as the code to generate these files still works it should be ok.
> >
> > Does it?  
>
>
> I assume Kenji-San tested that.
>
>
> > Shouldn't the tools export this information too, if it really 
> > should belong in the pci_id structure?
>
>
> No - is driver_data exported? 
>  
>
> > So, is _every_ pci driver going to have to be modified to support this
> > new field if they are supposed to work on this kind of hardware? 
>
>
> There is 100% source compatibility because fields are only added at the
> end of the structure.
>
> And the drivers will still work on this hardware even without modification.
>
> It's only an optimization that can be added to selected drivers.

It doesn't matter how easily its added, it is the wrong place to add 
such things.

This is what the various functions called during pci_driver::probe() do...

	Jeff



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