Re: Problems with printk logs and my driver

On 4 October 2015 at 16:28, Alan Stern wrote: > On Sun, 4 Oct 2015, Eric Curtin wrote: > >> Ok so for the fun of it, I changed the VENDOR_ID and DEVICE_ID of my >> keyboard to use the driver for this samsung Wireless keyboard and >> mouse, crazy I know since I have a

Re: Problems with printk logs and my driver

On 30 September 2015 at 13:07, Austin S Hemmelgarn wrote: > On 2015-09-29 18:11, Eric Curtin wrote: >> >> On 25 September 2015 at 16:45, Austin S Hemmelgarn >> wrote: >>> >>> On 2015-09-25 08:02, Jiri Kosina wrote: On Fri, 25 Sep 2015,

Re: Problems with printk logs and my driver

On Sun, 4 Oct 2015, Eric Curtin wrote: > Ok so for the fun of it, I changed the VENDOR_ID and DEVICE_ID of my > keyboard to use the driver for this samsung Wireless keyboard and > mouse, crazy I know since I have a different piece of hardware, but I > wanted to see what happens or at least does

Re: Problems with printk logs and my driver

On 2015-09-29 18:11, Eric Curtin wrote: On 25 September 2015 at 16:45, Austin S Hemmelgarn wrote: On 2015-09-25 08:02, Jiri Kosina wrote: On Fri, 25 Sep 2015, Felipe Tonello wrote: Maybe a better description on Kconfig and/or comments on source code it's enough. I

Re: Problems with printk logs and my driver

On 25 September 2015 at 16:45, Austin S Hemmelgarn wrote: > On 2015-09-25 08:02, Jiri Kosina wrote: >> >> On Fri, 25 Sep 2015, Felipe Tonello wrote: >> >>> Maybe a better description on Kconfig and/or comments on source code >>> it's enough. >> >> >> I personally find the

Re: Problems with printk logs and my driver

On 2015-09-25 08:02, Jiri Kosina wrote: On Fri, 25 Sep 2015, Felipe Tonello wrote: Maybe a better description on Kconfig and/or comments on source code it's enough. I personally find the current Kconfig description: === config USB_KBD tristate "USB HIDBP Keyboard (simple Boot)

Re: Problems with printk logs and my driver

On Fri, 25 Sep 2015, Felipe Tonello wrote: > Maybe a better description on Kconfig and/or comments on source code > it's enough. I personally find the current Kconfig description: === config USB_KBD tristate "USB HIDBP Keyboard (simple Boot) support" depends on USB && INPUT

Re: Problems with printk logs and my driver

On Thu, Sep 24, 2015 at 9:51 PM, Alan Stern wrote: > On Thu, 24 Sep 2015, Jiri Kosina wrote: > >> On Wed, 23 Sep 2015, Alan Stern wrote: >> >> > Your mistake was thinking that the driver for your keyboard is usbkbd. >> > It isn't. It's usbhid, as you can see in the

Re: Problems with printk logs and my driver

On Thu, 24 Sep 2015, Jiri Kosina wrote: > On Wed, 23 Sep 2015, Alan Stern wrote: > > > Your mistake was thinking that the driver for your keyboard is usbkbd. > > It isn't. It's usbhid, as you can see in the "lsusb -t" output above. > > As Eric is absolutely not the first person ever who got

Re: Problems with printk logs and my driver

On Wed, 23 Sep 2015, Alan Stern wrote: > Your mistake was thinking that the driver for your keyboard is usbkbd. > It isn't. It's usbhid, as you can see in the "lsusb -t" output above. As Eric is absolutely not the first person ever who got confused by this (and I can certainly understand the

Problems with printk logs and my driver

Hi Guys, Just wondering what I am doing wrong. I can't see my logs. I figured out what driver is used for my keyboard and started adding logging: [curtine@localhost ~]$ sudo lsusb -v | grep eyboard -B 13 Bus 001 Device 003: ID 04ca:008d Lite-On Technology Corp. Device Descriptor: bLength

Re: Problems with printk logs and my driver

On Thu, 24 Sep 2015, Eric Curtin wrote: > Hi Guys, > > Just wondering what I am doing wrong. I can't see my logs. I figured > out what driver is used for my keyboard and started adding logging: > > [curtine@localhost ~]$ sudo lsusb -v | grep eyboard -B 13 > Bus 001 Device 003: ID 04ca:008d