Displaying 20 results from an estimated 400 matches similar to: "Only stereo sound with gtx570 over hdmi (regression)"
2015 Feb 17
1
Only stereo sound with gtx570 over hdmi (regression)
Hello Ben,
The working kernel code I based my investigation was a 1.3.17 + gentoo patch (so yes, pretty old)
The new one below, not working is the vanilla 3.19 (from the gentoo repo, should be identical to the latest 3.19 stable)
I've narrowed down the issue to the size of the eld.
The new patch (that indeed uses drm_eld_size) (with this patch, I have a working 3.19 kernel):
I will need to
2015 Feb 16
0
Only stereo sound with gtx570 over hdmi (regression)
On Mon, Feb 16, 2015 at 5:03 AM, Farid BENAMROUCHE <fariouche at yahoo.fr> wrote:
> Hello all,
>
> I'm using gentoo, with kernel 3.17.0-p1-pf and at some point, a patch was included in this branch of the gentoo kernel that broke hdmi audio.
>
> I've checked with the latest 3.19 vanilla kernel, and I still have the same problem. I cannot output multichannel sound over
2014 Mar 19
1
[PATCH v2] disp/nvd0-: allow 540MHz data rate for nvd0+ devices
Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=76319
Signed-off-by: Ilia Mirkin <imirkin at alum.mit.edu>
---
It's unclear to me whether GF11x devices actually support this, but
the disp "split" is at nvd0, so I went with that. The marketing docs
are fairly unclear. However most of them don't actually have DP in the
first place, so it may not be a huge issue.
I
2014 Nov 10
1
[PATCH 2/2] drm/edid: fix Baseline_ELD_Len field in drm_edid_to_eld()
Hi Ben,
The below patch from Jani also touches nouveau, can you please take a
look at it an ack? The core part + nouveau apply on top of drm-next,
the i915 part needs stuff from my next queue. So I'd prefer if we can
get this in through drm-intel-next.
Hi Dave,
Ack on that from your side?
Cheers, Daniel
On Tue, Oct 28, 2014 at 3:20 PM, Jani Nikula <jani.nikula at intel.com> wrote:
2018 Jul 12
1
[PATCH] drm/nouveau: Don't forget to label dp_aux devices
This makes debugging with DP tracing a lot harder to interpret, so name
each i2c based off the name of the encoder that it's for
Signed-off-by: Lyude Paul <lyude at redhat.com>
---
drivers/gpu/drm/nouveau/dispnv04/disp.c | 2 +-
drivers/gpu/drm/nouveau/dispnv50/disp.c | 2 +-
drivers/gpu/drm/nouveau/nouveau_connector.c | 12 ++++++++++--
2017 Jan 11
1
[PATCH] drm/nouveau: Fix HDA ELD handling (thus, HDMI audio) on gt215
Store the ELD correctly, not just enough copies of the first byte
to pad out the given ELD size.
Signed-off-by: Alastair Bridgewater <alastair.bridgewater at gmail.com>
---
drivers/gpu/drm/nouveau/nvkm/engine/disp/hdagt215.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/gpu/drm/nouveau/nvkm/engine/disp/hdagt215.c
2020 Apr 16
1
[PATCH] drm/nouveau: Fix regression by audio component transition
Since the commit 742db30c4ee6 ("drm/nouveau: Add HD-audio component
notifier support"), the nouveau driver notifies and pokes the HD-audio
HPD and ELD via audio component, but this seems broken. The culprit
is the naive assumption that crtc->index corresponds to the HDA pin.
Actually this rather corresponds to the MST dev_id (alias "pipe" in
the audio component framework)
2014 Mar 19
0
[PATCH] disp/nvd0-: allow 540MHz data rate for nvd0+ devices
Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=76319
Signed-off-by: Ilia Mirkin <imirkin at alum.mit.edu>
---
It's unclear to me whether GF11x devices actually support this, but
the disp "split" is at nvd0, so I went with that. The marketing docs
are fairly unclear. However most of them don't actually have DP in the
first place, so it may not be a huge issue.
I
2014 Aug 12
6
[PATCH 0/4] Some initial tidy-ups and refactoring
The patches contain some tidy-up work, and refactoring that has arisen
as a by-product of my initial work on adding TV support to nv50.
Joel Holdsworth (4):
drm/nouveau: Removed unneeded include in nvc0_fence.c
drm/nouveau: Replaced magic numbers with defines from nouveau_reg
drm/nouveau: Replaced copy-pasted nv_wait with nv50_wait_dpms_ctrl
helper
drm/nouveau: Refactored encoder
2017 Jan 17
32
[PATCH 0/6] drm/nouveau: Enable HDMI Stereoscopy
This is an initial implementation of HDMI 3D mode support for the
nouveau kernel driver. It works on all of the hardware that I have
available to test at the moment, but I am unsure as to the overall
approach taken for setting HDMI InfoFrames, there's no support for g84
or gf119 disps, and the criteria for enabling stereo support for an
output seems a bit iffy.
The first four patches arrange
2013 Jul 18
105
[Bug 67051] New: No nouveau HDMI sound on NVIDIA GT430
https://bugs.freedesktop.org/show_bug.cgi?id=67051
Priority: medium
Bug ID: 67051
Assignee: nouveau at lists.freedesktop.org
Summary: No nouveau HDMI sound on NVIDIA GT430
Severity: normal
Classification: Unclassified
OS: Linux (All)
Reporter: alupu01 at gmail.com
Hardware: x86 (IA32)
Status:
2010 Dec 15
9
[Bug 32406] New: nouveau fails to send hotplug event to ALSA hda hdmi audio
https://bugs.freedesktop.org/show_bug.cgi?id=32406
Summary: nouveau fails to send hotplug event to ALSA hda hdmi
audio
Product: xorg
Version: unspecified
Platform: Other
OS/Version: All
Status: NEW
Severity: normal
Priority: medium
Component: Driver/nouveau
AssignedTo: nouveau
2008 Oct 07
2
Transition from Courier-IMAP
Hello all,
Currently we are looking at the possibility of moving from Courier-IMAP
to Dovecot (the one that comes with Debian Lenny: version 1.0.15). I'm
currently testing it on a non-production server and have a few questions:
1) Currently all our clients use Thunderbird as their mail client to
read mail from our IMAP server. Thunderbird is configured with "INBOX."
as the
2010 Jun 01
3
[PATCHv3 0/2] virtio: put last seen used index into ring itself
Changes from v2: added padding between avail idx and flags,
and changed virtio to only publish used index when callbacks
are enabled.
Here's a rewrite of the original patch with a new layout.
I haven't tested it yet so no idea how this performs, but
I think this addresses the cache bounce issue raised by Avi.
Posting for early flames/comments.
Generally, the Host end of the virtio ring
2010 Jun 01
3
[PATCHv3 0/2] virtio: put last seen used index into ring itself
Changes from v2: added padding between avail idx and flags,
and changed virtio to only publish used index when callbacks
are enabled.
Here's a rewrite of the original patch with a new layout.
I haven't tested it yet so no idea how this performs, but
I think this addresses the cache bounce issue raised by Avi.
Posting for early flames/comments.
Generally, the Host end of the virtio ring
2020 Jan 13
0
[PATCH RESEND] drm/nouveau: Add HD-audio component notifier support
This patch adds the support for the notification of HD-audio hotplug
via the already existing drm_audio_component framework. This allows
us more reliable hotplug notification and ELD transfer without
accessing HD-audio bus; it's more efficient, and more importantly, it
works without waking up the runtime PM.
The implementation is rather simplistic: nouveau driver provides the
get_eld ops for
2020 Nov 14
0
[PATCH 8/8] drm/nouveau/kms/nv50-: Fix locking for audio callbacks
Noticed that I wasn't paying close enough attention the last time I looked
at our audio callbacks, as I completely missed the fact that we were
figuring out which audio-enabled connector goes to each encoder by checking
it's state, but without grabbing any of the appropriate modesetting locks
to do so.
That being said however: trying to grab modesetting locks in our audio
callbacks would
2010 May 26
6
[PATCHv2-RFC 0/2] virtio: put last seen used index into ring itself
Here's a rewrite of the original patch with a new layout.
I haven't tested it yet so no idea how this performs, but
I think this addresses the cache bounce issue raised by Avi.
Posting for early flames/comments.
Generally, the Host end of the virtio ring doesn't need to see where
Guest is up to in consuming the ring. However, to completely understand
what's going on from the
2010 May 26
6
[PATCHv2-RFC 0/2] virtio: put last seen used index into ring itself
Here's a rewrite of the original patch with a new layout.
I haven't tested it yet so no idea how this performs, but
I think this addresses the cache bounce issue raised by Avi.
Posting for early flames/comments.
Generally, the Host end of the virtio ring doesn't need to see where
Guest is up to in consuming the ring. However, to completely understand
what's going on from the
2018 Dec 13
3
[Bug 1308] New: iptables -i + is broken in v1.8.0
https://bugzilla.netfilter.org/show_bug.cgi?id=1308
Bug ID: 1308
Summary: iptables -i + is broken in v1.8.0
Product: iptables
Version: unspecified
Hardware: x86_64
OS: RedHat Linux
Status: NEW
Severity: normal
Priority: P5
Component: iptables
Assignee: netfilter-buglog at