From: superaorta@gmail.com
To: openembedded-devel@lists.openembedded.org
Subject: Re: comedi / angstrom
Date: Tue, 15 Jun 2010 10:02:34 +0100 [thread overview]
Message-ID: <201006151002.35045.superaorta@gmail.com> (raw)
In-Reply-To: <4C173712.3070405@ge.com>
> 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,
thanks - this looks promising but I think there is an added complication - I
am running 2.6.29 on the board and I think the comedi drivers were moved to
kernel staging after this time.
opkg list |grep "kernel -"
kernel - 2.6.29-r46.1 - Linux kernel for OMAP processors
To be honest I think I am out of my depth on this and very short of time- I
have had the BB running a stock system for a long while and haven't touched
this, the git / bitbake system I setup yesterday on my linux box doesn't seem
to match it and I haven't a clue what I am doing with it.
I think I'm going to try the ubuntu bb install, I understand debian etc a bit
better and I think comedi is ready packaged for unbuntu...
Thanks for your help,
SA
next prev parent reply other threads:[~2010-06-15 9:07 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
2010-06-15 9:02 ` superaorta [this message]
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=201006151002.35045.superaorta@gmail.com \
--to=superaorta@gmail.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