From: Gary Thomas <gary@mlbassoc.com>
To: Marc Kleine-Budde <mkl@pengutronix.de>
Cc: rotesmofa <pascalkrauth@gmail.com>, linux-can@vger.kernel.org
Subject: Re: Bitbake recipe building socketcan for angstrom
Date: Thu, 18 Oct 2012 05:31:19 -0600 [thread overview]
Message-ID: <507FE887.3080705@mlbassoc.com> (raw)
In-Reply-To: <507FE560.8070905@pengutronix.de>
On 2012-10-18 05:17, Marc Kleine-Budde wrote:
> On 10/18/2012 12:55 PM, rotesmofa wrote:
>> Hallo everyone,
>>
>> I am fighting with Bitbaking Socketcan for Angstrom with a 2.6.32 Kernel for my
>> Craneboard.
>
> Regarding the kernel. It's rather old, doesnt't support much CAN
> hardware and may have CAN related bugs. Better update to latest v3.6 or
> newer.
>
>> Currently I have a basic lag of understanding for the *.bb files. I simply want
>> to build socketcan for my board using either Eclipse with my Angstrom toolchain
>> or using Bitbake.
>
> If you want to use socketcan you have to switch on some kernel features:
>
> -> Networking support
> -> CAN bus subsystem support
> [ ] Raw CAN Protocol (raw access with CAN-ID filtering)
> -> CAN Device Drivers
> [ ] Platform CAN drivers with Netlink support
>
> + the driver you need.
>
> No need to change any bitbake files.
>
>> Can anyone guide me? I'am in India and have kind of a research project but there
>> is no support and I'am a Hardware Guy ;-)
>
> If you need support for the userspace tools in openembedded/angstrom you
> should contact they mailinglist.
Just build 'canutils' which is part of the meta-openembedded/meta-oe layer
--
------------------------------------------------------------
Gary Thomas | Consulting for the
MLB Associates | Embedded world
------------------------------------------------------------
prev parent reply other threads:[~2012-10-18 11:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-18 10:55 Bitbake recipe building socketcan for angstrom rotesmofa
2012-10-18 11:17 ` Marc Kleine-Budde
2012-10-18 11:31 ` Gary Thomas [this message]
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=507FE887.3080705@mlbassoc.com \
--to=gary@mlbassoc.com \
--cc=linux-can@vger.kernel.org \
--cc=mkl@pengutronix.de \
--cc=pascalkrauth@gmail.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.