From: Oliver Hartkopp <socketcan@hartkopp.net>
To: Nikita Edward Baruzdin <nebaruzdin@gmail.com>
Cc: "linux-can@vger.kernel.org" <linux-can@vger.kernel.org>
Subject: Re: CAN documentation
Date: Fri, 25 Jul 2014 16:03:47 +0200 [thread overview]
Message-ID: <53D263C3.2090602@hartkopp.net> (raw)
In-Reply-To: <1406296057.9487.1.camel@gmail.com>
Hi Nikita,
indeed the BCM patches have been added to the tree as well as
CAN FD and filter documentation updates, see commit log at:
http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/log/Documentation/networking/can.txt
Don't know if it's really useful to split up the file.
Would you like to provide a patch for the timestamping stuff?
Regards,
Oliver
On 25.07.2014 15:47, Nikita Edward Baruzdin wrote:
> Hello, guys,
>
> I'm looking at linux-can/can-modules tree:
>
> 2011-06-26 12:47 Oliver Hartkopp
> minor doc changes ... tbc
>
> 2011-06-10 19:08 Oliver Hartkopp
> documentation: rework chapter numbering & references
>
> ...
>
> 2010-11-22 19:41 Oliver Hartkopp
> Added new documentation layout contributed by Daniele Venzano.
>
> Why are all these changes still not in the kernel? I'm not sure if this
> is a good idea to split the documentation, but the patches introduce
> some new helpful information.
>
> Hence a little follow-up question:
>
>> The timestamp on Linux has a resolution of one microsecond and it is
>> set automatically at the reception of a CAN frame.
>
> It seems to me this is not entirely true as the kernel has a support for
> SO_TIMESTAMPNS socket option for quite a long time. Could you really use
> that option with CAN? Does it make sense to use nanosecond timestamps?
> I'm also a bit confused whether these are only the software timestamps
> or you can somehow get them from a controller too.
>
prev parent reply other threads:[~2014-07-25 14:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-25 13:47 CAN documentation Nikita Edward Baruzdin
2014-07-25 14:03 ` Oliver Hartkopp [this message]
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=53D263C3.2090602@hartkopp.net \
--to=socketcan@hartkopp.net \
--cc=linux-can@vger.kernel.org \
--cc=nebaruzdin@gmail.com \
/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