From: Gabriel Manriquez <gmanriquez@wegmannusa.com>
To: Oliver Hartkopp <socketcan@hartkopp.net>
Cc: linux-can@vger.kernel.org
Subject: Re: socketCan build fails
Date: Fri, 24 Feb 2012 08:46:45 -0500 [thread overview]
Message-ID: <4F4794C5.7060803@wegmannusa.com> (raw)
In-Reply-To: <4F467C03.2000607@hartkopp.net>
Oliver,
Thank you very much for your help.
I will go ahead and start testing.
-Gabriel
On 2/23/2012 12:48 PM, Oliver Hartkopp wrote:
> On 23.02.2012 18:33, Gabriel Manriquez wrote:
>
>> Hi Oliver,
>>
>> I'm running kernel version 2.6.35.11.
>>
>> I was just following the README file which says to compile kernel/<version>
>> ... so since you're saying that I don't need to then can I just go ahead and
>> compile the utilities and test programs?
>
> Yep! :-)
>
>> I'm trying to use socketcan in conjuction with can driver :
>> peak-linux-driver-7.4 which I already installed.
>
> Then you are done.
>
>> At this point I just need to test communication to and from my CAN device via
>> usb and I thought I needed the socketcan utiliites/test programs to do that.
>
> Yes - using the can-utils is the easiest way to start with SocketCAN.
>
>> The peak-linux-driver-7.4 driver comes with receive and transmit test
>> utilities but they're not suitable for my type of driver install "NETDEV"
>
> That's right.
>
>> I hope what I'm saying makes sense. Otherwise please ask.
>
> Yes. Everything makes sense.
>
> You're on the right way :-)
>
> Regards,
> Oliver
next prev parent reply other threads:[~2012-02-24 13:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-23 15:02 socketCan build fails Gabriel Manriquez
2012-02-23 17:21 ` Oliver Hartkopp
2012-02-23 17:33 ` Gabriel Manriquez
2012-02-23 17:48 ` Oliver Hartkopp
2012-02-24 13:46 ` Gabriel Manriquez [this message]
2012-02-27 9:12 ` Steffen Rose
2012-02-27 9:32 ` Wolfgang Grandegger
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=4F4794C5.7060803@wegmannusa.com \
--to=gmanriquez@wegmannusa.com \
--cc=linux-can@vger.kernel.org \
--cc=socketcan@hartkopp.net \
/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).