On 2013-10-31 17:08, Edward Vidal wrote:
Hello,
I had just recently built angstrom a few days ago. I tried the kernel that was
built with 3.2.28 with the same results still not getting a /dev/video0.
I did the following steps since angstrom uses meta-beagleboard, in hopes of
getting a kernel 3.8 version.
git commit -a
git checkout -b wkg-angstrom-v2013.06-yocto1.4 origin/angstrom-v2013.06-yocto1.4
./oebb.sh config beagleboard
./oebb.sh update
. .oe/environment-angstrom-v2013.06
MACHINE=beagleboard bitbake console-image
rm -rf build/tmp-angstrom_v2012_12-eglibc/
Even with meta-beagleboard at
commit cdaa65dba20da97be7793404bcc90c498771fb04
Author: Koen Kooi <k...@dominion.thruhere.net
<mailto:k...@dominion.thruhere.net>>
Date: Wed Oct 30 18:31:21 2013 +0100
contrib: bone-flash-tool: use --numeric-owner with tar to keep file
ownershi
Signed-off-by: Koen Kooi <k...@dominion.thruhere.net
<mailto:k...@dominion.thruhere.net>>
Which is a dylan branch it still was building a 3.2.28 kernel
git checkout -b 3.8 feb3ea180018d0f
commit feb3ea180018d0f64f406f208827413b91122b07
Author: Koen Kooi <k...@dominion.thruhere.net
<mailto:k...@dominion.thruhere.net>>
Date: Sun Oct 27 17:17:06 2013 +0100
linux-mainline 3.8: ADC and MIDI cape patches
Signed-off-by: Koen Kooi <k...@dominion.thruhere.net
<mailto:k...@dominion.thruhere.net>>
It still tries to build a 3.2.28 kernel.
What should I do to force it to build the 3.8 kernel?
Both meta-beagleboard and meta-ti seem to be stuck at 3.2.28 for the
BeagleBoard. Not unlike
my cell phone, old devices get left in the dust (even if they are only weeks
old...)!
You might try building with meta-yocto-bsp as it will build 3.10+
Any and all help will be appreciated.
Thanks to all
On Thu, Oct 31, 2013 at 11:08 AM, Khem Raj <raj.k...@gmail.com
<mailto:raj.k...@gmail.com>> wrote:
On Thu, Oct 31, 2013 at 9:54 AM, Edward Vidal <vidal.devel...@gmail.com
<mailto:vidal.devel...@gmail.com>> wrote:
> hello,
> I removed the bus
> udevadm test --action=add /usr/src/kernel/sysfs
>
> run_command: calling: test
> adm_test: version 182
> This program is for debugging only, it does not run any program,
> specified by a RUN key. It may show incorrect results, because
> some values may be different, or not available at a simulation run.
>
> builtin_kmod_init: load module index
> add_matching_files: unable to open '/var/run/udev/rules.d': No such file
or
> directory
> parse_file: reading '/etc/udev/rules.d/10-c920.rules' as rules file
> still no /dev/video0
>
> cat /etc/udev/rules.d/10-c920.rules
> SUBSYSTEM=="video4linux", ATTRS{idvendor}=="0x046d",
> ATTRS{idProduct}=="0x082d", NAME="video0", MODE:="0660", RUN="/bin/mknod
> /dev/video0 c 81 0"
> still no /dev/video0
> The camera is working correctly on my fedora 18 x86_64.
OK so atleast your rules file is correct syntax wise. Why not try the
3.8 kernel from meta-beagleboard ?
>
> Note:
> * Before camera connected
> ** After camera connected
> Linuxsim4.swbell.net <http://sim4.swbell.net> 3.9.2-200.fc18.x86_64 #1
SMP Mon May 13 13:59:47 UTC
> 2013 x86_64 x86_64 x86_64 GNU/Linux
>
> Module Size Used by
> **snd_usb_audio 145223 1
> **snd_usbmidi_lib 24713 1 snd_usb_audio
> **snd_rawmidi 29531 1 snd_usbmidi_lib
>
> *snd_hwdep 17650 1 snd_hda_codec
> **snd_hwdep 17650 2 snd_usb_audio,snd_hda_codec
>
> *snd_seq_device 14136 1 snd_seq
> **snd_seq_device 14136 2 snd_seq,snd_rawmidi
>
> *snd 79379 19
>
snd_hda_codec_realtek,snd_hwdep,snd_timer,snd_hda_codec_hdmi,snd_pcm,snd_seq,snd_hda_codec,snd_hda_intel,snd_seq_device
> **snd 79379 24
>
snd_hda_codec_realtek,snd_usb_audio,snd_hwdep,snd_timer,snd_hda_codec_hdmi,snd_pcm,snd_seq,snd_rawmidi,snd_usbmidi_lib,snd_hda_codec,snd_hda_intel,snd_seq_device
>
> *video 18991 0
> **video 18991 0
>
> This is the beagleboard
> lsmod
> Module Size Used by
> nls_iso8859_1 3673 1
> nls_cp437 5339 1
> I am going to be checking the video is a module or built into the kernel
of
> the
> uname -a
> Linux beagleboard 3.4.36-yocto-standard #1 Mon Oct 28 21:58:22 MDT 2013
> armv7l GNU/Linux
>
> Thanks
>
>
> On Thu, Oct 31, 2013 at 10:23 AM, Khem Raj <raj.k...@gmail.com
<mailto:raj.k...@gmail.com>> wrote:
>>
>> On Thu, Oct 31, 2013 at 8:45 AM, Edward Vidal <vidal.devel...@gmail.com
<mailto:vidal.devel...@gmail.com>>
>> wrote:
>> >
>> > Do I add RUN+="/bin/mknod /dev/video0 c 81 0" see below new version of
>> > 1--c920.rules
>> > cat 10-c920.rules
>> > SUBSYSTEM=="video4linux", BUS=="usb", ATTRS{idvendor}=="0x046d",
>> > ATTRS{idProduct}=="0x082d", NAME="video0", MODE:="0660",
>> > RUN+="/bin/mknod
>> > /dev/video0 c 81 0"
>>
>> get rid of BUS construct there
>
>
_______________________________________________
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
--
------------------------------------------------------------
Gary Thomas | Consulting for the
MLB Associates | Embedded world
------------------------------------------------------------
_______________________________________________
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
