From: me@tobin.cc (Tobin C. Harding)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Xilinx clock wizard driver
Date: Tue, 10 Oct 2017 08:46:03 +1100 [thread overview]
Message-ID: <20171009214603.GA20083@eros> (raw)
In-Reply-To: <CABiBLRr9VWqC0yMO4d2So__B3aFm+tqwgDGjAEhPJ3s+4P2cFA@mail.gmail.com>
On Mon, Oct 09, 2017 at 01:16:41PM -0400, Merin Santhosh wrote:
> Hi All,
>
> I'm Merin, I'm a masters student at the University of Florida.
Hi Merin, welcome.
> I was doing
> through the Linux Kernel, hoping to contribute to something of relevance.
> Since I have a background in systems, I was hoping to get started with the
> Xilinx clocking wizard(link)
> <https://git.kernel.org/pub/scm/linux/kernel/git/gregkh/staging.git/tree/drivers/staging/clocking-wizard/TODO>
Cool, go for it.
> I wanted to know how is it that the modified driver is tested once coded.
> Can someone explain to me how this is done?
I am by no means an expert. One sure method (for any of the drivers in staging) is to buy some
hardware to test the driver. I know nothing about the Xilinx clocking wizard but a quick search
shows that you can set up an FPGA board of some sort to use with the clocking wizard. Here is a link
you may find useful
http://gadgetfactory.net/learn/2017/02/22/fpga-clocking-clocking-wizard-in-xilinx-ise/
If you are borking at paying for hardware just look at it as an investment in your education. Any
hardware you buy will be cheap compared with your other tuition fees.
Happy hacking,
Tobin.
next prev parent reply other threads:[~2017-10-09 21:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-09 17:16 Xilinx clock wizard driver Merin Santhosh
2017-10-09 21:46 ` Tobin C. Harding [this message]
2017-10-10 0:42 ` Merin Santhosh
2017-10-10 4:00 ` Tobin C. Harding
2017-10-10 4:20 ` Merin Santhosh
2017-10-10 4:50 ` Greg KH
-- strict thread matches above, loose matches on Subject: below --
2017-10-25 0:51 Elias Kouskoumvekakis
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=20171009214603.GA20083@eros \
--to=me@tobin.cc \
--cc=kernelnewbies@lists.kernelnewbies.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.