Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Martyn Welch <martyn.welch@ge.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: comedi / angstrom
Date: Tue, 15 Jun 2010 09:17:22 +0100	[thread overview]
Message-ID: <4C173712.3070405@ge.com> (raw)
In-Reply-To: <201006150815.32214.superaorta@gmail.com>

superaorta@gmail.com wrote:
> I would like to build comedi (www.comedi.org) for my beagle board. From the 
> instructions for comedi, "you will need to havea correctly configured Linux 
> kernel source tree".
>
> I have built comedi on many platforms without trouble but I'm completely lost 
> in Angstrom - I have the kernel source (2.6.29 from kernel.org) but I don't 
> know where to find the config files. I have done this on and x86 host: 
> http://www.angstrom-distribution.org/building-angstrom
>
> I don't fancy building comedi using bitbake because I have not the slightest 
> idea how to adapt it to this purpose. The easiest thing seems to me is to 
> find the correctly configures kernel source and config files and install them 
> on the beagleboard then build comedi locally.
>
> Any advice? overwhelmed and stuck here.
>
>   

I built comedi into one of our builds for testing a parallel port as
GPIO. Comedi consists of 2 parts:

1) Kernel drivers - which seem to be in the staging directory of the
kernel tree, so can be enabled via a custom defconfig. This would need
adding to OEs metadata, but is fairly simple. First you need to know
which kernel is being built for your machine, assuming your machine is
"foo" and OE is building the stock 2.6.32 kernel (I think you can check
by running 'opkg list | grep "kernel -" ' on your board), then add your
edited defconfig as
"openembedded/recipes/linux/linux-2.6.32/foo/defconfig". The config
currently used is probably here already, so that just needs to be modified.

2) Userspace libraries - I have a bitbake file for version 0.8.1 that I
hadn't got around to pushing yet (didn't think there would be any
interest either). I'll push that in a minute. You will either need to
add it to the bitbake image you want to build or you can add it and it's
dependencies at run time using the package manager (opkg).

Clean the kernel and (I think) task-base and rebuild your image.

Hope that helps,

Martyn

-- 
Martyn Welch (Principal Software Engineer)   |   Registered in England and
GE Intelligent Platforms                     |   Wales (3828642) at 100
T +44(0)127322748                            |   Barbirolli Square, Manchester,
E martyn.welch@ge.com                        |   M2 3AB  VAT:GB 927559189




  parent reply	other threads:[~2010-06-15  8:37 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-15  7:15 comedi / angstrom superaorta
2010-06-15  7:22 ` Frans Meulenbroeks
2010-06-15  8:06   ` superaorta
2010-06-15  8:17 ` Martyn Welch [this message]
2010-06-15  9:02   ` superaorta
2010-06-15  9:33     ` Martyn Welch

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=4C173712.3070405@ge.com \
    --to=martyn.welch@ge.com \
    --cc=openembedded-devel@lists.openembedded.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox