Openembedded Devel Discussions
 help / color / mirror / Atom feed
* comedi / angstrom
@ 2010-06-15  7:15 superaorta
  2010-06-15  7:22 ` Frans Meulenbroeks
  2010-06-15  8:17 ` Martyn Welch
  0 siblings, 2 replies; 6+ messages in thread
From: superaorta @ 2010-06-15  7:15 UTC (permalink / raw)
  To: Openembedded-devel


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.

Cheers,

SA




^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: comedi / angstrom
  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
  1 sibling, 1 reply; 6+ messages in thread
From: Frans Meulenbroeks @ 2010-06-15  7:22 UTC (permalink / raw)
  To: openembedded-devel

2010/6/15  <superaorta@gmail.com>:
>
> 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

If you are lost in Angstrom better mail to the angstrom mailing list :-)

> 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

if you do not want to use bitbake the openembedded mailing list does
not seem to be the proper place to ask questions, as all of oe uses
bitbake.

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

bitbake virtual/kernel will build a kernel for you, you might be lucky
copying over that kernel.
>
> Any advice? overwhelmed and stuck here.
>
> Cheers,
>
> SA
>
>
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
>



^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: comedi / angstrom
  2010-06-15  7:22 ` Frans Meulenbroeks
@ 2010-06-15  8:06   ` superaorta
  0 siblings, 0 replies; 6+ messages in thread
From: superaorta @ 2010-06-15  8:06 UTC (permalink / raw)
  To: openembedded-devel

On Tuesday 15 June 2010 08:22:22 Frans Meulenbroeks wrote:
> 2010/6/15  <superaorta@gmail.com>:
> > 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
>
> If you are lost in Angstrom better mail to the angstrom mailing list :-)
>
> > 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
>
> if you do not want to use bitbake the openembedded mailing list does
> not seem to be the proper place to ask questions, as all of oe uses
> bitbake.
>
> > 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.
>
> bitbake virtual/kernel will build a kernel for you, you might be lucky
> copying over that kernel.
>
Any chance you could offer some useful advice, maybe tell me something helpful 
or something that I don't already know? Like I said, I have a running kernel, 
I just want the source tree and the config files.  Comedi is slightly less 
than trivial to build out of place and the easiest solution is to get the 
kernel source and config files and build it in situ.





^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: comedi / angstrom
  2010-06-15  7:15 comedi / angstrom superaorta
  2010-06-15  7:22 ` Frans Meulenbroeks
@ 2010-06-15  8:17 ` Martyn Welch
  2010-06-15  9:02   ` superaorta
  1 sibling, 1 reply; 6+ messages in thread
From: Martyn Welch @ 2010-06-15  8:17 UTC (permalink / raw)
  To: openembedded-devel

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




^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: comedi / angstrom
  2010-06-15  8:17 ` Martyn Welch
@ 2010-06-15  9:02   ` superaorta
  2010-06-15  9:33     ` Martyn Welch
  0 siblings, 1 reply; 6+ messages in thread
From: superaorta @ 2010-06-15  9:02 UTC (permalink / raw)
  To: openembedded-devel


> 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



^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: comedi / angstrom
  2010-06-15  9:02   ` superaorta
@ 2010-06-15  9:33     ` Martyn Welch
  0 siblings, 0 replies; 6+ messages in thread
From: Martyn Welch @ 2010-06-15  9:33 UTC (permalink / raw)
  To: openembedded-devel

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




^ permalink raw reply	[flat|nested] 6+ messages in thread

end of thread, other threads:[~2010-06-15 11:24 UTC | newest]

Thread overview: 6+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
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 is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox