* Missing /dev/video[N] devices...?
@ 2011-03-02 16:16 Nick Pelling
2011-03-02 18:54 ` Andy Walls
0 siblings, 1 reply; 3+ messages in thread
From: Nick Pelling @ 2011-03-02 16:16 UTC (permalink / raw)
To: linux-media
Hi everyone,
I'm trying to bring up the 2.6.37 kernel from scratch on a new
Samsung S5PC100-based board, but have hit a media problem. Though my
various v4l2 devices are all registering OK during the boot process
and end up visible in /sys/class/video4linux , they never manage to
become visible in /dev , i.e.
# ls /dev/video*
ls: /dev/video*: No such file or directory
# ls /sys/class/video4linux/
video0 video1 video14 video2 video21 video22
# ls /sys/class/video4linux/video0/
dev index name subsystem uevent
# cat /sys/class/video4linux/video0/name
s5p-fimc.0:m2m
# cat /sys/class/video4linux/video0/uevent
MAJOR=81
MINOR=0
DEVNAME=video0
I've tried enabling everything that seems relevant in the kernel's
menuconfig options, but it seems as though I've omitted some crucial
piece of the v4l2 infrastructure. Any suggestions for what's missing?
Thanks!, ....Nick Pelling....
^ permalink raw reply [flat|nested] 3+ messages in thread
* Missing /dev/video[N] devices...?
@ 2011-03-02 17:25 Nick Pelling
0 siblings, 0 replies; 3+ messages in thread
From: Nick Pelling @ 2011-03-02 17:25 UTC (permalink / raw)
To: linux-media
Hi everyone,
Problem solved - the boot sequence didn't have a makedev, so the
/dev/video[N] nodes weren't getting automatically created. A few
"mknod c X Y" commands later, all the /dev/video[N] items are in place. :-)
Cheers, ....Nick Pelling....
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: Missing /dev/video[N] devices...?
2011-03-02 16:16 Nick Pelling
@ 2011-03-02 18:54 ` Andy Walls
0 siblings, 0 replies; 3+ messages in thread
From: Andy Walls @ 2011-03-02 18:54 UTC (permalink / raw)
To: Nick Pelling, linux-media
Nick Pelling <nickpelling@nanodome.com> wrote:
>Hi everyone,
>
>I'm trying to bring up the 2.6.37 kernel from scratch on a new
>Samsung S5PC100-based board, but have hit a media problem. Though my
>various v4l2 devices are all registering OK during the boot process
>and end up visible in /sys/class/video4linux , they never manage to
>become visible in /dev , i.e.
>
> # ls /dev/video*
> ls: /dev/video*: No such file or directory
>
> # ls /sys/class/video4linux/
> video0 video1 video14 video2 video21 video22
>
> # ls /sys/class/video4linux/video0/
> dev index name subsystem uevent
>
> # cat /sys/class/video4linux/video0/name
> s5p-fimc.0:m2m
>
> # cat /sys/class/video4linux/video0/uevent
> MAJOR=81
> MINOR=0
> DEVNAME=video0
>
>I've tried enabling everything that seems relevant in the kernel's
>menuconfig options, but it seems as though I've omitted some crucial
>piece of the v4l2 infrastructure. Any suggestions for what's missing?
>
>Thanks!, ....Nick Pelling....
>
>--
>To unsubscribe from this list: send the line "unsubscribe linux-media"
>in
>the body of a message to majordomo@vger.kernel.org
>More majordomo info at http://vger.kernel.org/majordomo-info.html
I thought udev normally makes those nodes.
On embedded systems there is a different, smaller user space app responding to hotplug events including firmware load requests.
-Andy
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2011-03-02 18:54 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2011-03-02 17:25 Missing /dev/video[N] devices...? Nick Pelling
-- strict thread matches above, loose matches on Subject: below --
2011-03-02 16:16 Nick Pelling
2011-03-02 18:54 ` Andy Walls
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox