Usb module loading

Usb module loading

[selva]

Hi All

I have written a usb module which will be linked if any keyboard
is hot plug.

I follow the step below to make it work

1) rmmod usbhid

2) insmod hello.ko

3) hot plug the keyboard

when the keyboard is hot plugged my kernel module gets loaded and in
syslog the messages regarding the detection of the keyboard are present.

My problem is i have to always remove "usbhid", if i donot that
then "usbhid" module is always linked with the keyboard.

How to make make sure that my module usb_kbd.ko gets linked to the keyboard
with out removing "usbhid" ?

My code is present in the following link

https://github.com/selvagit/little_penguin/blob/master/task_05/hello.c

The syslog is present in the following path

https://github.com/selvagit/little_penguin/blob/master/task_05/syslog

I had looked at udev rules, but what i have understood is we can set attributes
for the modules but we can not determine which kernel module should be
loaded for
any device.

Thanks,
Selvaraj

Usb module loading

[Kristofer Hallin]

You are not supposed to make the solutions for Eudyptula challenge
available to others.
On Aug 8, 2014 8:12 AM, "selva" <selvabe99@gmail.com> wrote:

> Hi All
>
> I have written a usb module which will be linked if any keyboard
> is hot plug.
>
> I follow the step below to make it work
>
> 1) rmmod usbhid
>
> 2) insmod hello.ko
>
> 3) hot plug the keyboard
>
> when the keyboard is hot plugged my kernel module gets loaded and in
> syslog the messages regarding the detection of the keyboard are present.
>
> My problem is i have to always remove "usbhid", if i donot that
> then "usbhid" module is always linked with the keyboard.
>
> How to make make sure that my module usb_kbd.ko gets linked to the keyboard
> with out removing "usbhid" ?
>
> My code is present in the following link
>
> https://github.com/selvagit/little_penguin/blob/master/task_05/hello.c
>
> The syslog is present in the following path
>
> https://github.com/selvagit/little_penguin/blob/master/task_05/syslog
>
> I had looked at udev rules, but what i have understood is we can set
> attributes
> for the modules but we can not determine which kernel module should be
> loaded for
> any device.
>
> Thanks,
> Selvaraj
>
> _______________________________________________
> Kernelnewbies mailing list
> Kernelnewbies at kernelnewbies.org
> http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20140808/66d4e76a/attachment.html 

Usb module loading

[Sudip Mukherjee]

On Fri, Aug 8, 2014 at 11:42 AM, selva <selvabe99@gmail.com> wrote:
> Hi All
>
> I have written a usb module which will be linked if any keyboard
> is hot plug.

Is it related to the Eudyptula Challenge ?? Looks like it is ...


> I follow the step below to make it work
>
> 1) rmmod usbhid
>
> 2) insmod hello.ko
>
> 3) hot plug the keyboard
>
> when the keyboard is hot plugged my kernel module gets loaded and in
> syslog the messages regarding the detection of the keyboard are present.
>
> My problem is i have to always remove "usbhid", if i donot that
> then "usbhid" module is always linked with the keyboard.
>
> How to make make sure that my module usb_kbd.ko gets linked to the keyboard
> with out removing "usbhid" ?
>
> My code is present in the following link
>
> https://github.com/selvagit/little_penguin/blob/master/task_05/hello.c
>
> The syslog is present in the following path
>
> https://github.com/selvagit/little_penguin/blob/master/task_05/syslog
>
> I had looked at udev rules, but what i have understood is we can set attributes
> for the modules but we can not determine which kernel module should be
> loaded for
> any device.
>
> Thanks,
> Selvaraj
>
> _______________________________________________
> Kernelnewbies mailing list
> Kernelnewbies at kernelnewbies.org
> http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies

Usb module loading

[Varka Bhadram]

On 08/08/2014 11:42 AM, selva wrote:

> My code is present in the following link
>
> https://github.com/selvagit/little_penguin/blob/master/task_05/hello.c

As per the rules of *The Eudyptula Challenge*: *Posting answers to the questions
online is also frowned apon, as it really doesn't help anyone out*.

You are not supposed to make available to others...

-- 
Regards,
Varka Bhadram.

Usb module loading

[Valdis.Kletnieks at vt.edu]

On Fri, 08 Aug 2014 08:14:26 +0200, Kristofer Hallin said:

> You are not supposed to make the solutions for Eudyptula challenge
> available to others.

Also, it's a potentially career-limiting move - Google is forever, and
doing something like that may tell potential employers that you are
either unwilling or unable to read and follow a set of specifications.

And if you can't be trusted with the Eudyptula NDA, why should they trust
you with an NDA that matters?
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 848 bytes
Desc: not available
Url : http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20140808/03bdc05b/attachment.bin 

Usb module loading

[selva]

Hi all,

Sorry for not remembering the rules, i will make the link inaccessible

Thanks,
Selvaraj

Usb module loading

[selva]

Just a info to any one taking the little penguin task, my mail was
removed from the task because of posting of public domain.

Do not post in public domain


On Wed, Aug 06, 2014 at 03:15:20AM +0000, Little Penguin wrote:
> On Tue, Aug 05, 2014 at 09:24:00PM +0530, selva wrote:
> > Hi,
> >
> >
> > This loads for _any_ usb device, not just a usb keyboard :(
>
> Not good, please fix.

And now you ask on a public mailing list, with pointers to a github
repo, both of which are totally against the rules of the challenge.

There's already enough public versions of this task's answer floating
around out there that I had to change it once, don't make me have to
change it again.

So, since you violated the rules of the challenge, I'm going to have to
remove you from the challenge, sorry.

Sad to see you go.


        - little