From: Marc Kleine-Budde <mkl@pengutronix.de>
To: Luc Richer <lricher@symboticware.com>, linux-can@vger.kernel.org
Subject: Re: trouble bringing up can0 interface on intel eg20t chipset
Date: Mon, 10 Feb 2014 17:57:10 +0100 [thread overview]
Message-ID: <52F904E6.2060605@pengutronix.de> (raw)
In-Reply-To: <52F903EB.8030107@symboticware.com>
[-- Attachment #1: Type: text/plain, Size: 1069 bytes --]
On 02/10/2014 05:52 PM, Luc Richer wrote:
> I am trying to interface with vehicle engine using Intel EG20T chipset.
>
> This board does have a pinout for CANbus interface, and I believe I have
> determined the correct module for the interface is pch_can
> http://cateee.net/lkddb/web-lkddb/PCH_CAN.html
> Someone told me I may need the i2c module for this chipset as well, so I
> have loaded it also (i2c_eg20t)
>
> I have loaded the modules for the can interface (can, can-dev, can-raw,
> can-bcm) along with i2c_eg20t and pch_can.
>
> dmesg | grep can reveals
> can: controller area network core (rev 20120528 abi 9)
> can: raw protocol (rev 20120528)
> can: broadcast manager protocol (rev 20120528 t)
Please send the output of:
lspci
ifconfig -a
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: 242 bytes --]
next prev parent reply other threads:[~2014-02-10 16:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-10 16:52 trouble bringing up can0 interface on intel eg20t chipset Luc Richer
2014-02-10 16:57 ` Marc Kleine-Budde [this message]
2014-02-10 18:05 ` Luc Richer
2014-02-10 18:30 ` 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=52F904E6.2060605@pengutronix.de \
--to=mkl@pengutronix.de \
--cc=linux-can@vger.kernel.org \
--cc=lricher@symboticware.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.