From: Marc Kleine-Budde <mkl@pengutronix.de>
To: Wolfgang Grandegger <wg@grandegger.com>
Cc: christian.buettner@rafi.de, linux-can@vger.kernel.org
Subject: Re: Antwort: Re: [Socketcan-users] socketcan in barebox bootloader
Date: Thu, 09 Feb 2012 10:50:04 +0100 [thread overview]
Message-ID: <4F3396CC.1060009@pengutronix.de> (raw)
In-Reply-To: <4F3392C5.2080409@grandegger.com>
[-- Attachment #1: Type: text/plain, Size: 704 bytes --]
On 02/09/2012 10:32 AM, Wolfgang Grandegger wrote:
> On 02/09/2012 09:46 AM, christian.buettner@rafi.de wrote:
>> Hi Wolfgang,
>>
>> i know that CAN is not the best solution for this tasks, but it is a
>> requirement of a customer to use the can-bus :(
>>
>> So i create a SocketCAN interface on the host side and implement a Level 2
>> CAN receiver in the bootloader, right?
What's Level 2 CAN receiver?
Marc
--
Pengutronix e.K. | Marc Kleine-Budde |
Industrial Linux Solutions | Phone: +49-231-2826-924 |
Vertretung West/Dortmund | Fax: +49-5121-206917-5555 |
Amtsgericht Hildesheim, HRA 2686 | http://www.pengutronix.de |
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 262 bytes --]
next prev parent reply other threads:[~2012-02-09 9:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <OF32B6D01B.4E8430B8-ONC125799E.0055E20B-C125799E.00563FFD@o0802.rafi.inhouse>
[not found] ` <4F3372C3.3040902@grandegger.com>
[not found] ` <OF323BE753.A56A00D8-ONC125799F.002F6CA3-C125799F.00302BFA@o0802.rafi.inhouse>
2012-02-09 9:32 ` Antwort: Re: [Socketcan-users] socketcan in barebox bootloader Wolfgang Grandegger
2012-02-09 9:50 ` Marc Kleine-Budde [this message]
[not found] ` <1328824647.5414.10.camel@slaptop>
2012-02-10 8:55 ` Marc Kleine-Budde
2012-02-10 9:33 ` Oliver Hartkopp
2012-02-10 10:58 ` Marc Kleine-Budde
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=4F3396CC.1060009@pengutronix.de \
--to=mkl@pengutronix.de \
--cc=christian.buettner@rafi.de \
--cc=linux-can@vger.kernel.org \
--cc=wg@grandegger.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 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.