search for: sideband

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 sideband layers found Error ---> Invalid sideband mode encountered (1st sideband): 7 Error...

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 that lightly test sideband message encoding and decoding as w...

...UP requests in MST is completely bogus. drm_dp_mst_handle_up_req() is called from drm_dp_mst_hpd_irq(), which is usually called from the driver's hotplug handler. Because we handle sending the hotplug event from this function, we actually cause the driver's hotplug handler (and in turn, all sideband transactions) to block on drm_device->mode_config.connection_mutex. This makes it impossible to send any sideband messages from the driver's connector probing functions, resulting in the aforementioned sideband message timeout. There's even more problems with this beyond breaking hotplu...

...UP requests in MST is completely bogus. drm_dp_mst_handle_up_req() is called from drm_dp_mst_hpd_irq(), which is usually called from the driver's hotplug handler. Because we handle sending the hotplug event from this function, we actually cause the driver's hotplug handler (and in turn, all sideband transactions) to block on drm_device->mode_config.connection_mutex. This makes it impossible to send any sideband messages from the driver's connector probing functions, resulting in the aforementioned sideband message timeout. There's even more problems with this beyond breaking hotplu...

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 is always the same - I cannot decod any speex files. I've tried Ogg Speex/Wave Speex encoded by jspeex-v0.9.2_R1.12/speexenc/speexACM-v1.0.1.1 at 8/16/22/32/44 kHz I've spen...

...hat contains speex-encoded data. I want to read that file, extract the audio bits, and convert them to a different format. I've written a little java app to do this, but I receive this error when running it: Exception in thread "main" java.io.StreamCorruptedException: More than two sideband layers found I've got a feeling the SpeexDecoder class wants/assumes a certain amount of data when decoding and I'm not meeting that expectation. Is that correct? How much data should I hand to the decoder when I call the processData() method? Thanks! -- Jeff Ramin Software Engineer Si...

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

...ch_device); > } > > -static void drm_dp_port_teardown_pdt(struct drm_dp_mst_port *port, int old_pdt) > -{ > - struct drm_dp_mst_branch *mstb; > - > - switch (old_pdt) { > - case DP_PEER_DEVICE_DP_LEGACY_CONV: > - case DP_PEER_DEVICE_SST_SINK: > - /* remove i2c over sideband */ > - drm_dp_mst_unregister_i2c_bus(&port->aux); > - break; > - case DP_PEER_DEVICE_MST_BRANCHING: > - mstb = port->mstb; > - port->mstb = NULL; > - drm_dp_mst_topology_put_mstb(mstb); > - break; > - } > -} > - > static void drm_dp_destroy_port(...

...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...

...ADSI compatible handset and dial up my bank, OneWorldBankingConglomerate. Would they be able to push me their menu? Button 1 for TeleBanking. Button 2 for New Accounts. Button 3 for Customer Service. Button 4 Check Verification, etc... Is there a protocol that supports this? Could it be passed in sideband somehow? Would normal people actually buy phones to have access to this? What kind of security implications would this have? ----- Andrew Thompson http://aktzero.com/ Your eyes are weary from staring at the CRT. You feel sleepy. Notice how restful it is to watch the cursor blink. Close your eyes....

...I want to read that file, extract the audio bits, and > convert them to a different format. > > I've written a little java app to do this, but I receive this error when > running it: > > Exception in thread "main" java.io.StreamCorruptedException: More than > two sideband layers found > > I've got a feeling the SpeexDecoder class wants/assumes a certain amount > of data when decoding and I'm not meeting that expectation. > > Is that correct? How much data should I hand to the decoder when I call > the processData() method? > > Thanks!...

...mp;mstb->topology_kref, drm_dp_destroy_mst_branch_device); } -static void drm_dp_port_teardown_pdt(struct drm_dp_mst_port *port, int old_pdt) -{ - struct drm_dp_mst_branch *mstb; - - switch (old_pdt) { - case DP_PEER_DEVICE_DP_LEGACY_CONV: - case DP_PEER_DEVICE_SST_SINK: - /* remove i2c over sideband */ - drm_dp_mst_unregister_i2c_bus(&port->aux); - break; - case DP_PEER_DEVICE_MST_BRANCHING: - mstb = port->mstb; - port->mstb = NULL; - drm_dp_mst_topology_put_mstb(mstb); - break; - } -} - static void drm_dp_destroy_port(struct kref *kref) { struct drm_dp_mst_port *port =...

...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 few such as ISB (Independent Sideband AM) are stereo. To simplify the design I followed the API's recommendation to always feed the encoder a 48 kHz stereo stream and let Opus sort it out. This works well, but then I noticed the SET_FORCE_CHANNELS option. Is there any advantage to my detecting identical left and right channels and...

...mp;mstb->topology_kref, drm_dp_destroy_mst_branch_device); } -static void drm_dp_port_teardown_pdt(struct drm_dp_mst_port *port, int old_pdt) -{ - struct drm_dp_mst_branch *mstb; - - switch (old_pdt) { - case DP_PEER_DEVICE_DP_LEGACY_CONV: - case DP_PEER_DEVICE_SST_SINK: - /* remove i2c over sideband */ - drm_dp_mst_unregister_i2c_bus(&port->aux); - break; - case DP_PEER_DEVICE_MST_BRANCHING: - mstb = port->mstb; - port->mstb = NULL; - drm_dp_mst_topology_put_mstb(mstb); - break; - } -} - static void drm_dp_destroy_port(struct kref *kref) { struct drm_dp_mst_port *port =...

...drm_dp_port_teardown_pdt(struct drm_dp_mst_port *port, int > > old_pdt) > > -{ > > - struct drm_dp_mst_branch *mstb; > > - > > - switch (old_pdt) { > > - case DP_PEER_DEVICE_DP_LEGACY_CONV: > > - case DP_PEER_DEVICE_SST_SINK: > > - /* remove i2c over sideband */ > > - drm_dp_mst_unregister_i2c_bus(&port->aux); > > - break; > > - case DP_PEER_DEVICE_MST_BRANCHING: > > - mstb = port->mstb; > > - port->mstb = NULL; > > - drm_dp_mst_topology_put_mstb(mstb); > > - break; > > - } > > -}...

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 reinitializing the display. Cc: Juston Li <juston.li at intel.com> Cc: Imre Deak <imre.deak at intel.com> Cc: Ville Syrj?l? <ville.syrjala at...

...is resumed, or while the device housing said connector is in runtime suspend. As well, the debugging tools that are added in this include: - A limited debugging utility for dumping the list of topology references on an MST port or branch connector whose topology reference count has reached 0 - Sideband down request dumping, along with some basic selftests for testing our encoding/decoding functions Patchseries wide changes since v1 - Add "Combine redundant cases in drm_dp_encode_sideband_req()" to fulfill some of the danvet's review requests Lyude Paul (27): drm/dp_mst:...

...is resumed, or while the device housing said connector is in runtime suspend. As well, the debugging tools that are added in this include: - A limited debugging utility for dumping the list of topology references on an MST port or branch connector whose topology reference count has reached 0 - Sideband down request dumping, along with some basic selftests for testing our encoding/decoding functions Cc: Juston Li <juston.li at intel.com> Cc: Imre Deak <imre.deak at intel.com> Cc: Ville Syrjälä <ville.syrjala at linux.intel.com> Cc: Harry Wentland <hwentlan at amd.com> L...

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: Imre Deak <imre.deak at intel.com> > Cc: Ville Syrjälä <ville.syrjala at l...