A while back, Laurent raised some comments about the component helper,
which this patch set starts to address.
The first point it addresses is the repeated parsing inefficiency when
deferred probing occurs. When DT is used, the structure of the
component helper today means that masters end up parsing the device
tree for each attempt to re-bind the driver.
We remove this inefficiency by creating an array of matching data and
functions, which the component helper can use …
[View More]internally to match up
components to their master.
The second point was the inefficiency of destroying the list of
components each time we saw a failure. We did this to ensure that
we kept things correctly ordered: component bind order matters.
As we have an array instead, the array is already ordered, so we
use this array to store the component pointers instead of a list,
and remember which are duplicates (and thus should be avoided.)
Avoiding the right duplicates matters as we walk the array in the
opposite direction at tear down.
drivers/base/component.c | 249 ++++++++++++++++++++++-----------
drivers/gpu/drm/msm/msm_drv.c | 83 +++++------
drivers/staging/imx-drm/imx-drm-core.c | 57 +-------
include/linux/component.h | 8 +-
4 files changed, 208 insertions(+), 189 deletions(-)
--
FTTC broadband for 0.8mile line: now at 9.7Mbps down 460kbps up... slowly
improving, and getting towards what was expected from it.
[View Less]
https://bugs.freedesktop.org/show_bug.cgi?id=65963
Damian Nowak <nowaker(a)geozone.pl> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|REOPENED |RESOLVED
Resolution|--- |DUPLICATE
--- Comment #27 from Damian Nowak <nowaker(a)geozone.pl> ---
Although this issue is older than #81644, the latter contains way more
…
[View More]information. Closing this one.
*** This bug has been marked as a duplicate of bug 81644 ***
--
You are receiving this mail because:
You are the assignee for the bug.
[View Less]
https://bugs.freedesktop.org/show_bug.cgi?id=65963
--- Comment #26 from Aaron B <aaronbottegal(a)gmail.com> ---
This should be a duplicate of my bug here:
https://bugs.freedesktop.org/show_bug.cgi?id=81644
SHort story: THe blank screen crash (and rare recover) usually happens for me
is triggered by Chromium, VLC, and OpenGL games opened when Chromium or VLC are
opened. Also rarely on game start ups in general it seems. I believe it's a bug
in Mesa, no clue where, but the apps that …
[View More]trigger it all should be pushing data
to the GPU, so I'd imagine it's a fault in that pipe/allocation.
--
You are receiving this mail because:
You are the assignee for the bug.
[View Less]
https://bugs.freedesktop.org/show_bug.cgi?id=83234
Priority: medium
Bug ID: 83234
Assignee: dri-devel(a)lists.freedesktop.org
Summary: Opening Steam crashes X session
Severity: normal
Classification: Unclassified
OS: Linux (All)
Reporter: gutigen(a)outlook.com
Hardware: x86-64 (AMD64)
Status: NEW
Version: git
Component: Drivers/Gallium/radeonsi
Product: Mesa
…
[View More]Created attachment 105418
--> https://bugs.freedesktop.org/attachment.cgi?id=105418&action=edit
dmesg
Instantly after opening Steam X crashes. OpenGL apps work fine, tested with
Unigine Heaven (64 bit) and Xonotic (32 and 64bit).
--
You are receiving this mail because:
You are the assignee for the bug.
[View Less]