Date: Tue, 10 Apr 2018 17:16:12 +0000 (UTC) From: LinkedIn <security-noreply@linkedin.com> To: =?UTF-8?Q?Micha=C5=82_Hendzel?= <freebsd-multimedia@FreeBSD.ORG> Subject: Update primary email address Message-ID: <438035238.1151302.1523380572624.JavaMail.app@lor1-app12633.prod.linkedin.com>
next in thread | raw e-mail | index | archive | help
Micha=C5=82, We've noticed the primary email address associated with your LinkedIn accou= nt can no longer receive emails from LinkedIn. To make sure you don't miss any invitations to connect, messages, or update= s on LinkedIn, you can: Add a different email address: https://www.linkedin.com/e/v2?e=3D4zmfs-jftxgd43-qj&lipi=3Durn%3Ali%3Apage%= 3Aemail_email_account_access_bouncing_eml_notice_01%3BNMzxHwGLSvinRJTMyEcgK= A%3D%3D&a=3Dpsettings-email-summary&midToken=3DAQHLzWiv-C-enw&ek=3Demail_ac= count_access_bouncing_eml_notice_01&li=3D0&m=3Dhero&ts=3Dadd-new-email Keep your primary address by re-confirming your email address: https://www.linkedin.com/e/v2?e=3D4zmfs-jftxgd43-qj&lipi=3Durn%3Ali%3Apage%= 3Aemail_email_account_access_bouncing_eml_notice_01%3BNMzxHwGLSvinRJTMyEcgK= A%3D%3D&a=3Dpsettings-email-summary&midToken=3DAQHLzWiv-C-enw&ek=3Demail_ac= count_access_bouncing_eml_notice_01&li=3D1&m=3Dhero&ts=3Dreconfirm-primary-= email Visit our help center if you believe this notice was sent by mistake: https://www.linkedin.com/e/v2?e=3D4zmfs-jftxgd43-qj&lipi=3Durn%3Ali%3Apage%= 3Aemail_email_account_access_bouncing_eml_notice_01%3BNMzxHwGLSvinRJTMyEcgK= A%3D%3D&t=3Dplh&midToken=3DAQHLzWiv-C-enw&ek=3Demail_account_access_bouncin= g_eml_notice_01&li=3D2&m=3Dhero&ts=3Dhelp-center&urlhash=3Dw9ic&url=3Dhttps= %3A%2F%2Fwww%2Elinkedin%2Ecom%2Fhelp%2Flinkedin%2Ftopics%2F6001%2F6018 Thank you for being a member of LinkedIn. ..................................... This email was intended for Micha=C5=82 Hendzel (Senior Software Engineer a= t BERNINA International AG). Learn why we included this: https://www.linkedin.com/e/v2?e=3D4zmfs-jftxgd4= 3-qj&lipi=3Durn%3Ali%3Apage%3Aemail_email_account_access_bouncing_eml_notic= e_01%3BNMzxHwGLSvinRJTMyEcgKA%3D%3D&a=3DcustomerServiceUrl&midToken=3DAQHLz= Wiv-C-enw&ek=3Demail_account_access_bouncing_eml_notice_01&articleId=3D4788 =C2=A9 2018 LinkedIn Ireland Unlimited Company, Wilton Plaza, Wilton Place,= Dublin 2. LinkedIn is a registered business name of LinkedIn Ireland Unlim= ited Company. LinkedIn and the LinkedIn logo are registered trademarks of L= inkedIn. From owner-freebsd-multimedia@freebsd.org Wed Apr 11 02:40:00 2018 Return-Path: <owner-freebsd-multimedia@freebsd.org> Delivered-To: freebsd-multimedia@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 240C7F8C528 for <freebsd-multimedia@mailman.ysv.freebsd.org>; Wed, 11 Apr 2018 02:40:00 +0000 (UTC) (envelope-from curtis@orleans.occnc.com) Received: from mta1-em1.orleans.occnc.com (mta1-em1.orleans.occnc.com [IPv6:2001:470:88e6:1::141]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mta1.orleans.occnc.com", Issuer "OCCNC secondary CA (ca1a2a)" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id B1AE969694 for <freebsd-multimedia@freebsd.org>; Wed, 11 Apr 2018 02:39:59 +0000 (UTC) (envelope-from curtis@orleans.occnc.com) Received: from harbor1.v6only.occnc.com (harbor1-em2.v6only.occnc.com [IPv6:2001:470:88e6:2::230]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) (Authenticated sender: curtis@occnc.com) by mta1-em1.orleans.occnc.com (Postfix) with ESMTPSA id 0BAD81250D; Tue, 10 Apr 2018 22:39:58 -0400 (EDT) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=orleans.occnc.com; s=curtis-orleans-20180228-204217; t=1523414399; bh=S/+vZtyZR4in6FeH3ehWQTbnWAfgTsAGt65zvhN8GlU=; h=To:cc:Reply-To:From:Subject:In-reply-to:Date; b=DvIwbSrFev8lkqNXEHjqEUyUpHhnXpIQq+2T617M8MCP+Ktos1WDouoM7McV4p1pu NIKkWafp/yKxt9rxGbkuXZkx7hItfPMVXjJJAgEs+XEdgKOydrm4+qiwg9w19YeLc0 LSFmryH0aPs9lsYlw27wt4bXwYoA7MbIy62yxbdh+TTuBsPmaj9CB0rt2IPZKTYeNg wBsb4OnACQeOHKnrJeNHCr6PBavQnBq6Md0NaxyGGN0WHl7gKeDQSHGz6gNuc96kyE t9Gh27eFKAOyfsYn289oxAsVv/dOzKDGWB2uP6K+ni1Yz9DdzCcfYomrRCAz/7NIZv nZBDld1hK1Qeg== To: Hans Petter Selasky <hps@selasky.org> cc: Curtis Villamizar <curtis@orleans.occnc.com>, freebsd-multimedia@freebsd.org Reply-To: Curtis Villamizar <curtis@orleans.occnc.com> From: Curtis Villamizar <curtis@orleans.occnc.com> Subject: Re: video using webcamd on Raspberry Pi 3 In-reply-to: Your message of "Tue, 03 Oct 2017 10:00:37 +0200." <23bc6bc5-d255-4e9b-ab46-aa712cfe6673@selasky.org> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <13233.1523409429.1@harbor1-em2.v6only.occnc.com> Date: Tue, 10 Apr 2018 21:17:09 -0400 X-BeenThere: freebsd-multimedia@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Multimedia discussions <freebsd-multimedia.freebsd.org> List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-multimedia>, <mailto:freebsd-multimedia-request@freebsd.org?subject=unsubscribe> List-Archive: <http://lists.freebsd.org/pipermail/freebsd-multimedia/>; List-Post: <mailto:freebsd-multimedia@freebsd.org> List-Help: <mailto:freebsd-multimedia-request@freebsd.org?subject=help> List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-multimedia>, <mailto:freebsd-multimedia-request@freebsd.org?subject=subscribe> X-List-Received-Date: Wed, 11 Apr 2018 02:40:00 -0000 HPS, Resurrecting 6+ month old thread. The two cameras that I had tried with Raspberry Pi 3 still don't work with a recent FreeBSD-12 build. I waited a while since there was work going on in USB and in ARM support in FreeBSD 12, in hopes this would just fix itself (it didn't). These two cameras work fine with an Orange Pi PC Plus (OPiPC+) and I'll be testing shortly with Orange Pi One (should work, same H3 SoC). I'm going with Orange Pi for this project as I don't want to keep fussing with RPi3. Earlier testing was with webcamd, cuse, and multimedia/pwcview. Motion (multimedia/motion) is now being used on OPiPC+. If you would like you can have root on my RPi3 and I'll plug in one of the cameras and let you play all you want. I'm building using crochet and would be willing to try whatever kernel patches you'd like and reboot now and then. You can rebuild anything in ports yourself. I'll just wipe the SD card when you're done. I can give this thing a routeable IPv6 address. Send me private email if you are willing to do this. Would you like me to report a bug on this so it can be tracked? Curtis ps - good news is the "motion" application now works where it didn't last October (lots of code changes in that port) and that port is just about perfect for what I want to do. In message <23bc6bc5-d255-4e9b-ab46-aa712cfe6673@selasky.org> Hans Petter Selasky writes: > On 09/30/17 22:49, Curtis Villamizar wrote: > On 09/30/17 14:11, Hans Petter Selasky wrote: >> lsusb -v > > The output is 740 lines long. Here are the bDescriptorSubtype lines: > > bDescriptorSubtype 1 (HEADER) > bDescriptorSubtype 3 (OUTPUT_TERMINAL) > bDescriptorSubtype 6 (EXTENSION_UNIT) > bDescriptorSubtype 2 (INPUT_TERMINAL) > bDescriptorSubtype 5 (PROCESSING_UNIT) > bDescriptorSubtype 1 (INPUT_HEADER) > bDescriptorSubtype 6 (FORMAT_MJPEG) > bDescriptorSubtype 7 (FRAME_MJPEG) > bDescriptorSubtype 7 (FRAME_MJPEG) > bDescriptorSubtype 7 (FRAME_MJPEG) > bDescriptorSubtype 7 (FRAME_MJPEG) > bDescriptorSubtype 7 (FRAME_MJPEG) > bDescriptorSubtype 7 (FRAME_MJPEG) > bDescriptorSubtype 7 (FRAME_MJPEG) > bDescriptorSubtype 7 (FRAME_MJPEG) > bDescriptorSubtype 3 (STILL_IMAGE_FRAME) > bDescriptorSubtype 4 (FORMAT_UNCOMPRESSED) > bDescriptorSubtype 5 (FRAME_UNCOMPRESSED) > bDescriptorSubtype 5 (FRAME_UNCOMPRESSED) > bDescriptorSubtype 5 (FRAME_UNCOMPRESSED) > bDescriptorSubtype 5 (FRAME_UNCOMPRESSED) > bDescriptorSubtype 5 (FRAME_UNCOMPRESSED) > bDescriptorSubtype 5 (FRAME_UNCOMPRESSED) > bDescriptorSubtype 5 (FRAME_UNCOMPRESSED) > bDescriptorSubtype 5 (FRAME_UNCOMPRESSED) > bDescriptorSubtype 3 (STILL_IMAGE_FRAME) > bDescriptorSubtype 13 (COLORFORMAT) > bDescriptorSubtype 1 (HEADER) > bDescriptorSubtype 2 (INPUT_TERMINAL) > bDescriptorSubtype 6 (FEATURE_UNIT) > bDescriptorSubtype 3 (OUTPUT_TERMINAL) > bDescriptorSubtype 1 (AS_GENERAL) > bDescriptorSubtype 2 (FORMAT_TYPE) > bDescriptorSubtype 1 (EP_GENERAL) > > The format is MJPEG or raw. > > For the resolution of 320x240 we have: > > VideoStreaming Interface Descriptor: > bLength 30 > bDescriptorType 36 > bDescriptorSubtype 7 (FRAME_MJPEG) > bFrameIndex 4 > bmCapabilities 0x00 > Still image unsupported > wWidth 320 > wHeight 240 > dwMinBitRate 37005360 > dwMaxBitRate 37005360 > dwMaxVideoFrameBufferSize 154189 > dwDefaultFrameInterval 333333 > bFrameIntervalType 1 > dwFrameInterval( 0) 333333 > > VideoStreaming Interface Descriptor: > bLength 30 > bDescriptorType 36 > bDescriptorSubtype 5 (FRAME_UNCOMPRESSED) > bFrameIndex 4 > bmCapabilities 0x00 > Still image unsupported > wWidth 320 > wHeight 240 > dwMinBitRate 36864000 > dwMaxBitRate 36864000 > dwMaxVideoFrameBufferSize 153600 > dwDefaultFrameInterval 333333 > bFrameIntervalType 1 > dwFrameInterval( 0) 333333 > > This still doesn't work with 160x120 and 5 fps so probably not a CPU > issue, but I could be wrong. OTOH I just got a kernel panic while > running 160x120. It doesn't seem related based on where it was. I'm > running that again and no panic so far but also nothing on the screen > even after quite a few minutes. > Hi, Can you check dmesg if there are any errors? Can you further check "top" for CPU usage. --HPS
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?438035238.1151302.1523380572624.JavaMail.app>