tiomap-dev team mailing list archive

[Ricardo Salveti <rsalveti@xxxxxxxxxxxx>]

Checking for a v4l device in this case is not enough, you'd need to try
to use it before knowing that it's broken.

While I agree that something can be done at the kernel side, I believe
having a better error checking code at ubiquity for devices that fail
when accessing it might be something good to have.

** Also affects: linux-ti-omap4 (Ubuntu)
   Importance: Undecided
       Status: New

-- 
You received this bug notification because you are a member of TI OMAP
Developers, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/924419

Title:
  oem-config detecting camera where no camera exists

Status in “linux-ti-omap4” package in Ubuntu:
  New
Status in “ubiquity” package in Ubuntu:
  Incomplete

Bug description:
  On omap4, the camera module is built into the kernel for development
  purposes, and creates a /dev/video0 device, but there is no actual
  camera.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: oem-config 2.9.15
  ProcVersionSignature: User Name 3.2.0-1405.7-omap4 3.2.1
  Uname: Linux 3.2.0-1405-omap4 armv7l
  ApportVersion: 1.91-0ubuntu1
  Architecture: armel
  Date: Tue Jan 31 10:00:22 2012
  PackageArchitecture: all
  ProcEnviron:
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubiquity
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-ti-omap4/+bug/924419/+subscriptions