Re: Appropriate method of io remapping a single memory location?

On Tue, May 5, 2015 at 3:29 PM, maitysancha...@gmail.com wrote: Thanks for the reply. Hmm... I did not think of a DT entry as it is a single location and not part of any particular peripheral. Not even mentioned in the memory map. That's why I suggested to use a syscon device. I tried

Preferred userspace IPC mechanism for new drivers?

Hello, I’m writing a driver that needs to communicate with userspace applications. Userspace needs to be able to send commands and associated data to the driver, so the ioctl interface seems pretty straightforward. However, LDD3 states that new ioctls in the kernel are a no-no. If that’s the

About head of kernel linked list structure

In my understanding, the head initialised using LIST_HEAD_INIT or defined by LIST_HEAD corresponds to no *real* data field. But it *does* have its own _next_ and _prev_ pointers. The _next_ pointer points to the first real node in the doubly linked list, and the _prev_ pointer points to the

Re: About head of kernel linked list structure

On Wed, 6 May 2015, Huaicheng Li wrote: In my understanding, the head initialised using LIST_HEAD_INIT or defined by LIST_HEAD corresponds to no *real* data field. correct. a better way to describe it would be that it corresponds to no real enclosing payload, so it should never be

Map syscall nr to syscall name

Hi all I am looking for an efficient way to convert syscall number to syscall name. I can get syscall number by enabling profiling using perf_event_open(), but cant find way to convert it to actual syscall name. Thanks --sahil ___ Kernelnewbies