search for: sidebands

Hi guys I succesfully got my encoder and decoder working after much hassles, but when I use the same code in another project, I get these following errors: Error ---> Invalid sideband mode encountered (1st sideband): 7 Error ---> Invalid sideband mode encountered (1st sideband): 7 Error ---> Invalid sideband mode encountered (1st sideband): 6 Error ---> More than two

Unfortunately the DP MST helpers do not have much in the way of debugging utilities. So, let's add some! This adds basic debugging output for down sideband requests that we send from the driver, so that we can actually discern what's happening when sideband requests timeout. Since there wasn't really a good way of testing that any of this worked, I ended up writing simple selftests

Once upon a time, hotplugging devices on MST branches actually worked in DRM. Now, it only works in amdgpu (likely because of how it's hotplug handlers are implemented). On both i915 and nouveau, hotplug notifications from MST branches are noticed - but trying to respond to them causes messaging timeouts and causes the whole topology state to go out of sync with reality, usually resulting in

Once upon a time, hotplugging devices on MST branches actually worked in DRM. Now, it only works in amdgpu (likely because of how it's hotplug handlers are implemented). On both i915 and nouveau, hotplug notifications from MST branches are noticed - but trying to respond to them causes messaging timeouts and causes the whole topology state to go out of sync with reality, usually resulting in

This fixes some annoying issues on the P50-P52 with displays not being detected if they aren't plugged in at boot, and sometimes even when they are plugged in at boot. See: https://bugzilla.redhat.com/show_bug.cgi?id=1477182 Lyude Paul (2): drm/nouveau: Only write DP_MSTM_CTRL when needed drm/nouveau: Reset MST branching unit before enabling drivers/gpu/drm/nouveau/dispnv50/disp.c | 65

Hi, I downloaded Ulrich's TestClient and have not been able to connect to the default server. I will try to modify and get to work locally(local echo). I wanted to test my SpeexDecoder as no matter what I try I alwasy get an java.io.StreamCorruptedException: Invalid sideband mode encountered. (2nd sideband): 7 Please note that the Invalid sideband modes differ per file but the end result

FLV contains TC messages? TC message payload contains a format byte and speex frames (up to eight). In the format byte 0xb0 indicates speex. Speex is always 16 kHz, 16 bit, mono. Jozsef Message: 1 Date: Mon, 16 Nov 2009 14:40:20 -0600 From: Jeff Ramin <jeff.ramin at singlewire.com> Subject: [Speex-dev] jspeex question To: speex-dev at xiph.org Message-ID: <4B01B8B4.8020904 at

Hello, I have a crossover PRI(Asterisk server to PBX) and a regular telco PRI T1 line and currently have echocancel=yes and echocancelwhenbridged=yes on those spans in zapata.conf. I was discussing CPU load with another Asterisk user and he mentioned that PRIs don't need echo cancelation and that turning it off will reduced CPU load on the server. I checked many sample configs and the

On Tue, Sep 03, 2019 at 04:45:54PM -0400, Lyude Paul wrote: > Since we're going to be implementing suspend/resume reprobing very soon, > we need to make sure we are extra careful to ensure that our locking > actually protects the topology state where we expect it to. Turns out > this isn't the case with drm_dp_port_setup_pdt() and > drm_dp_port_teardown_pdt(), both of which

...pass them to the playing buffer which sends them to the soundcard when i have enough data to start playing. ---- Now, it works GOOD! Most of the time... but from time to time, out of the blue and totally random, the decoder (and only the decoder) throws an Exception like: "more than two sidebands found" or "invalid sideband mode" and simply stops working, making my app unable to continue working. From my understanding of the Speex library, this means that the decoder doesn't find the bits where it expect them to be... but WHY it happens only from time to time?! I...

I am curious. I understand that features can be pushed to an ADSI phone that make navigating your own voicemail easier, and for other internal things. But, does anyone push this data outside of their own phone network? Example: I am at home with my spiffy new ADSI compatible handset and dial up my bank, OneWorldBankingConglomerate. Would they be able to push me their menu? Button 1 for

The link is http://www.adobe.com/devnet/rtmp/. TC Message stands for TinCan message. It is 11 bytes long, first byte is message type, three bytes of payload length four bytes of timestamp and three bytes of stream ID. The first byte of the payload for audio message is the format byte and the rest of the byte is the payload. Jozsef ----- Original Message ---- From: Jeff Ramin <jeff.ramin

Since we're going to be implementing suspend/resume reprobing very soon, we need to make sure we are extra careful to ensure that our locking actually protects the topology state where we expect it to. Turns out this isn't the case with drm_dp_port_setup_pdt() and drm_dp_port_teardown_pdt(), both of which change port->mstb without grabbing &mgr->lock. Additionally, since most

I'm using Opus for a networked ham radio communications receiver. Kudos on the whole project; it sounds excellent even at low bit rates and the API was surprisingly simple and easy to use. And god knows the world needs a really good, general purpose, non-proprietary codec. One question, though. Depending on the mode my receiver can generate mono or stereo. Most operating modes are mono, but a

Since we're going to be implementing suspend/resume reprobing very soon, we need to make sure we are extra careful to ensure that our locking actually protects the topology state where we expect it to. Turns out this isn't the case with drm_dp_port_setup_pdt() and drm_dp_port_teardown_pdt(), both of which change port->mstb without grabbing &mgr->lock. Additionally, since most

On Wed, 2019-09-25 at 15:27 -0400, Sean Paul wrote: > On Tue, Sep 03, 2019 at 04:45:54PM -0400, Lyude Paul wrote: > > Since we're going to be implementing suspend/resume reprobing very soon, > > we need to make sure we are extra careful to ensure that our locking > > actually protects the topology state where we expect it to. Turns out > > this isn't the case

From: Lyude Paul <lyude at redhat.com> [ Upstream commit ac0de16a38a9ec7026ca96132e3883c564497068 ] Currently, we enable hotplug detection only after we re-enable the display. However, this is too late if we're planning on sending sideband messages during the resume process - which we'll need to do in order to reprobe the topology on resume. So, enable hotplug events before

This is the large series for adding MST suspend/resume reprobing that I've been working on for quite a while now. In addition, I: - Refactored and cleaned up any code I ended up digging through in the process of understanding how some parts of these helpers worked. - Added some debugging tools along the way that I ended up needing to figure out some issues in my own code Note that

This is the large series for adding MST suspend/resume reprobing that I've been working on for quite a while now. In addition, I: - Refactored and cleaned up any code I ended up digging through in the process of understanding how some parts of these helpers worked. - Added some debugging tools along the way that I ended up needing to figure out some issues in my own code Note that

On Tue, Sep 3, 2019 at 4:49 PM Lyude Paul <lyude at redhat.com> wrote: > > Since we're going to be reprobing the entire topology state on resume > now using sideband transactions, we need to ensure that we actually have > short HPD irqs enabled before calling drm_dp_mst_topology_mgr_resume(). > So, do that. > > Cc: Juston Li <juston.li at intel.com> > Cc: