[CFP] ICAT 2013: Paper deadline extended!!!
EXTENDED DEADLINE AUGUST 24th: Due to multiple conflicting deadlines and the fact that many people are in the middle of an extensive examination period, we received many requests for a deadline extension. Therefore, the deadline for regular paper submission to ICAT 2013 has been extended to August 24th. === ICAT 2013: The 23rd International Conference on Artificial Reality and Telexistence, December 11-13, 2013, Miraikan, Tokyo, Japan http://www.ic-at.org/2013/ IMPORTANT DATES Papers: Submission Deadline: August 24, 2013 <- The deadline has been extended!!! Acceptance Notification: September 30, 2013 Camera-Ready Deadline: October 21, 2013 Posters and Demos: Submission Deadline : October 4, 2013 Acceptance Notification: October 18, 2013 Camera Ready Due : November 1, 2013 ICAT 2013 Conference: December 11-13, 2013 === ICAT (International Conference on Artificial Reality and Telexistence) is the oldest established international conference on Virtual Reality (VR) and Telexistence. Started in 1991, ICAT has annually brought together VR, MR, and Telerobotics researchers from around the globe. It has been held in different locations in Asia, Oceania, and Europe. VR and Telexistence have the potential to augment human ability in perception, understanding, and action in time and space. The technologies that are the focus of this research community also make it possible for humans to be seemingly anywhere at any given time, thus providing humans virtually ubiquitous impact and interaction possibilities. ICAT 2013 will not only look for innovations in VR technology itself, but also explore novel ways to express and transfer information and creative ideas to societies and their people. ICAT 2013 will include technical sessions covering traditional VR areas as well as new emerging areas with a lineup of plenary sessions, invited talks, technical tours, and technology/art exhibitions. The organizing committee cordially invites you to submit original technical work and experimental results related to Virtual Reality to this conference. Each submission will be refereed on the basis of technical quality, novelty, significance, and clarity. We invite contributions on a broad range of topics, such as Artificial Reality / Virtual Reality Teleoperation / Telepresence / Telexistence Augmented Reality / Mixed Reality Motion Tracking Real Time Computer Simulation Ubiquitous / Wearable Computing Visual and Auditory Displays Anthropomorphic Intelligent Robotics Software Architectures for VR Immersive Projection Technologies Retroreflective Projection Technologies (RPT) Tools for Modeling VR Systems Haptics Multi/Cross-Modal Interfaces Evaluation of VR Techniques and Systems Distributed and Collaborative VR Systems Augmented Humans Natural User Interfaces Brain-Machine Interfaces / Brain-Computer Interfaces Human Robot Interaction Medical VR/AR - Information for Authors ICAT 2013 uses a single-blind review process. Outstanding original paper submissions, as identified by the review process, will be accepted as oral presentations or poster presentations. Authors of accepted papers will be responsible for preparing a final camera- ready electronic version of their paper. The copyright of the final papers must be transferred to VRSJ (The Virtual Reality Society of Japan). Accepted papers will be published in the conference proceedings distributed on USB flash drives and archived on the ICAT webpage. The ICAT 2013 is supported by IEEE Technical Co-sponsorship. Accepted papers will be archived via IEEE Xplore after the conference. ICAT 2013 reserves the right to exclude a paper from distribution after the conference (e.g., removal from IEEE Xplore) if the paper is not presented at the conference. In particular, a paper accepted for the ICAT 2013 technical program will not be published at IEEE Xplore if its authors do not present the paper at the conference. - Submission Instructions Authors should submit papers through an electronic submission system, which will be announced at the conference URL: http://www.ic-at.org/2013/ Papers have to be written in English and can be of up to 8 pages in length. They must be formatted according to the IEEE Computer Society VGTC authoring guidelines: http://www.cs.sfu.ca/~vis/Tasks/camera.html Authors can submit one ZIP file as supplemental material, including movies, images, etc. The maximum total storage size of the paper and the supplemental material will be announced with the submission instructions. - Organization Committee General Co-chairs: Susumu Tachi Masahiko Inami Program Co-Chairs: Hideo Saito Tobias Hollerer Christian Sandor Organizing Co-chairs: Maki Sugimoto Kouta Minamizawa For more information, please visit http://www.ic-at.org/2013/ -- To unsubscribe from this
[PATCH v2] introduce gspca-stk1135: Syntek STK1135 driver
Hello,
this is a new gspca driver for Syntek STK1135 webcams. The code is completely
new, but register values are based on Syntekdriver (stk11xx) by Nicolas VIVIEN
(http://syntekdriver.sourceforge.net).
Only one webcam type is supported now - vendor 0x174f, device 0x6a31.
It's Asus F5RL laptop flippable webcam with MT9M112.
The camera works better than in Windows - initializes much faster and
provides more resolutions (the sensor can do almost any resolution - just
add it to the stk1135_modes[] - could this feature be somehow used by
applications to avoid SW scaling?).
Autoflip works too - when the camera is flipped around, the image is flipped
automatically.
Signed-off-by: Ondrej Zary
diff --git a/drivers/media/usb/gspca/Kconfig b/drivers/media/usb/gspca/Kconfig
index 6345f93..4f0c6d5 100644
--- a/drivers/media/usb/gspca/Kconfig
+++ b/drivers/media/usb/gspca/Kconfig
@@ -338,6 +338,15 @@ config USB_GSPCA_STK014
To compile this driver as a module, choose M here: the
module will be called gspca_stk014.
+config USB_GSPCA_STK1135
+ tristate "Syntek STK1135 USB Camera Driver"
+ depends on VIDEO_V4L2 && USB_GSPCA
+ help
+ Say Y here if you want support for cameras based on the STK1135 chip.
+
+ To compile this driver as a module, choose M here: the
+ module will be called gspca_stk1135.
+
config USB_GSPCA_STV0680
tristate "STV0680 USB Camera Driver"
depends on VIDEO_V4L2 && USB_GSPCA
diff --git a/drivers/media/usb/gspca/Makefile b/drivers/media/usb/gspca/Makefile
index c901da0..5855131 100644
--- a/drivers/media/usb/gspca/Makefile
+++ b/drivers/media/usb/gspca/Makefile
@@ -34,6 +34,7 @@ obj-$(CONFIG_USB_GSPCA_SQ905C) += gspca_sq905c.o
obj-$(CONFIG_USB_GSPCA_SQ930X) += gspca_sq930x.o
obj-$(CONFIG_USB_GSPCA_SUNPLUS) += gspca_sunplus.o
obj-$(CONFIG_USB_GSPCA_STK014) += gspca_stk014.o
+obj-$(CONFIG_USB_GSPCA_STK1135) += gspca_stk1135.o
obj-$(CONFIG_USB_GSPCA_STV0680) += gspca_stv0680.o
obj-$(CONFIG_USB_GSPCA_T613) += gspca_t613.o
obj-$(CONFIG_USB_GSPCA_TOPRO)+= gspca_topro.o
@@ -78,6 +79,7 @@ gspca_sq905-objs:= sq905.o
gspca_sq905c-objs := sq905c.o
gspca_sq930x-objs := sq930x.o
gspca_stk014-objs := stk014.o
+gspca_stk1135-objs := stk1135.o
gspca_stv0680-objs := stv0680.o
gspca_sunplus-objs := sunplus.o
gspca_t613-objs := t613.o
diff --git a/drivers/media/usb/gspca/stk1135.c
b/drivers/media/usb/gspca/stk1135.c
new file mode 100644
index 000..5858688
--- /dev/null
+++ b/drivers/media/usb/gspca/stk1135.c
@@ -0,0 +1,685 @@
+/*
+ * Syntek STK1135 subdriver
+ *
+ * Copyright (c) 2013 Ondrej Zary
+ *
+ * Based on Syntekdriver (stk11xx) by Nicolas VIVIEN:
+ * http://syntekdriver.sourceforge.net
+ *
+ * This program is free software; you can redistribute it and/or modify
+ * it under the terms of the GNU General Public License as published by
+ * the Free Software Foundation; either version 2 of the License, or
+ * any later version.
+ *
+ * This program is distributed in the hope that it will be useful,
+ * but WITHOUT ANY WARRANTY; without even the implied warranty of
+ * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
+ * GNU General Public License for more details.
+ *
+ * You should have received a copy of the GNU General Public License
+ * along with this program; if not, write to the Free Software
+ * Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA
+ */
+
+#define pr_fmt(fmt) KBUILD_MODNAME ": " fmt
+
+#define MODULE_NAME "stk1135"
+
+#include "gspca.h"
+#include "stk1135.h"
+
+MODULE_AUTHOR("Ondrej Zary");
+MODULE_DESCRIPTION("Syntek STK1135 USB Camera Driver");
+MODULE_LICENSE("GPL");
+
+
+/* specific webcam descriptor */
+struct sd {
+ struct gspca_dev gspca_dev; /* !! must be the first item */
+
+ u8 pkt_seq;
+ u8 sensor_page;
+
+ bool flip_status;
+ u8 flip_debounce;
+
+ struct v4l2_ctrl *hflip;
+ struct v4l2_ctrl *vflip;
+};
+
+static const struct v4l2_pix_format stk1135_modes[] = {
+ {160, 120, V4L2_PIX_FMT_SBGGR8, V4L2_FIELD_NONE,
+ .bytesperline = 160,
+ .sizeimage = 160 * 120,
+ .colorspace = V4L2_COLORSPACE_SRGB},
+ {176, 144, V4L2_PIX_FMT_SBGGR8, V4L2_FIELD_NONE,
+ .bytesperline = 176,
+ .sizeimage = 176 * 144,
+ .colorspace = V4L2_COLORSPACE_SRGB},
+ {320, 240, V4L2_PIX_FMT_SBGGR8, V4L2_FIELD_NONE,
+ .bytesperline = 320,
+ .sizeimage = 320 * 240,
+ .colorspace = V4L2_COLORSPACE_SRGB},
+ {352, 288, V4L2_PIX_FMT_SBGGR8, V4L2_FIELD_NONE,
+ .bytesperline = 352,
+ .sizeimage = 352 * 288,
+ .colorspace = V4L2_COLORSPACE_SRGB},
+ {640, 480, V4L2_PIX_FMT_SBGGR8, V4L2_FIELD_NONE,
+ .bytesperline = 640,
+ .sizeimage = 640 * 480,
+ .colorspace = V4L2_COLORSPACE_
cron job: media_tree daily build: WARNINGS
This message is generated daily by a cron job that builds media_tree for the kernels and architectures in the list below. Results of the daily build of media_tree: date: Sun Aug 11 19:00:19 CEST 2013 git branch: test git hash: dfb9f94e8e5e7f73c8e2bcb7d4fb1de57e7c333d gcc version:i686-linux-gcc (GCC) 4.8.1 sparse version: v0.4.5-rc1 host hardware: x86_64 host os:3.9-7.slh.1-amd64 linux-git-arm-at91: OK linux-git-arm-davinci: OK linux-git-arm-exynos: OK linux-git-arm-mx: OK linux-git-arm-omap: OK linux-git-arm-omap1: OK linux-git-arm-pxa: OK linux-git-blackfin: OK linux-git-i686: OK linux-git-m32r: OK linux-git-mips: OK linux-git-powerpc64: OK linux-git-sh: OK linux-git-x86_64: OK linux-2.6.31.14-i686: WARNINGS linux-2.6.32.27-i686: WARNINGS linux-2.6.33.7-i686: WARNINGS linux-2.6.34.7-i686: WARNINGS linux-2.6.35.9-i686: WARNINGS linux-2.6.36.4-i686: WARNINGS linux-2.6.37.6-i686: WARNINGS linux-2.6.38.8-i686: WARNINGS linux-2.6.39.4-i686: WARNINGS linux-3.0.60-i686: OK linux-3.10-i686: OK linux-3.1.10-i686: OK linux-3.2.37-i686: OK linux-3.3.8-i686: OK linux-3.4.27-i686: WARNINGS linux-3.5.7-i686: WARNINGS linux-3.6.11-i686: WARNINGS linux-3.7.4-i686: WARNINGS linux-3.8-i686: WARNINGS linux-3.9.2-i686: WARNINGS linux-2.6.31.14-x86_64: WARNINGS linux-2.6.32.27-x86_64: WARNINGS linux-2.6.33.7-x86_64: WARNINGS linux-2.6.34.7-x86_64: WARNINGS linux-2.6.35.9-x86_64: WARNINGS linux-2.6.36.4-x86_64: WARNINGS linux-2.6.37.6-x86_64: WARNINGS linux-2.6.38.8-x86_64: WARNINGS linux-2.6.39.4-x86_64: WARNINGS linux-3.0.60-x86_64: OK linux-3.10-x86_64: OK linux-3.1.10-x86_64: OK linux-3.2.37-x86_64: OK linux-3.3.8-x86_64: OK linux-3.4.27-x86_64: WARNINGS linux-3.5.7-x86_64: WARNINGS linux-3.6.11-x86_64: WARNINGS linux-3.7.4-x86_64: WARNINGS linux-3.8-x86_64: WARNINGS linux-3.9.2-x86_64: WARNINGS apps: WARNINGS spec-git: OK sparse version: v0.4.5-rc1 sparse: ERRORS Detailed results are available here: http://www.xs4all.nl/~hverkuil/logs/Sunday.log Full logs are available here: http://www.xs4all.nl/~hverkuil/logs/Sunday.tar.bz2 The Media Infrastructure API from this daily build is here: http://www.xs4all.nl/~hverkuil/spec/media.html -- To unsubscribe from this list: send the line "unsubscribe linux-media" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [RFC PATCH] introduce gspca-stk1135: Syntek STK1135 driver
On Sunday 11 August 2013 11:26:18 Hans de Goede wrote: > Hi, > > On 08/11/2013 12:10 AM, Ondrej Zary wrote: > > Hello, > > this is a new gspca driver for Syntek STK1135 webcams. The code is > > completely new, but register values are based on Syntekdriver (stk11xx) > > by Nicolas VIVIEN (http://syntekdriver.sourceforge.net). > > > > Only one webcam type is supported now - vendor 0x174f, device 0x6a31. > > It's Asus F5RL laptop flippable webcam with MT9M112. > > > > The camera works better than in Windows - initializes much faster and > > provides more resolutions > > You've certainly done this quickly, many thanks for working on this! > > Looks good. Any reason why this is RFC, iow any reason why I should not add > this to my tree and include it in my next pullreq to Mauro ? > > > Autoflip works too - when the camera is flipped around, the image is > > flipped automatically. > > Cool, but I've some comments on the implementation: > > 1) It seems autoflip and manual flip with controls conflict, the manual > setting will be overwritten as soon as the switch is debounced. > I think it would be best to make the manual setting invert (when on) the > setting detected from the switch Yes, that's a problem. Too bad that there's no "autorotate" control in V4L2. Inverting seems like a good idea. > 2) You make the switch control both hflip and vflip, but the way the > flipping works the sensor is not turned upside down, but rotated over its > x-axis, so you should only set vflip based on the switch if I'm not > mistaken. To verify this take a piece of paper, and write on it with large > letters "HELLO" then hold it in front of the camera. It should read > normally on the screen. I believe that in one of the 2 orientations of the > camera it will be mirrored now since you set hflip while it should not be > set I thought that too at first - and changed only vflip. Then noticed that the image is mirrored when the camera is flipped to the back. When the sensor is rotated over its x-axis, the "left" side of the sensor will be on the right side (when you look from the back of the laptop). > 3) Once debounced is over 100, you re-set hflip and vflip every frame, this > causes expensive USB IO, so please cache the current setting and only > change it if it actually needs to change When debounce gets over 100, flip_status is inverted (so it matches the current state reported by camera). Thus, debounce is not incremented in sd_pkt_scan but reset to 0 instead. Maybe the code could be re-arranged somehow to make this more clear. > If you can do a new version with these 3 things fixed I'll happily pull it > into my tree! Working on it now. -- Ondrej Zary -- To unsubscribe from this list: send the line "unsubscribe linux-media" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [RFC PATCH] introduce gspca-stk1135: Syntek STK1135 driver
Hi, On 08/11/2013 12:10 AM, Ondrej Zary wrote: Hello, this is a new gspca driver for Syntek STK1135 webcams. The code is completely new, but register values are based on Syntekdriver (stk11xx) by Nicolas VIVIEN (http://syntekdriver.sourceforge.net). Only one webcam type is supported now - vendor 0x174f, device 0x6a31. It's Asus F5RL laptop flippable webcam with MT9M112. The camera works better than in Windows - initializes much faster and provides more resolutions You've certainly done this quickly, many thanks for working on this! Looks good. Any reason why this is RFC, iow any reason why I should not add this to my tree and include it in my next pullreq to Mauro ? Autoflip works too - when the camera is flipped around, the image is flipped automatically. Cool, but I've some comments on the implementation: 1) It seems autoflip and manual flip with controls conflict, the manual setting will be overwritten as soon as the switch is debounced. I think it would be best to make the manual setting invert (when on) the setting detected from the switch 2) You make the switch control both hflip and vflip, but the way the flipping works the sensor is not turned upside down, but rotated over its x-axis, so you should only set vflip based on the switch if I'm not mistaken. To verify this take a piece of paper, and write on it with large letters "HELLO" then hold it in front of the camera. It should read normally on the screen. I believe that in one of the 2 orientations of the camera it will be mirrored now since you set hflip while it should not be set 3) Once debounced is over 100, you re-set hflip and vflip every frame, this causes expensive USB IO, so please cache the current setting and only change it if it actually needs to change If you can do a new version with these 3 things fixed I'll happily pull it into my tree! Regards, Hans -- To unsubscribe from this list: send the line "unsubscribe linux-media" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
