From: "Uwe Wilhelm \(PEAK-System\)" <u.wilhelm@peak-system.com>
To: "'Marc Kleine-Budde'" <mkl@pengutronix.de>,
"'François Beaulier'" <fbeaulier@orange.fr>,
"'Andri Yngvason'" <andri.yngvason@marel.com>,
"'Yegor Yefremov'" <yegorslists@googlemail.com>
Cc: linux-can@vger.kernel.org
Subject: AW: [BULK]Re: Linux board with 10 CANs
Date: Fri, 15 May 2015 15:04:12 +0200 [thread overview]
Message-ID: <005401d08f0f$a3b9f960$eb2dec20$@peak-system.com> (raw)
In-Reply-To: <5555EAC6.8010901@pengutronix.de>
> -----Ursprüngliche Nachricht-----
> Von: linux-can-owner@vger.kernel.org [mailto:linux-can-
> owner@vger.kernel.org] Im Auftrag von Marc Kleine-Budde
> Gesendet: Freitag, 15. Mai 2015 14:47
> An: François Beaulier; Andri Yngvason; Yegor Yefremov
> Cc: linux-can@vger.kernel.org
> Betreff: [BULK]Re: Linux board with 10 CANs
>
> On 05/15/2015 02:40 PM, François Beaulier wrote:
> >> Have you considered FPGA?
> >>
> >> Andri
> > I don't know much about FPGA, i can see in the kernel that there are
> > c_can and m_can drivers, i guess i have to add something like a PCIe
>
> c_can and m_can are IP cores by bosch, they are used in various SoCs.
>
> > bridge to connect the CAN controllers with the SOC ?
> > Is there a way to use FPGA that would not lead to driver development ?
> > Do you have any link where i can learn more about Linux + FPGA + CAN ?
>
> You have to use an IP core that is already supported by the kernel.
>
> Marc
> --
PEAK offer a 2 and a 4 CAN Channel FPGA Solution which support Socket CAN.
A 12 Channel CAN card build with this Core is running under a Military Label
without any problem with nearly 100% Busload per Channel / 1 Mbit
But you need 3 free PCIe 1x Lanes. Cost are cheap, because you only pay License,
no Hardware - that’s up to you (you get the schematic).
You are 100% compatible to the PEAK PCIe based boards -- see WEB Page or google
Regards
Uwe
PEAK-System Technik GmbH
E-mail: support@peak-system.com
Webseite: www.peak-system.com
--
PEAK-System Technik GmbH
Sitz der Gesellschaft Darmstadt
Handelsregister Darmstadt HRB 9183
Geschaeftsfuehrung: Alexander Gach, Uwe Wilhelm
--
next prev parent reply other threads:[~2015-05-15 13:13 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-15 7:56 Linux board with 10 CANs François Beaulier
2015-05-15 8:20 ` Yegor Yefremov
2015-05-15 8:50 ` François Beaulier
2015-05-15 9:11 ` Marc Kleine-Budde
2015-05-15 9:33 ` François Beaulier
2015-05-15 10:24 ` Andri Yngvason
2015-05-15 12:40 ` François Beaulier
2015-05-15 12:47 ` Marc Kleine-Budde
2015-05-15 13:04 ` Uwe Wilhelm (PEAK-System) [this message]
2015-05-15 13:17 ` AW: [BULK]Re: " Marc Kleine-Budde
2015-05-15 13:20 ` AW: " Uwe Wilhelm (PEAK-System)
2015-05-15 14:18 ` François Beaulier
2015-05-15 12:38 ` Gerhard Uttenthaler
2015-05-15 12:48 ` Marc Kleine-Budde
2015-05-15 13:54 ` Bernd Krumboeck
2015-05-18 9:07 ` François Beaulier
2015-05-18 13:31 ` Bernd Krumboeck
2015-05-20 11:35 ` Gediminas Simanskis
2015-05-21 3:19 ` Bernd Krumboeck
2015-05-15 15:24 ` Tom Evans
2015-05-18 9:25 ` François Beaulier
2015-05-18 9:40 ` Gerhard Bertelsmann
2015-05-18 11:13 ` François Beaulier
2015-05-18 12:56 ` Tom Evans
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='005401d08f0f$a3b9f960$eb2dec20$@peak-system.com' \
--to=u.wilhelm@peak-system.com \
--cc=andri.yngvason@marel.com \
--cc=fbeaulier@orange.fr \
--cc=linux-can@vger.kernel.org \
--cc=mkl@pengutronix.de \
--cc=yegorslists@googlemail.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;
as well as URLs for NNTP newsgroup(s).