From: greg@kroah.com (Greg KH)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Xilinx clock wizard driver
Date: Tue, 10 Oct 2017 06:50:31 +0200 [thread overview]
Message-ID: <20171010045030.GJ24158@kroah.com> (raw)
In-Reply-To: <CABiBLRqy8Pux=z1U1uHrNnp_q51mAOv8fPEsL7RHM97snhsxeQ@mail.gmail.com>
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?
A: No.
Q: Should I include quotations after my reply?
http://daringfireball.net/2007/07/on_top
On Mon, Oct 09, 2017 at 08:42:34PM -0400, Merin Santhosh wrote:
> Xilinx fpga kits are pretty pricey, doubt if I can buy one.
> Is there any other way these codes can be tested? Can anyone who is an expert
> in the field comment?
For lots of drivers you do not need the hardware to make basic code
changes like cleanups and such. But to make logical changes, then
having the hardware is almost essencial to ensure your changes actually
work.
If you can't get one of these kits, then try working on a different
driver. Or ask the company if they can send you one. Or look to get a
student discount. Or something else.
best of luck!
greg k-h
next prev parent reply other threads:[~2017-10-10 4:50 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
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 [this message]
-- 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=20171010045030.GJ24158@kroah.com \
--to=greg@kroah.com \
--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.