From: Wolfgang Grandegger <wg@grandegger.com>
To: christian.buettner@rafi.de
Cc: linux-can@vger.kernel.org
Subject: Re: Antwort: Re: [Socketcan-users] socketcan in barebox bootloader
Date: Thu, 09 Feb 2012 10:32:53 +0100 [thread overview]
Message-ID: <4F3392C5.2080409@grandegger.com> (raw)
In-Reply-To: <OF323BE753.A56A00D8-ONC125799F.002F6CA3-C125799F.00302BFA@o0802.rafi.inhouse>
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?
Yep.
Wolfgang.
>
> Christian
>
>
>
> Von: Wolfgang Grandegger <wg@grandegger.com>
> An: christian.buettner@rafi.de
> Kopie: socketcan-users@lists.berlios.de
> Datum: 09.02.2012 08:47
> Betreff: Re: [Socketcan-users] socketcan in barebox bootloader
>
>
>
> Hi Christian,
>
> On 02/08/2012 04:42 PM, christian.buettner@rafi.de wrote:
>> Hi everyone,
>>
>> we use the i.MX28 from freescale and need a socketcan driver
>> implementation in the barebox bootloader.
>
> Well, a Socket-CAN implementation seems a bit heavy and overkill for a
> boot loader.
>
>> The goal is to flash a linux or rootfs image through the barebox
>> bootloader using a CAN bus connection.
>
> CAN is slow! Seem not be a good idea to transfer megabytes of data that
> way.
>
>> We need it to make a field update of the target possible.
>>
>> Has anyone done something like that yet?
>
> Not that I know of.
>
> Wolfgang.
>
> PS:
>
> please do not use this mailing list any longer but send your questions
> to the new "linux-can" mailing list address "linux-can@vger.kernel.org".
> For subscription or mailing list archives please have a look to:
>
> http://vger.kernel.org/vger-lists.html#linux-can
>
> Mail archives of the new linux-can mailing list can be found at:
>
> http://dir.gmane.org/gmane.linux.can
> http://marc.info/?l=linux-can&r=1&w=2
>
>
>
>
next parent reply other threads:[~2012-02-09 9:39 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 ` Wolfgang Grandegger [this message]
2012-02-09 9:50 ` Antwort: Re: [Socketcan-users] socketcan in barebox bootloader Marc Kleine-Budde
[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=4F3392C5.2080409@grandegger.com \
--to=wg@grandegger.com \
--cc=christian.buettner@rafi.de \
--cc=linux-can@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 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.