Adam Belay wrote:
On Mon, Feb 07, 2005 at 02:18:20PM -0800, Greg KH wrote:
On Mon, Feb 07, 2005 at 04:00:27PM -0600, [EMAIL PROTECTED] wrote:
Currently, code exists in the pci layer to allow userspace to specify
driver data when adding a pci dynamic id from sysfs. However, this data
is never used
Adam Belay wrote:
On Mon, Feb 07, 2005 at 02:18:20PM -0800, Greg KH wrote:
On Mon, Feb 07, 2005 at 04:00:27PM -0600, [EMAIL PROTECTED] wrote:
Currently, code exists in the pci layer to allow userspace to specify
driver data when adding a pci dynamic id from sysfs. However, this data
is never used
On Mon, Feb 07, 2005 at 02:18:20PM -0800, Greg KH wrote:
> On Mon, Feb 07, 2005 at 04:00:27PM -0600, [EMAIL PROTECTED] wrote:
> >
> > Currently, code exists in the pci layer to allow userspace to specify
> > driver data when adding a pci dynamic id from sysfs. However, this data
> > is never used
On Mon, Feb 07, 2005 at 02:18:20PM -0800, Greg KH wrote:
On Mon, Feb 07, 2005 at 04:00:27PM -0600, [EMAIL PROTECTED] wrote:
Currently, code exists in the pci layer to allow userspace to specify
driver data when adding a pci dynamic id from sysfs. However, this data
is never used and
Martin Mares wrote:
Hello!
Which is a good thing, right? "driver_data" is usually a pointer to
somewhere. Having userspace specify it would not be a good thing.
That depends on the driver usage, and the patch allows it to be
configurable and defaults to not being used.
Maybe we could just
Hello!
> >Which is a good thing, right? "driver_data" is usually a pointer to
> >somewhere. Having userspace specify it would not be a good thing.
>
> That depends on the driver usage, and the patch allows it to be
> configurable and defaults to not being used.
Maybe we could just define the
Greg KH wrote:
On Mon, Feb 07, 2005 at 04:00:27PM -0600, [EMAIL PROTECTED] wrote:
Currently, code exists in the pci layer to allow userspace to specify
driver data when adding a pci dynamic id from sysfs. However, this data
is never used and there exists no way in the existing code to use it.
On Mon, Feb 07, 2005 at 04:00:27PM -0600, [EMAIL PROTECTED] wrote:
>
> Currently, code exists in the pci layer to allow userspace to specify
> driver data when adding a pci dynamic id from sysfs. However, this data
> is never used and there exists no way in the existing code to use it.
Which is
On Mon, Feb 07, 2005 at 04:00:27PM -0600, [EMAIL PROTECTED] wrote:
Currently, code exists in the pci layer to allow userspace to specify
driver data when adding a pci dynamic id from sysfs. However, this data
is never used and there exists no way in the existing code to use it.
Which is a
Greg KH wrote:
On Mon, Feb 07, 2005 at 04:00:27PM -0600, [EMAIL PROTECTED] wrote:
Currently, code exists in the pci layer to allow userspace to specify
driver data when adding a pci dynamic id from sysfs. However, this data
is never used and there exists no way in the existing code to use it.
Hello!
Which is a good thing, right? driver_data is usually a pointer to
somewhere. Having userspace specify it would not be a good thing.
That depends on the driver usage, and the patch allows it to be
configurable and defaults to not being used.
Maybe we could just define the
Martin Mares wrote:
Hello!
Which is a good thing, right? driver_data is usually a pointer to
somewhere. Having userspace specify it would not be a good thing.
That depends on the driver usage, and the patch allows it to be
configurable and defaults to not being used.
Maybe we could just
12 matches
Mail list logo
