On Wed, 2005-08-03 at 07:17 +0200, Martin Wilck wrote:
> Jens Axboe wrote:
>
> >>If I am reading the specs correctly, that'd mean the ahci driver is
> >>wrong in setting the SActive bit.
> >
> > I completely agree, that was my reading of the spec as well and hence my
> > original posts about thi
On Thu, 2005-08-18 at 22:49 +0200, Pavel Machek wrote:
> Please make it "echo 1 > frozen", then userspace can do "echo 0 > frozen"
> after five seconds.
What if the code to do "echo 0 > frozen" is swapped out to disk? ;)
Thanks,
Adam
signature.asc
Description: This is a digitally signed mes
Mac OS X has a similar thing, with a pretty simple description of how
they do it:
http://developer.apple.com/technotes/tn/tn1150.html#HotFile
Adam
On Tue, 2005-02-15 at 13:56 -0600, Linas Vepstas wrote:
> On Tue, Feb 15, 2005 at 12:43:29AM +0100, Diego Calleja was heard to remark:
> >
> > A
(resending in plain text)
(please CC me on replies, I am not on LKML)
Hi,
I have a new Mac Mini (MacMini7,1). This model supports hotplugging of
Thunderbolt on Windows 8 and above. Unfortunately hotplug does not
seem to be working for me under Linux. I get the default behavior of
devices only wor
On Wed, Apr 22, 2015 at 12:05 AM, Adam Goode wrote:
> (resending in plain text)
> (please CC me on replies, I am not on LKML)
>
> Hi,
>
> I have a new Mac Mini (MacMini7,1). This model supports hotplugging of
> Thunderbolt on Windows 8 and above. Unfortunately hotplug
On Thu, Apr 23, 2015 at 6:08 AM, Andreas Noever
wrote:
> Hi Adam,
>
> On my system (MacBookPro10,1 - 4 channel TB1) the bridges and the
> controller both use 0x1547 and are only differentiated by
> subvendor/subdevice.
>
> 0x156c is the 4 channel TB2 controller and was originally added by
> Matthe
On Thu, Apr 23, 2015 at 9:28 AM, Adam Goode wrote:
>
> On Thu, Apr 23, 2015 at 6:08 AM, Andreas Noever
> wrote:
> > Hi Adam,
> >
> > On my system (MacBookPro10,1 - 4 channel TB1) the bridges and the
> > controller both use 0x1547 and are only differen
On Thu, Apr 23, 2015 at 12:12 PM, Andreas Noever
wrote:
> On Thu, Apr 23, 2015 at 5:10 PM, Adam Goode wrote:
>> On Thu, Apr 23, 2015 at 9:28 AM, Adam Goode wrote:
>>>
>>> On Thu, Apr 23, 2015 at 6:08 AM, Andreas Noever
>>> wrote:
>>> > Hi Ad
On Thu, Apr 23, 2015 at 1:15 PM, Adam Goode wrote:
> On Thu, Apr 23, 2015 at 12:12 PM, Andreas Noever
> wrote:
>> On Thu, Apr 23, 2015 at 5:10 PM, Adam Goode wrote:
>>> On Thu, Apr 23, 2015 at 9:28 AM, Adam Goode wrote:
>>>>
>>>> On Thu, Apr 23
On Fri, Apr 24, 2015 at 7:46 AM, Andreas Noever
wrote:
> On Fri, Apr 24, 2015 at 6:50 AM, Adam Goode wrote:
>> On Thu, Apr 23, 2015 at 1:15 PM, Adam Goode wrote:
>>> On Thu, Apr 23, 2015 at 12:12 PM, Andreas Noever
>>> wrote:
>>>> On Thu, Apr 23, 2015
On Fri, Apr 24, 2015 at 2:39 PM, Adam Goode wrote:
> On Fri, Apr 24, 2015 at 7:46 AM, Andreas Noever
> wrote:
>> On Fri, Apr 24, 2015 at 6:50 AM, Adam Goode wrote:
>>> On Thu, Apr 23, 2015 at 1:15 PM, Adam Goode wrote:
>>>> On Thu, Apr 23, 2015 at 12:12 PM, And
On Sat, Apr 25, 2015 at 12:58 AM, Adam Goode wrote:
> On Fri, Apr 24, 2015 at 2:39 PM, Adam Goode wrote:
>> On Fri, Apr 24, 2015 at 7:46 AM, Andreas Noever
>> wrote:
>>> On Fri, Apr 24, 2015 at 6:50 AM, Adam Goode wrote:
>>>> On Thu, Apr 23, 2015 at 1:15
dding Region
[CMS0] 8802658a0438 to address handler 880264160480
[SystemCMOS]
Next step is to figure out how to install the address handler earlier.
Adam
On Sat, Apr 25, 2015 at 10:41 PM, Adam Goode wrote:
> On Sat, Apr 25, 2015 at 12:58 AM, Adam Goode wrote:
>> On Fri, Apr 24, 2
On Sun, Nov 22, 2020 at 2:34 PM Benjamin Drung
wrote:
>
> Am Freitag, den 20.11.2020, 16:45 -0500 schrieb Adam Goode:
> > On Fri, Nov 20, 2020 at 1:52 PM Benjamin Drung
> > wrote:
> > >
> > > Hi,
> > >
> > > I own an Elgato Cam Link 4K which
On Fri, Nov 20, 2020 at 1:52 PM Benjamin Drung
wrote:
>
> Hi,
>
> I own an Elgato Cam Link 4K which is a very popular USB HDMI capture
> device (number one capture card by click rates on Geizhals [1]). The
> problem is that the video feed is distorted when using the /dev/videoX
> device in the bro
On Sat, Apr 25, 2015 at 11:00 PM, Adam Goode wrote:
> Here's the problem:
>
> [0.126595] ACPI Error: No handler for Region [CMS0]
> (8802658a0438) [SystemCMOS] (20150410/evregion-163)
> [0.126597] ACPI Error: Region SystemCMOS (ID=5) has no handler
>
wo, so
I chose "status" as the LED name.
Signed-off-by: Adam Goode
diff --git a/drivers/platform/x86/thinkpad_acpi.c
b/drivers/platform/x86/thinkpad_acpi.c
index cacb43fb1df7..6577bf8e5635 100644
--- a/drivers/platform/x86/thinkpad_acpi.c
+++ b/drivers/platform/x86/thinkpad_acpi.c
@
On Sun, Feb 12, 2017 at 1:22 PM, Sebastian Reichel wrote:
> Hi,
>
> On Tue, Feb 07, 2017 at 11:01:32PM -0200, Henrique de Moraes Holschuh wrote:
>> Hello Adam,
>>
>> I apologise for the delay on answering you.
>>
>> On Tue, 31 Jan 2017, Adam Goode wrote
change.
Since there are many YUV and non-YUV formats supported by UVC cameras (but
not mentioned in the official specifications), and the quantization is
also not specified for these formats, I am not changing that behavior: all
formats besides MJPEG will stay at V4L2_QUANTIZATION_DEFAULT as before.
Hi,
I sent a v2 patch last night, thanks for all the comments here!
Adam
have values for all the possible UVC color settings,
so it is mapped as closely as possible.
Signed-off-by: Adam Goode
---
Changes in v3:
- Remove quantization changes completely.
drivers/media/usb/uvc/uvc_driver.c | 64 --
drivers/media/usb/uvc/uvc_v4l2.c
gt; >> Thank you for the patch.
> >>
> >> On Sat, Aug 22, 2020 at 09:21:34PM -0400, Adam Goode wrote:
> >>> The Color Matching Descriptor has been present in USB cameras since
> >>> the original version of UVC, but it has never been fully used
>
On Mon, Aug 24, 2020 at 10:38 AM Hans Verkuil wrote:
>
> On 24/08/2020 15:56, Adam Goode wrote:
> > On Mon, Aug 24, 2020 at 4:48 AM Hans Verkuil
> > wrote:
> >>
> >> On 23/08/2020 17:08, Laurent Pinchart wrote:
> >>> Hi Adam,
> >>>
>
On Mon, Aug 31, 2020 at 9:17 PM Laurent Pinchart
wrote:
>
> Hi Adam,
>
> On Mon, Aug 24, 2020 at 01:31:54PM -0400, Adam Goode wrote:
> > On Mon, Aug 24, 2020 at 10:38 AM Hans Verkuil wrote:
> > > On 24/08/2020 15:56, Adam Goode wrote:
> > > > On Mon, Aug
On Thu, Aug 27, 2020 at 11:28 PM Adam Goode wrote:
>
> The Color Matching Descriptor has been present in USB cameras since
> the original version of UVC, but it has never been fully exposed
> in Linux.
>
> This change informs V4L2 of all of the UVC colorspace parameters:
On Thu, Sep 3, 2020 at 11:04 PM Laurent Pinchart
wrote:
>
> Hi Adam,
>
> Thank you for the patch.
>
> On Wed, Sep 02, 2020 at 04:06:17PM -0400, Adam Goode wrote:
> > The Color Matching Descriptor has been present in USB cameras since
> > the original version of UV
probe and read uncorrupted images from this camera.
With this change, both qv4l2 and chromium can now read uncorrupted video
from the Elgato HD60 S+.
Signed-off-by: Adam Goode
---
drivers/media/usb/uvc/uvc_v4l2.c | 26 ++
1 file changed, 26 insertions(+)
diff --git a
rpret MJPEG as FULL range. Web browsers
such as Chrome and Firefox already ignore V4L2's quantization for USB
devices and use the correct LIMITED value, but other programs such
as qv4l2 will incorrectly interpret the output of MJPEG from USB
cameras without this change.
Signed-off-by: Ada
On Fri, Apr 24, 2020 at 1:37 AM Adam Goode wrote:
>
> bFrameIndex and bFormatIndex can be negotiated by the camera during
> probing, resulting in the camera choosing a different format than
> expected. v4l2 can already accommodate such changes, but the code was
> not updating th
29 matches
Mail list logo
