From: Oliver Hartkopp <oliver@hartkopp.net>
To: Michael Arndt <flexray4linux@scriptkiller.de>
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH] FlexRay: Allocate numbers for FlexRay communication
Date: Thu, 30 Apr 2009 19:28:01 +0200 [thread overview]
Message-ID: <49F9DFA1.30100@hartkopp.net> (raw)
In-Reply-To: <20090430163825.GX13310@m58s01.vlinux.de>
Michael Arndt wrote:
> This patch adds a protocol family, Ethernet protocol ID,
> ARP protocol identifier and a line discipline for FlexRay
> communication using Linux.
>
> I do not know why ETH_P_CAN has been chosen to be 0x000C
perhaps because of 'C'AN ?
>
> Further code including the FlexRay core, raw sockets and
> examples will soon be posted on a yet-to-be-created project site.
Usually there's a project and some kind of community that worked, discussed
and tested the stuff for some time to be mature for mainline.
- What is the technical background?
- Is there any documentation?
- Do you need realtime?
- What hardware is supported?
> +++ b/include/linux/tty.h
> @@ -23,7 +23,7 @@
> */
> /* line disciplines */
> #define N_TTY 0
> @@ -46,6 +46,7 @@
> #define N_GIGASET_M101 16 /* Siemens Gigaset M101 serial DECT adapter */
> #define N_SLCAN 17 /* Serial / USB serial CAN Adaptors */
> #define N_PPS 18 /* Pulse per Second */
> +#define N_SLFLEXRAY 19 /* Serial / USB serial FlexRay adapters */
???
I bet there's no Flexray hardware on the market that can be attached on a
serial line like there are for low-cost CAN adaptors, right?
So why are you claiming a line discipline here?
Regards,
Oliver
next prev parent reply other threads:[~2009-04-30 17:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-30 16:38 [PATCH] FlexRay: Allocate numbers for FlexRay communication Michael Arndt
2009-04-30 16:50 ` David Miller
2009-04-30 17:28 ` Oliver Hartkopp [this message]
2009-05-02 16:32 ` Michael Arndt
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=49F9DFA1.30100@hartkopp.net \
--to=oliver@hartkopp.net \
--cc=flexray4linux@scriptkiller.de \
--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).