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 10:33:57 +0100	[thread overview]
Message-ID: <4C174905.5020701@ge.com> (raw)
In-Reply-To: <201006151002.35045.superaorta@gmail.com>

superaorta@gmail.com wrote:
>> 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.
>   

Some appear to be there, however it's only a handful. You could add a
patch (look in the .bb file for the kernel below and the associated
directory. The patch is usually named in "SRC_URI" or "SRC_URI_foo"
(assuming foo again) and the patch is placed in the associated
directory. You'll probably need to pull any patches out of OE that are
added for your board to build a usable kernel, in addition to patching
it to provide the Comedi driver you need, so you are probably going to
need to understand a bit about OE to do that.

> 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.
>
>   

It's probably moved on. You'll probably need to do a complete build, or
ask some specific questions WRT the (I assume pre-built) build you are
running and how to generate extra packages. Though I'm afraid I can't be
of much assistance there, I run OE mainly on x86 and PPC at the moment.

> 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...
>
>   

I assume that it's just the build system, i.e. Bitbake. That's not going
to get you very far - you will still need the metadata and build an
image for the board. In some respects it will be harder as the version
of Bitbake may be out of sync with the metadata and the approach you
will need to take may vary subtly from that which is documented for OE.

Comedi is probably packaged for Ubuntu, but I not sure this is going to
run on your board. A quite search makes me think that Ubuntu may do an
Embedded OMAP build, but I'm not sure what that has to do with Bitbake.

Which OE tree are you trying to use, "org.openembeded.dev",
"stable-2009" or something else?

> Thanks for your help,
>   

np,

Martyn
> SA
>
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
>   


-- 
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




      reply	other threads:[~2010-06-15 11:24 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
2010-06-15  9:33     ` Martyn Welch [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=4C174905.5020701@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