linux-pci.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: <salix@opencores.org>
To: <linux-kernel@vger.kernel.org>
Cc: <linux-pci@vger.kernel.org>
Subject: HOWTO do Linux kernel development
Date: Sat, 04 Jul 2015 13:07:27 +0430	[thread overview]
Message-ID: <c7923f5477f56a19f70f4450ef22c01f@sarv.net> (raw)

hi,

I'm beginner in Device Driver Developing and I trying to write a WAN 
card driver for a FPGA
based card. I reading pc300too.c and wanxl.c codes in 
linux/drivers/net/wan/ directory to write my driver
also I using kscope-1.6.2, It's great software for reading codes.

I know there are some static and dynamic tools for testing drivers and 
kernel modules
such as KEDR, LDV, S2E, symDrive, cpaChecker, ...

which one is better for me to test wanxl.c and pc300too.c for reverse 
engineering and finally test my driver?
which tools you use? and how test your codes?

thanks
Best Regards


                 reply	other threads:[~2015-07-05 13:55 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=c7923f5477f56a19f70f4450ef22c01f@sarv.net \
    --to=salix@opencores.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
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).