Greg KH greg@... writes:
Btw. are there repositories that would be suitable to make
highly experimental
code available ?
Yes, that is what drivers/staging/ is for, why not submit your driver
for inclusion there?
The driver is not even close from being finished...
Ugh, the whitehead
On Wed, Jan 16, 2013 at 12:37:43AM +, Tilman wrote:
Greg KH greg@... writes:
Btw. are there repositories that would be suitable to make
highly experimental
code available ?
Yes, that is what drivers/staging/ is for, why not submit your driver
for inclusion there?
The
Hello Greg
Do you have a pointer to your code anywhere? That would be the easiest
way to help you out here. Otherwise we are just guessing as to the
issues involved.
Not really -- I hence pasted it into this posting. I hope that is OK and does
violate some etiquette of this list.
Btw.
On Sun, Jan 13, 2013 at 10:23:59PM +, Tilman wrote:
Hello Greg
Do you have a pointer to your code anywhere? That would be the easiest
way to help you out here. Otherwise we are just guessing as to the
issues involved.
Not really -- I hence pasted it into this posting. I hope
On Tue, 8 Jan 2013, Tilman wrote:
I added an addition port_probe, and port_remove function that do nothing but a
return 0. The bahavior is unchanged. The private data is already deallocated
once the release function is called
Of course. Changes you make in your driver aren't going to affect
On Tue, Jan 08, 2013 at 12:14:19AM +, Tilman wrote:
I added an addition port_probe, and port_remove function that do nothing but a
return 0. The bahavior is unchanged. The private data is already deallocated
once the release function is called
Now, i have 2 follow up questions:
1) When
On Mon, 7 Jan 2013, Tilman wrote:
Hello
I am porting a usb test driver from kernel version 3.0.8 to
kernel version 3.7.1.
The release function was working on V3.0.0. On V3.7.1, the
private data stored in serial-port.device-p-driver_data
seems already to be deallocated (or never
