linux-kernel - Re: Problems with printk logs and my driver

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <Pine.LNX.4.44L0.1510041123080.20035-100000@netrider.rowland.org>
Date:	Sun, 4 Oct 2015 11:28:04 -0400 (EDT)
From:	Alan Stern <stern@...land.harvard.edu>
To:	Eric Curtin <ericcurtin17@...il.com>
cc:	Austin S Hemmelgarn <ahferroin7@...il.com>,
	Jiri Kosina <jikos@...nel.org>,
	Felipe Tonello <eu@...ipetonello.com>,
	USB list <linux-usb@...r.kernel.org>,
	Kernel development list <linux-kernel@...r.kernel.org>
Subject: 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 it change driver. When I
> reboot to this kernel, my keyboard still uses the usbhid driver. Why
> does this happen?

Because the Samsung wireless keyboard and mouse also use the usbhid 
driver.  Besides, the choice of driver depends just as much on the 
bInterfaceClass, -Subclass, and -Protocol as on the vendor and product 
IDs.

Basically, nothing needs to use usbkbd.  Anything that driver can
handle will also work with usbhid.  The only reason for keeping usbkbd 
as a separate driver is because it is smaller than usbhid, so it's 
better suited to some embedded applications with limited memory.

Alan Stern

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/