Re: module_param does not work in Ubuntu 13.10 - Kernel 3.10.0-4

I am out of ideas. I have Ubuntu 13.04 as the OS and the kernel version is 3.11.0-rc7 which I compiled myself. sanmukh@sanmukh-laptop:/config/usb_gadget/g1/strings$ insmod --version kmod version 9 sanmukh@sanmukh-laptop:/config/usb_gadget/g1/strings$ lsb_release -a No LSB modules are available.

RE: module_param does not work in Ubuntu 13.10 - Kernel 3.10.0-4

HI Sanmukh, Thank you for testing the code. Yes I am using the same file and there is no typo. When I insert the module it inserts just fine. In this case mystring takes the default value "blah" as seen in log below. dmesg: [ 7907.858933] Demonstrating module parameters [ 7907.858937]

Re: module_param does not work in Ubuntu 13.10 - Kernel 3.10.0-4

I have kernel 3.11.0-rc7 and it seems to be working fine. Are you sure the file attached is the correct one or there is no typo? See the output which I got compiling your file and loading it as a module in the attachment. Thanks, Sanmukh On Thu, Sep 5, 2013 at 9:52 PM, wrote: > Hi all, > > I u

module_param does not work in Ubuntu 13.10 - Kernel 3.10.0-4

Hi all, I use the kernel version "3.10.0-4" that came with Ubuntu distribution. When I compile the example module I got from LKMPG (hello-5.c) and try to load the driver by passing the module with the following command, it gives the following error: # insmod parameter.ko mystring="bebop" Erro

Re: IOCTLs versus netlink

On Mon, Sep 2, 2013 at 1:30 AM, Kristian Evensen wrote: > On Sun, Sep 1, 2013 at 3:16 PM, Greg Freemyer > wrote: > > > > > > Kevin Wilson wrote: > >>Hi, > >>Can someone please explain why are netlink sockets a better > >>communication method between kernel space and userspace ? > >> > > Another

Re: "make install" error

Arun, I guess, you need to select the xhci_hcd module in make menuconfig for building it as a module. Here are the steps to do it. Device Drivers ---> [*] USB support ---> Make sure "Support for Host-side USB" is a dynamically loadable module by moving the cursor to that item and hitting the '

Re: Dcache_lock replacement

Just to explain my previous mail even better-- 1. If I need to protect my driver from itself, it can add its own locking. 2. If the problem is that dcache_lock is used to protect critical variables from other parts of the kernel, I have two options- a) I will need to restructure my code to avoi