* Emulate pci deviceID/vendor for driver debug ?
@ 2016-02-02 11:39 Ran Shalit
2016-02-02 15:58 ` Bjorn Helgaas
0 siblings, 1 reply; 2+ messages in thread
From: Ran Shalit @ 2016-02-02 11:39 UTC (permalink / raw)
To: linux-pci
Hello,
Is there some simple way - just for debug purpose - to make the kernel
think that the driver matches the board/vendor , so that the driver
will be called ?
I don't have the real harware yet (even not a pci physical interface
for any card), but wanted to start debugging some template driver.
Thank you,
Ran
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: Emulate pci deviceID/vendor for driver debug ?
2016-02-02 11:39 Emulate pci deviceID/vendor for driver debug ? Ran Shalit
@ 2016-02-02 15:58 ` Bjorn Helgaas
0 siblings, 0 replies; 2+ messages in thread
From: Bjorn Helgaas @ 2016-02-02 15:58 UTC (permalink / raw)
To: Ran Shalit; +Cc: linux-pci
Hi Ran,
On Tue, Feb 02, 2016 at 01:39:29PM +0200, Ran Shalit wrote:
> Hello,
>
> Is there some simple way - just for debug purpose - to make the kernel
> think that the driver matches the board/vendor , so that the driver
> will be called ?
> I don't have the real harware yet (even not a pci physical interface
> for any card), but wanted to start debugging some template driver.
If you haven't seen it already, Linux Device Drivers should answer
many of your questions, and it's freely available online:
https://lwn.net/Kernel/LDD3/
If you write a template driver, you can put whatever vendor/device IDs
you want in the pci_device_id table, and then the driver will match
the device you care about. You might have to disable the driver (or
unload the driver module) that normally claims the device.
Bjorn
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2016-02-02 15:58 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2016-02-02 11:39 Emulate pci deviceID/vendor for driver debug ? Ran Shalit
2016-02-02 15:58 ` Bjorn Helgaas
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).