From: Stefan Roese <sr@denx.de>
To: netdev@vger.kernel.org
Cc: linuxppc-dev@ozlabs.org
Subject: IEEE1588 Precision Time Protocol (PTP) driver for AMCC 405EZ
Date: Mon, 30 Apr 2007 16:41:32 +0200 [thread overview]
Message-ID: <200704301641.32686.sr@denx.de> (raw)
Hi all,
I'm in the stage of integrating an IEEE1588 PTP driver for the AMCC 405EZ PPC
and looking for the correct location to place this driver in the Linux source
tree. The driver is a character-driver that enables the user space
applications to configure the time stamping unit and to read/write the
timestamps.
Is "drivers/net/ptp" or "drivers/net/ieee1588" a good solution? Or should it
go to "drivers/char/ptp" because of the chrdev nature of the driver?
Any suggestions welcome (could be that I missed an already existing example).
Best regards,
Stefan
next reply other threads:[~2007-04-30 14:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-30 14:41 Stefan Roese [this message]
2007-05-01 13:45 ` IEEE1588 Precision Time Protocol (PTP) driver for AMCC 405EZ Robert Schwebel
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=200704301641.32686.sr@denx.de \
--to=sr@denx.de \
--cc=linuxppc-dev@ozlabs.org \
--cc=netdev@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).