From: greg@kroah.com (Greg KH)
To: kernelnewbies@lists.kernelnewbies.org
Subject: How to design protocol stack with can-bus driver of character driver
Date: Thu, 13 Jan 2011 09:40:44 -0800 [thread overview]
Message-ID: <20110113174044.GA28247@kroah.com> (raw)
In-Reply-To: <AANLkTim4WkYvcr9WX=OQXSAZ6mQWSW0Gq5a4K5Y3TT91@mail.gmail.com>
On Fri, Jan 14, 2011 at 12:42:52AM +0800, cheng chen wrote:
> Hi all,
> I am working on vehicle body control system with can-bus as my BE final
> project.
> It contains three parts.
>
> 1.CAN chip driver
> 2.CAN-bus protocol stack
> 3.UI
>
> The problem is that I already have written the CAN chip driver as a
> character device driver using IO-simulated SPI.
Oops, don't do that.
> So with this character driver API open() read() write() ioctl(), I start to
> wonder where can I put my protocol stack?
Use the in-kernel CAN protocol stack, that is much easier.
> Or should rewrite the driver in network device frameworks?
Yes.
thanks,
greg k-h
next prev parent reply other threads:[~2011-01-13 17:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-13 16:42 How to design protocol stack with can-bus driver of character driver cheng chen
2011-01-13 16:51 ` Daniel Baluta
2011-01-13 17:40 ` Greg KH [this message]
2011-01-14 5:20 ` cheng chen
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=20110113174044.GA28247@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 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).