Re: [RFC] New driver information

2007-02-16 Thread Daniel Barkalow
On Fri, 16 Feb 2007, Heikki Orsila wrote: > I just read > > http://kerneltrap.org/node/7729 > > and it occured to me that it would be informative to have a new device > driver macro. The motivation for the new macro would be 4 issues: > > * Is it possible to get specifications for

Re: [RFC] New driver information

2007-02-16 Thread Adrian Bunk
On Fri, Feb 16, 2007 at 03:58:51PM +0200, Heikki Orsila wrote: > I just read > > http://kerneltrap.org/node/7729 > > and it occured to me that it would be informative to have a new device > driver macro. The motivation for the new macro would be 4 issues: > > * Is it possible to

Re: [RFC] New driver information

2007-02-16 Thread Maxim
On Friday 16 February 2007 16:08:53 Thiago Galesi wrote: > SInce this information does not, in any way, affect the functioning of > the driver... It is not "executable code", I don't see the point of > it. > > For "module_licence" we have the restriction of some functions being > used only for

Re: [RFC] New driver information

2007-02-16 Thread Thiago Galesi
SInce this information does not, in any way, affect the functioning of the driver... It is not "executable code", I don't see the point of it. For "module_licence" we have the restriction of some functions being used only for GPL code, but for this?!? I really don't see it... Just think: what

[RFC] New driver information

2007-02-16 Thread Heikki Orsila
I just read http://kerneltrap.org/node/7729 and it occured to me that it would be informative to have a new device driver macro. The motivation for the new macro would be 4 issues: * Is it possible to get specifications for the device? * If yes, under what terms? (nda,

[RFC] New driver information

2007-02-16 Thread Heikki Orsila
I just read http://kerneltrap.org/node/7729 and it occured to me that it would be informative to have a new device driver macro. The motivation for the new macro would be 4 issues: * Is it possible to get specifications for the device? * If yes, under what terms? (nda,

Re: [RFC] New driver information

2007-02-16 Thread Thiago Galesi
SInce this information does not, in any way, affect the functioning of the driver... It is not executable code, I don't see the point of it. For module_licence we have the restriction of some functions being used only for GPL code, but for this?!? I really don't see it... Just think: what would

Re: [RFC] New driver information

2007-02-16 Thread Maxim
On Friday 16 February 2007 16:08:53 Thiago Galesi wrote: SInce this information does not, in any way, affect the functioning of the driver... It is not executable code, I don't see the point of it. For module_licence we have the restriction of some functions being used only for GPL code,

Re: [RFC] New driver information

2007-02-16 Thread Adrian Bunk
On Fri, Feb 16, 2007 at 03:58:51PM +0200, Heikki Orsila wrote: I just read http://kerneltrap.org/node/7729 and it occured to me that it would be informative to have a new device driver macro. The motivation for the new macro would be 4 issues: * Is it possible to get

Re: [RFC] New driver information

2007-02-16 Thread Daniel Barkalow
On Fri, 16 Feb 2007, Heikki Orsila wrote: I just read http://kerneltrap.org/node/7729 and it occured to me that it would be informative to have a new device driver macro. The motivation for the new macro would be 4 issues: * Is it possible to get specifications for the