[lkml]   [2003]   [Aug]   [15]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [BK PATCH] Driver Core fixes for 2.6.0-test3
On Fri, Aug 15, 2003 at 09:54:59PM +0200, Ingo Oeser wrote:
> Hi Greg,

Hi, I've brought this back to lkml as I'm getting tired of private email
threads about this topic. Hope you don't mind.

> On Fri, Aug 15, 2003 at 11:25:00AM -0700, Greg KH wrote:
> > Here's some driver core changes that do the following things:
> > - remove struct field and fix up remaining
> > subsystems
> Could you point me to the rationale about this?
> I for one considered "everything should have a name" policy very
> useful and extendible.

The main problem is that we don't want to be putting name databases in
the kernel, like PCI, PnP, and USB were starting to do. People were
starting to complain that the PCI and USB names were not the "proper"
name, as we didn't have enough room for the "full" name.

Naming databases belong in userspace. For PCI, PnP, and USB we can
determine the name ourselves from userspace using lspci, lspnp, and
lsusb. Getting rid of the name field prevents us from relying on kernel
code when we shouldn't be.

> Not that I would like to change that back, just like to know why
> this is done, why so late and why after introducing it into all
> drivers in core?

We messed up, and we're now fixing that before people start to rely on
it :)

Now some subsystems still want to export a "name" as there is no other
way to determine the type of the device (no vendor or product ids.) For
them, a name field is just fine to have. For example, I moved the name
field back into the i2c_client and i2c_adapter structures for this very

Hey, we're saving kernel memory, and this is a problem? :)

Hope this helps explain things.

greg k-h
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

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