Re: Stop usbhid from claiming usb device on hotplug
On Sun, 31 May 2015 21:31:20 -0400, Nicholas Krause said: > Your right, questions about eucalyptus based tasks should be asked off list > to avoid people getting easy answers through. No, the rules are to do it *on your own*, without asking anybody, on or off list. > However I think a lot of this could be avoided if we taught people how to do > kernel programming research better. Well, why don't you make suggestions from your own experience how we can improve that? pgp0i4CrkkELP.pgp Description: PGP signature ___ Kernelnewbies mailing list Kernelnewbies@kernelnewbies.org http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
Re: Stop usbhid from claiming usb device on hotplug
On Sun, 31 May 2015 20:39:06 -0400, Nicholas Krause said: > If you send your complete code to the list I can try and see if there are > other issues but that's the most likely. Actually, he shouldn't send it to the list. It smells too much of eucalyptus pgp53YP95B7DJ.pgp Description: PGP signature ___ Kernelnewbies mailing list Kernelnewbies@kernelnewbies.org http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
Re: Stop usbhid from claiming usb device on hotplug
On Sat, May 30, 2015 at 9:28 PM, wrote: > On Sat, 30 May 2015 04:07:08 -0400, Armin Moradi said: > >> had done, but while I was reading LDD 3rd ed., I also wanted to get >> probing to work which is done after the driver is already loaded. > > If it's a dummy driver, what device is it going to probe? I have tried specifying a vendorID and productID in the id_table for one of the keyboards I have lying around. My expectation would be that the probe would get called when that device is connected, but I see usbhid initializing the keyboard and probe() not getting called at all. ___ Kernelnewbies mailing list Kernelnewbies@kernelnewbies.org http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
Packet encryption based on gre key value with ip xfrm command
Hi, I am trying to encrypt Gre packet have specific key values in GRE header with following command ip xfrm policy add src 192.168.1.9 dst 192.168.1.5 proto gre key 3 dir in tmpl src 192.168.1.9 dst 192.168.1.5 proto esp reqid 16387 mode transport But it is not working. If I remove the "key 3" from above system encrypt all GRE packets. I tried with kernel version 3.18 and iproute2 version.2.4. I got iproute2 patch file having changes to support filtering based on keys but didn't find corresponding kernel patch. How to encrypt Packets based on GRE key value.? Regards Harsh Jain ___ Kernelnewbies mailing list Kernelnewbies@kernelnewbies.org http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
