search for: _smallest_

Displaying 3 results from an estimated 3 matches for "_smallest_".

2012 May 29
2
Wilcoxon-Mann-Whitney U value: outcomes from different stat packages
Given this example #start code a<-c(0,70,50,100,70,650,1300,6900,1780,4930,1120,700,190,940, 760,100,300,36270,5610,249680,1760,4040,164890,17230,75140,1870,22380,5890,2430) b<-c(0,0,10,30,50,440,1000,140,70,90,60,60,20,90,180,30,90, 3220,490,20790,290,740,5350,940,3910,0,640,850,260) wilcox.test(a, b, paired=FALSE) #sum of rank for first sample sum.rank.a <-
2020 Mar 06
0
[PATCH 2/3] drm/dp_mst: Don't show connectors as connected before probing available PBN
...e of different hubs and have a much better understanding of how this should work now. So: first off tl;dr available_pbn is absolutely not what we want in basically any scenario, we actually want to use the full_pbn field that we get when sending ENUM_PATH_RESOURCES. Second, full_pbn represents the _smallest_ bandwidth limitation encountered in the path between the root MSTB and each connected sink. Remember that there's technically a DisplayPort link trained between each branch device going down the topology, so that bandwidth limitation basically equates to "what is the lowest trained link ra...
2020 Mar 05
4
[PATCH 2/3] drm/dp_mst: Don't show connectors as connected before probing available PBN
On Thu, Mar 05, 2020 at 01:13:36PM -0500, Lyude Paul wrote: > On Thu, 2020-03-05 at 15:11 +0200, Ville Syrj?l? wrote: > > On Wed, Mar 04, 2020 at 05:36:12PM -0500, Lyude Paul wrote: > > > It's next to impossible for us to do connector probing on topologies > > > without occasionally racing with userspace, since creating a connector > > > itself causes a