Thanks Micka. I was considering just removing the request to capemgr via
uEnv.txt, and writing a service to populate the slot. Ultimately the
loading should be taken care of via the EEPROM signature, but that has
not yet been implemented. I was just curious as to what was the
difference
Robert,
I switched to systemd, but the problem still exists. Is there a guide on
debugging the cape manager? The only messages I see are:
[2.559511] bone-capemgr bone_capemgr.9: failed to load firmware
'argus-ups-00A0.dtbo'
[2.567868] bone-capemgr bone_capemgr.9: loader: failed to
In desperation, I added a printk to capemgr to print out the return
value from request_firmware. I get -2 ENOENT, but the file name is in
/lib/firmware exactly as printed in the error line. Another thought is
that Debian appears to use initrd, whereas I don't think Angstrom does?
Could this be
Why not disabling the cap manager at the boot (is it possible?) and later
push yourself the config that you want in the slot?
Micka,
On Dec 10, 2013 5:50 AM, David Lambert d...@lambsys.com wrote:
On 12/09/2013 05:12 PM, Robert Nelson wrote:
On Mon, Dec 9, 2013 at 2:15 PM, David Lambert
On 12/05/2013 03:53 PM, Robert Nelson wrote:
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
optargs=capemgr.disable_partno=BB-BONELT-HDMI,BB-BONELT-HDMIN
On Fri, Dec 6, 2013 at 10:48 AM, David Lambert d...@lambsys.com wrote:
On 12/05/2013 03:53 PM, Robert Nelson wrote:
Well, the best option is to write a patch against:
https://github.com/beagleboard/kernel/tree/3.8
and then
Errr, that is as long as the file names have not changed . . .
I also wanted to point out that that technically uEnv.txt and uboot have
*nothing* to do with the OS in particular. However in this case optargs are
passed to the kernel when it starts up so . ..
On Fri, Dec 6, 2013 at 10:55 AM,
On Fri, Dec 6, 2013 at 12:12 PM, David Lambert d...@lambsys.com wrote:
I may be barking up the wrong tree here, but I also notice that the uboot
partition contains dtbs (see below). Do I need to put my cape's dtb here?
Also I am attaching the uEnv.txt from the Debian system. I am particularly
I may be barking up the wrong tree here, but I also notice that the
uboot partition contains dtbs (see below). Do I need to put my cape's
dtb here? Also I am attaching the uEnv.txt from the Debian system. I am
particularly confused by the line:
loadfdt=load mmc ${mmcdev}:${mmcpart} 0x815f
Thanks Robert. This make perfect sense now. Sorry for the dumb question :-[
Regards,
Dave.
On 12/06/2013 12:19 PM, Robert Nelson wrote:
I'm not sure on your confusion. With Angstrom the bootloader/uEnv.txt
matched each other and since they programmed them at the factory they
had a 100%
On Fri, Dec 6, 2013 at 1:15 PM, David Lambert d...@lambsys.com wrote:
Thanks Robert. This make perfect sense now. Sorry for the dumb question :-[
Not a problem Dave..
BTW, if you used my kernel build script, the config is already setup
to place the *.dtbo's (firmware) into into the kernel
On 12/06/2013 01:20 PM, Robert Nelson wrote:
BTW, if you used my kernel build script, the config is already setup
to place the *.dtbo's (firmware) into into the kernel (zImage). So if
your utilizing a new one, you don't actually have to copy the *.dtbo
to the /lib/firmware/ directory..
Thanks so
On Fri, Dec 6, 2013 at 2:14 PM, David Lambert d...@lambsys.com wrote:
On 12/06/2013 01:20 PM, Robert Nelson wrote:
BTW, if you used my kernel build script, the config is already setup
to place the *.dtbo's (firmware) into into the kernel (zImage). So if
your utilizing a new one, you don't
I think that just a space between the disable / enables lines is all you
need. There are a couple ways I could read your last message as in text
formating etc, but be sure there are no Windows type white spaces or more
specifically what Microsoft OSes call a line feed.
To be succinct: If you're
On 12/06/2013 02:37 PM, William Hermans wrote:
I think that just a space between the disable / enables lines is all
you need. There are a couple ways I could read your last message as in
text formating etc, but be sure there are no Windows type white spaces
or more specifically what Microsoft
On 12/06/2013 02:31 PM, Robert Nelson wrote:
Very strange... Does it help in any way to dump the argus-ups dtbo to
/lib/firmware/ ?
I am not sure what you mean by dump? The dtbo was put in /lib/firmware
by your scripts:
root@debian:~# ls -l /lib/firmware/arg*
-rw-r--r-- 1 dlambert dlambert
Perhaps the HDMI video and audio are not being disabled quickly enough for
your module to load. Another way to load your module would be to write a
startup service. Which you can then load at any point in the Debian startup
cycle. I have a write up of an example here :
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
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
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
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
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
22 matches
Mail list logo
