Thanks Robert. I must admit I am much more comfortable with that
approach, than with bitbake/Angstrom recipes.
Dave.
On 12/05/2013 03:53 PM, Robert Nelson wrote:
On Thu, Dec 5, 2013 at 3:48 PM, David Lambert <d...@lambsys.com> wrote:
On 12/05/2013 03:37 PM, Robert Nelson wrote:
On Thu, Dec 5, 2013 at 3:33 PM, David Lambert <d...@lambsys.com> wrote:
Mainly due to some frustrations around opencv Python support in Angstrom,
I
am investigating switching to the Debian distribution. I have followed
Robert Nelson's excellent tutorials and scripts, but need some guidance
in
adding my own kernel modules and device trees. I have already
successfully
built them under Angstrom/bitbake, but cannot determine the preferred or
"correct" workflow for Debian. Any help would be greatly appreciated.
Hi Dave,
What kernel modules/device tree's do you need enabled?
Thanks for your quick reply.
These are modules/dts that I have written to support a UPS/watchdog cape I
am developing. They are building and working fine with the 3.8 Angstrom
kernel using the attached bitbake recipe. My question is what are the
magical incantations I need to build these outside the kernel tree? I
suspect there is a "correct" way to do this under Debian, rather than me
re-inventing a wheel.
Well, the best option is to write a patch against:
https://github.com/beagleboard/kernel/tree/3.8
and then i'll merge it into both tree's and push out a new
debian/ubuntu kernel build. .;) So everyone get's the patch and
supports your new cape out of the box...
Regards,
--
For more options, visit http://beagleboard.org/discuss
---
You received this message because you are subscribed to the Google Groups "BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
