Re: /proc/slab_allocators empty??

2008-04-11 Thread Peter Teoh
This is beside the point: Looking at the patch in Feb2008: http://lkml.org/lkml/2008/2/19/244 It should be better to use SLOB than SLAB, which has been replaced by SLUB. Anyway, I have do a check on your config file (do it yourself too make oldconfig), and u will see that a lot of dependencies

Re: kernel preemption does not work

2008-04-11 Thread Peter Teoh
On Thu, Apr 10, 2008 at 3:32 PM, bhanu nani [EMAIL PROTECTED] wrote: Hi all, I am trying to test kernel preemption in my driver. When I first compiled the Linux kernel and tested it, I found it to be non-preemptible. Later I realised that my kernel was build with premption disabled. I

usb_control_msg for devices without an OUT endpoint.

2008-04-11 Thread Ribamar Santarosa de Sousa
Hello, There are some USB interfaces (such some kinds of HID) that don't have OUT endpoints and the unique manner to send them data is through control msg like Set_Report requests (chapter 7 of HID 1.1 specification). However, in the kernel interface for usb_control_msg() we need to pass a pipe

Re: clone - CLONE_THREAD and CLONE_SIGHAND without CLONE_VM

2008-04-11 Thread black hole
On Fri, Apr 11, 2008 at 4:08 AM, Mulyadi Santosa [EMAIL PROTECTED] wrote: Hi... On Thu, Apr 10, 2008 at 8:47 PM, black hole [EMAIL PROTECTED] wrote: Hi, I want to solve the following situation in a better way than it is currently solved. I have come into a conclusion that

Re: can i see a driver's registered *minor* number(s)?

2008-04-11 Thread Mohamed Thalib .H
On Fri, 2008-04-11 at 05:56 -0400, Robert P. J. Day wrote: i know well enough that, if i write and load a driver that allocates a device major number and one or more minor numbers, i can see the allocated major number via /proc/devices. but is there a userspace way to see the minor

Re: can i see a driver's registered *minor* number(s)?

2008-04-11 Thread Robert P. J. Day
On Fri, 11 Apr 2008, Mohamed Thalib .H wrote: On Fri, 2008-04-11 at 05:56 -0400, Robert P. J. Day wrote: i know well enough that, if i write and load a driver that allocates a device major number and one or more minor numbers, i can see the allocated major number via /proc/devices. but

Re: usb_control_msg for devices without an OUT endpoint.

2008-04-11 Thread Scott Lovenberg
Ribamar Santarosa de Sousa wrote: Hello, There are some USB interfaces (such some kinds of HID) that don't have OUT endpoints and the unique manner to send them data is through control msg like Set_Report requests (chapter 7 of HID 1.1 specification). However, in the kernel interface for

Re: can i see a driver's registered *minor* number(s)?

2008-04-11 Thread Robert P. J. Day
On Fri, 11 Apr 2008, Rene Herman wrote: On 11-04-08 11:56, Robert P. J. Day wrote: i know well enough that, if i write and load a driver that allocates a device major number and one or more minor numbers, i can see the allocated major number via /proc/devices. but is there a userspace

Re: can i see a driver's registered *minor* number(s)?

2008-04-11 Thread Robert P. J. Day
On Fri, 11 Apr 2008, Scott Lovenberg wrote: Robert P. J. Day wrote: On Fri, 11 Apr 2008, Rene Herman wrote: On 11-04-08 11:56, Robert P. J. Day wrote: i know well enough that, if i write and load a driver that allocates a device major number and one or more minor

Re: can i see a driver's registered *minor* number(s)?

2008-04-11 Thread Rene Herman
On 11-04-08 11:56, Robert P. J. Day wrote: i know well enough that, if i write and load a driver that allocates a device major number and one or more minor numbers, i can see the allocated major number via /proc/devices. but is there a userspace way to see the minor number(s)? or, as LDD3

Re: can i see a driver's registered *minor* number(s)?

2008-04-11 Thread Robert P. J. Day
On Fri, 11 Apr 2008, Rene Herman wrote: On 11-04-08 13:34, Robert P. J. Day wrote: Historically, no way. The driver just gets everything for its registered major and has to switch on minor itself. That is, no such thing as allocated minors as far as the system is concerned. just to

Re: can i see a driver's registered *minor* number(s)?

2008-04-11 Thread Scott Lovenberg
Robert P. J. Day wrote: On Fri, 11 Apr 2008, Rene Herman wrote: On 11-04-08 11:56, Robert P. J. Day wrote: i know well enough that, if i write and load a driver that allocates a device major number and one or more minor numbers, i can see the allocated major number via

Re: kernel preemption does not work

2008-04-11 Thread bhanu nani
Hi Guys, I am not sure whether this API is avialable to user space but this code snippet is part of Kernel module. Test code: -- read() { if(down_interruptible()) return error; mdelay(1); up(); } With this code in place, I try to do

Re: kernel preemption does not work

2008-04-11 Thread Patrick McManus
On Fri, 2008-04-11 at 09:40 -0700, bhanu nani wrote: code snippet is part of Kernel module. Test code: -- read() { if(down_interruptible()) return error; mdelay(1); up(); } This is my my read implementation of char

Re: kernel preemption does not work

2008-04-11 Thread Mulyadi Santosa
Hi... I hope I give you truly correct answer... On Fri, Apr 11, 2008 at 11:40 PM, bhanu nani [EMAIL PROTECTED] wrote: Hi Guys, I am not sure whether this API is avialable to user space but this code snippet is part of Kernel module. Test code: -- read() {