Hi
On Sat, Nov 30, 2013 at 2:52 PM, Bruno Pr?mont
wrote:
> With commit b4aa0163056b6c70029b6e8619ce07c274351f42 Matthew Garret
> introduced a efifb vga_default_device() so that EFI systems that do not
> load shadow VBIOS or setup VGA get proper value for boot_vga PCI sysfs
> attribute on the corr
Hi
On Wed, Dec 18, 2013 at 4:38 PM, David Herrmann
wrote:
> Hi
>
> On Sat, Nov 30, 2013 at 2:52 PM, Bruno Pr?mont
> wrote:
>> With commit b4aa0163056b6c70029b6e8619ce07c274351f42 Matthew Garret
>> introduced a efifb vga_default_device() so that EFI systems that do not
Hi
On Tue, Jan 9, 2018 at 11:16 AM, Daniel Vetter wrote:
> On Wed, Jan 03, 2018 at 11:21:05PM +0100, Noralf Trønnes wrote:
>> Export the following functions so in-kernel users can allocate
>> dumb buffers:
>> - drm_file_alloc
>> - drm_file_free
>> - drm_prime_handle_to_fd_ioctl
>> - drm_mode_addf
Hi
On Tue, Jan 9, 2018 at 11:20 AM, Daniel Vetter wrote:
> On Wed, Jan 03, 2018 at 11:21:03PM +0100, Noralf Trønnes wrote:
>> From: David Herrmann
>>
>> Rather than doing drm_file allocation/destruction right in the fops, lets
>> provide separate helpers. This decoupl
Hey
On Fri, Mar 11, 2016 at 12:52 PM, Lionel Landwerlin
wrote:
> Thanks a lot for pointing this out. I saw you previous comment but didn't
> realize the issue.
> I'll set the pointer to NULL.
>
> I don't if there is an agreement on this, but do you think the unref/free
> functions should check fo
Hi
On Mon, Mar 21, 2016 at 8:51 AM, Daniel Vetter
wrote:
> Just a bit of wording polish plus mentioning that it can fail and must
> be restarted.
>
> Requested by Sumit.
>
> v2: Fix them typos (Hans).
>
> Cc: Chris Wilson
> Cc: Tiago Vignatti
> Cc: Stéphane M
Hi
On Wed, Mar 23, 2016 at 9:42 AM, Alexey Brodkin
wrote:
> As a pair to already existing drm_connector_unregister_all() we're adding
> generic implementation of what is already done in some drivers.
>
> Once this helper is implemented we'll be ready to switch existing
> driver-specific implement
Hey
On Mon, Mar 21, 2016 at 6:14 PM, Daniel Vetter wrote:
> On Mon, Mar 21, 2016 at 01:26:58PM +0100, David Herrmann wrote:
>> Hi
>>
>> On Mon, Mar 21, 2016 at 8:51 AM, Daniel Vetter
>> wrote:
>> > Just a bit of wording polish plus mentioning that it
Hi
On Wed, Mar 23, 2016 at 12:56 PM, Chris Wilson
wrote:
> On Wed, Mar 23, 2016 at 12:30:42PM +0100, David Herrmann wrote:
>> My question was rather about why we do this? Semantics for EINTR are
>> well defined, and with SA_RESTART (default on linux) user-space can
>&g
Hey
On Wed, Mar 16, 2016 at 2:34 PM, Noralf Trønnes wrote:
> tinydrm provides a very simplified view of DRM for displays that has
> onboard video memory and is connected through a slow bus like SPI/I2C.
>
> Signed-off-by: Noralf Trønnes
> ---
> drivers/gpu/drm/Kconfig
Hi
On Mon, Mar 28, 2016 at 9:42 PM, Tiago Vignatti
wrote:
> Do we have an agreement here after all? David? I need to know whether this
> fixup is okay to go cause I'll need to submit to Chrome OS then.
Sure it is fine. The code is already there, we cannot change it.
Thanks
David
ting
> driver-specific implementations with the generic one.
>
> Signed-off-by: Alexey Brodkin
> Cc: Daniel Vetter
> Cc: David Airlie
> Cc: David Herrmann
> ---
>
> Changes v3 -> v4:
> * In drm_connector_register_all() fail path which calls unregister_all()
>
gic fails if no DRM-Master is currently active at all. Because
then the client itself would become DRM-Master (if it is root) and this
makes this whole thing useles.
Also note that the second "if-condition":
file_priv->minor->master != file_priv->master
is always true and ca
Hi Laurent
On Thu, Oct 11, 2012 at 12:35 PM, Laurent Pinchart
wrote:
> Hi David,
>
> Would you have time to document the master_set operation in
> Documentation/DocBook/drm.tmpl ? :-)
I have actually some drafts for "drmSetMaster/drmDropMaster" man-pages
for libdrm on my machine. However, I am s
console), then the background display-server is unable to
destroy its buffers.
Under special curcumstances (like monitor reconfiguration) this might even
happen during runtime.
Signed-off-by: David Herrmann
---
drivers/gpu/drm/drm_drv.c | 12 ++--
1 file changed, 6 insertions(+), 6 deletions
gic fails if no DRM-Master is currently active at all. Because
then the client itself would become DRM-Master (if it is root) and this
makes this whole thing useles.
Also note that the second "if-condition":
file_priv->minor->master != file_priv->master
is always true and ca
Hi Michael
On Sat, Dec 1, 2012 at 3:54 AM, Michael Hasselmann
wrote:
> On Fri, 2012-09-28 at 23:51 +0200, Luc Verhaegen wrote:
>> We still have, i hope (depends on what the FOSDEM organizers have left
>> for us), 6 slots fully open: first come first serve, and the earlier
>> bird gets the nicer s
Hi Jesse
On Thu, Jan 10, 2013 at 1:22 AM, Jesse Barnes wrote:
> On Fri, 28 Sep 2012 23:44:18 +0200
> David Herrmann wrote:
>
>> Hi
>>
>> This is revision 2 of the manpages for libdrm. I converted everything to
>> docbook
>> XML. This makes it easier to w
Hi Maarten
On Wed, Jan 16, 2013 at 3:16 PM, Maarten Lankhorst
wrote:
> Op 16-01-13 13:19, Maarten Lankhorst schreef:
>> ...
>> Jesse Barnes (1):
>> man: disable man page building until David saves us all
>>
> Looks like this commit might break building if you don't build against git
> dire
expensive xsltproc procedure can be
skipped.
Signed-off-by: David Herrmann
---
Hi
This is how I build manpages for kmscon and it worked until now so it should
also work for libdrm. I tried every kind of failure and out-of-tree builds and
everything worked. distcheck also passed fine.
I hope that
Hi Colin
On Thu, Jan 10, 2013 at 1:46 AM, Colin Walters wrote:
> It's not enough to check for xsltproc - the system may not have the
> docbook stylesheets installed. This patch also allows builders to
> override the generation/installation of manpages entirely; for
> example, manpages are of no
Hi Thierry
On Fri, Jan 18, 2013 at 1:22 PM, Thierry Reding
wrote:
> Due to the typo, none of the .xml files would end up in the release
> tarball and cause make distcheck as well as builds from the tarball to
> fail.
>
> Using $() isn't strictly necessary but other variables and expressions
> use
On Fri, Jan 18, 2013 at 5:00 PM, David Herrmann
wrote:
> Hi Thierry
>
> On Fri, Jan 18, 2013 at 1:22 PM, Thierry Reding
> wrote:
>> Due to the typo, none of the .xml files would end up in the release
>> tarball and cause make distcheck as well as builds from the tarball
Hi Mark
On Sun, Jan 20, 2013 at 7:39 AM, Mark Zhang wrote:
> Hi David:
>
> Sorry for jumping in. I pulled the ToT libdrm and it seems the manpages
> will not be built("make html" does nothing), any suggestions?
The manpages should be built automatically if you do "make". Or you
can try "make -C
Hi Jesse
On Fri, Jan 18, 2013 at 5:54 PM, Jesse Barnes wrote:
> On Fri, 18 Jan 2013 17:01:59 +0100
> David Herrmann wrote:
>
>> On Fri, Jan 18, 2013 at 5:00 PM, David Herrmann
>> wrote:
>> > Hi Thierry
>> >
>> > On Fri, Jan 18, 2013 at 1:22 PM, T
o the target format while blitting.
Fast-paths for xrgb32/etc. could be implemented if we want to improve
blitting performance.
Signed-off-by: David Herrmann
---
Hi
This driver is a very basic DRM driver with roughly the same functionality as
vesafb but with a userspace API that doesn't s
console), then the background display-server is unable to
destroy its buffers.
Under special curcumstances (like monitor reconfiguration) this might even
happen during runtime.
Signed-off-by: David Herrmann
---
drivers/gpu/drm/drm_drv.c | 12 ++--
1 file changed, 6 insertions(+), 6 deletions
Hi Jesse
On Mon, Sep 17, 2012 at 5:12 PM, Jesse Barnes wrote:
> I just pushed some basic man page stuff to the libdrm repo, but won't
> have time to do any more pages for the next week or two.
>
> But regardless, it would be cool if people could adopt some pages and
> push them out. The goal is
really ugly to read.
Regards
David
Some parts are copied from (I hope nobody minds?):
http://lwn.net/Articles/283798/
http://lwn.net/Articles/499261/
David Herrmann (4):
man: use automake man_MANS to allow multiple suffixes
man: add man/drm.7 overview page
man: add KMS overview pa
-page headers.
Signed-off-by: David Herrmann
---
man/Makefile.am | 16 +++-
man/drmAvailable.3 | 26 +
man/drmAvailable.man| 25 -
man/drmHandleEvent.3| 48
man/drmHandleEvent.man | 45
.
Signed-off-by: David Herrmann
---
man/Makefile.am | 1 +
man/drm.7 | 99 +
2 files changed, 100 insertions(+)
create mode 100644 man/drm.7
diff --git a/man/Makefile.am b/man/Makefile.am
index f003101..6193a95 100644
--- a/man
,
framebuffers, planes and cursors.
Signed-off-by: David Herrmann
---
man/Makefile.am | 1 +
man/drm-kms.7 | 269
2 files changed, 270 insertions(+)
create mode 100644 man/drm-kms.7
diff --git a/man/Makefile.am b/man/Makefile.am
index 6193a95
driver-dependent information is needed.
Signed-off-by: David Herrmann
---
man/Makefile.am | 4 +
man/drm-gem.7| 1 +
man/drm-memory.7 | 412 +++
man/drm-mm.7 | 1 +
man/drm-ttm.7| 1 +
5 files changed, 419 insertions(+)
create
Hi Michel
On Mon, Sep 24, 2012 at 9:45 AM, Michel Dänzer wrote:
> On Son, 2012-09-23 at 16:40 +0200, David Herrmann wrote:
>> +
>> +.SS TTM
>> +.B TTM
>> +stands for
>> +.B Translation Table Manager
>> +and is another generic memory-manager provided by the
Hi Thierry
On Mon, Sep 24, 2012 at 9:51 PM, Thierry Reding
wrote:
> On Sun, Sep 23, 2012 at 04:40:03PM +0200, David Herrmann wrote:
>> Hi
>>
>> This tries to continue the effort to document libdrm. I actually removed the
>> X11-like man-page generation code as autotool
.
Thanks for reviewing!
Regards
David
David Herrmann (4):
man: convert manpages to XML instead of plain troff
man: add drm.7 overview page
man: add drm-kms overview page
man: add drm-memory overview page
.gitignore | 4 +
configure.ac| 24 +--
man
If we want to use the manpages in external documentation other than normal
manpages, we should rather use XML. Furthermore, almost no-one knows troff
today, anyway, and XML allows others to easily add more pages without
having to learn troff.
Signed-off-by: David Herrmann
---
.gitignore
The drm.xml file compiles to drm.7 and is meant as a global overview page
for libdrm. It is targeted to new users of libdrm and redirects to all
other main man-pages.
Signed-off-by: David Herrmann
Reviewed-by: Jesse Barnes
---
man/Makefile.am | 1 +
man/drm.xml | 137
This is an overview page for KMS. It is again targeted at novice users
that need redirection to the correct function man-pages.
Signed-off-by: David Herrmann
Reviewed-by: Jesse Barnes
---
man/Makefile.am | 1 +
man/drm-kms.xml | 342
2
This adds an overview page that describes Dumb-Buffers, TTM and GEM. It
does not describe chipset-specific features. You should do that in the
driver-manpages.
Signed-off-by: David Herrmann
Reviewed-by: Jesse Barnes
---
man/Makefile.am| 9 +-
man/drm-memory.xml | 430
gic fails if no DRM-Master is currently active at all. Because
then the client itself would become DRM-Master (if it is root) and this
makes this whole thing useles.
Also note that the second "if-condition":
file_priv->minor->master != file_priv->master
is always true and ca
Hi Laurent
On Thu, Oct 11, 2012 at 12:35 PM, Laurent Pinchart
wrote:
> Hi David,
>
> Would you have time to document the master_set operation in
> Documentation/DocBook/drm.tmpl ? :-)
I have actually some drafts for "drmSetMaster/drmDropMaster" man-pages
for libdrm on my machine. However, I am s
Hi
I thought it's better to ask this question here again as it is easier
to comment via mail.
I tried writing a simple kms modesetting program. I have written it similar to:
http://virtuousgeek.org/blog/index.php/jbarnes?blog=2&title=writing_stanalone_programs_with_egl_and_
and wayland compositor
On Mon, Nov 14, 2011 at 9:38 PM, Jesse Barnes wrote:
> On Mon, 14 Nov 2011 21:25:56 +0100
> David Herrmann wrote:
>
>> Hi
>>
>> I thought it's better to ask this question here again as it is easier
>> to comment via mail.
>>
>> I tried writing a
2011/11/15 Kristian Høgsberg :
> On Mon, Nov 14, 2011 at 5:54 PM, Jesse Barnes
> wrote:
>> On Mon, 14 Nov 2011 21:47:09 +0100
>> David Herrmann wrote:
>>> > I had to modify the resolution the test was searching for
>>> > to 1920x1200 instead o
2011/11/15 Kristian Høgsberg :
> 2011/11/15 David Herrmann :
>> 2011/11/15 Kristian Høgsberg :
>>> On Mon, Nov 14, 2011 at 5:54 PM, Jesse Barnes
>>> wrote:
>>>> On Mon, 14 Nov 2011 21:47:09 +0100
>>>> David Herrmann wrote:
>>>&g
On Fri, Nov 18, 2011 at 10:41 PM, Jesse Barnes wrote:
> On Fri, 18 Nov 2011 22:35:13 +0100
> David Herrmann wrote:
>
>> 2011/11/15 Kristian Høgsberg :
>> > 2011/11/15 David Herrmann :
>> >> 2011/11/15 Kristian Høgsberg :
>> >>> On Mon, N
xf86drmMode.h is missing a header protection. xf86drm.h has one so just copy it
and adjust the name.
Signed-off-by: David Herrmann
---
I am not sure if this is the correct mailing-list for libdrm nor who the actual
maintainer is. Please correct me if I should CC someone else or post it to
Hi
I was tracing down a bug that made drmModePageFlip() fail and I noticed that the
DPMS settings are not correctly restored when switching between xorg-server and
vtcon. In fact, when enabling a monitor with xrandr in X while
DPMS=off for that monitor,
then it will stay blank. Switching back to V
Hi
Motivated by Jesse's letter to the lazyweb [1] I worked on a kmscon
program. It provides a
terminal-emulator similar to the in-kernel terminal-emulator based on
DRM. It is written
from scratch and needs as external dependencies only mesa (libdrm,
libgbm, libEGL, libGLESv2),
udev, xproto (build-
Hi
On Tue, Mar 27, 2012 at 5:59 PM, Ville Syrjälä
wrote:
> On Tue, Mar 27, 2012 at 04:57:29PM +0200, David Herrmann wrote:
>> It needs some more work in the VTE layer and on the UI but it's
>> I had several issues while writing it but most of them are fixed. One
>
Hi
On Wed, Mar 28, 2012 at 8:14 PM, Ville Syrjälä
wrote:
> On Wed, Mar 28, 2012 at 10:30:20AM -0700, Jesse Barnes wrote:
>> On Tue, 27 Mar 2012 16:57:29 +0200
>> David Herrmann wrote:
>>
>> > Hi
>> >
>> > Motivated by Jesse's letter to
Hi
On Wed, Mar 28, 2012 at 7:30 PM, Jesse Barnes wrote:
> On Tue, 27 Mar 2012 16:57:29 +0200
> David Herrmann wrote:
>
>> Hi
>>
>> Motivated by Jesse's letter to the lazyweb [1] I worked on a kmscon
>> program. It provides a
>> terminal-emulator simi
We use errno and EINVAL so include errno.h.
Signed-off-by: David Herrmann
---
src/gallium/state_trackers/egl/fbdev/native_fbdev.c |1 +
1 file changed, 1 insertion(+)
diff --git a/src/gallium/state_trackers/egl/fbdev/native_fbdev.c
b/src/gallium/state_trackers/egl/fbdev/native_fbdev.c
27;ed mesa-dev and the people who reviewed the original patch this
time as I have no idea who I need to send this to.
Thanks
David
**
egl-fbdev: Fix compile-error by including errno.h
We use errno and EINVAL so include errno.h.
Signed-off-by: Davi
We use errno and EINVAL so include errno.h.
This patch introduced this bug:
http://cgit.freedesktop.org/mesa/mesa/commit/src/gallium/state_trackers/egl/fbdev/native_fbdev.c?id=b60120608f6ddf4098bc324363197c979ee04cb7
Signed-off-by: David Herrmann
Cc: Chia-I Wu
Cc: Dave Airlie
Cc: Adam Jackson
Hi
The recently added gbm gallium target
(./src/gallium/targets/gbm/gbm.c) requires HAVE_DRM_PIPE_LOADER for
pipe_loader_drm_probe(). Otherwise, the compiler fails with an
unresolved function-name.
However, HAVE_DRM_PIPE_LOADER is not defined when compiling i915 only,
so I need to compile gallium
user-space.
We can avoid this by waiting for events until we got at least one event or
an error occurred.
Signed-off-by: David Herrmann
---
The patch might look a bit scary but it adds only a single do { } while(!total);
around the whole block.
drivers/gpu/drm/drm_fops.c |
user-space.
We can avoid this by waiting for events until we got at least one event or
an error occurred.
Signed-off-by: David Herrmann
---
The patch might look a bit scary but it adds only a single do { } while(!total);
around the whole block.
drivers/gpu/drm/drm_fops.c |
Hi
I am currently working on fblog [1] (a replacement for fbcon without
VT dependencies) but this questions does also apply to other fbdev
users. Is there a way to share framebuffers between fbdev devices? I
was thinking especially of USB devices like DisplayLink. If they share
the same screen dim
Hi Laurent and Alan
On Tue, Jul 17, 2012 at 1:24 PM, Alan Cox wrote:
>> The main issue is that fbdev has been designed with the implicit assumption
>> that an fbdev driver will always own the graphics memory it uses. All
>> components in the stack, from drivers to applications, have been designed
to see the system-framebuffer platform-devices being registered
during architecture initialization. I haven't worked much there so any comments
are welcome. Otherwise, I will keep the HACK to add the devices during sysfb
module-init.
Regards
David
David Herrmann (9):
video: introduce syste
From: David Herrmann
For a long time now we have the problem that there are multiple drivers
available that try to use system framebuffers (like EFI, VESA/VBE, ...).
There is no way to control which driver gets access to the devices, but
instead works on a first-come-first-serve basis
From: David Herrmann
This adds the VESA BIOS Extension (VBE) device type. Platform code needs
to provide the "vbefb" platform-device with a screen_info structure as
platform code.
All drivers that depend on VBE can now register as bus drivers and bind
to SYSFB_VBE devices. T
From: David Herrmann
HACK: This should be provided by architecture setup code. But to show how it is
supposed to work, we now simply add a "vbefb" device during initialization.
The better way to do this is by moving this into arch-code. So for instance the
x86 boot initialization sho
From: David Herrmann
Fix the vesafb module to no longer use any static __init data. Also add a
module_exit() function that destroys the platform device.
Note that fbdev hotplugging is broken and the self-reference actually
prevents sane module-unloading. Anyway, this at least allows delayed
because the sysfb bus provides all devices now.
Signed-off-by: David Herrmann
---
drivers/video/Kconfig | 1 +
drivers/video/vesafb.c | 49 +++--
2 files changed, 16 insertions(+), 34 deletions(-)
diff --git a/drivers/video/Kconfig b/drivers/video/Kconfig
This provides a new DRM bus helper for the system framebuffer bus. It is
very similar in its functionality to the DRM_USB helper. It allows to
write DRM drivers that register as SYSFB drivers to the system.
Signed-off-by: David Herrmann
---
drivers/gpu/drm/Kconfig | 5 ++
drivers/gpu/drm
into the framebuffer.
All buffer objects are backed by shmem so we can later add PRIME support.
Signed-off-by: David Herrmann
---
drivers/gpu/drm/Kconfig | 2 +
drivers/gpu/drm/Makefile | 1 +
drivers/gpu/drm/dvbe/Kconfig | 28 +++
drivers/gpu/drm/dvbe/Makefile| 4
pixel from the user's
buffer format into the target format while blitting.
Fast-paths for xrgb32/etc. could be implemented if we want to improve
blitting performance.
Signed-off-by: David Herrmann
---
drivers/gpu/drm/dvbe/Kconfig | 1 +
drivers/gpu/drm/dvbe/Makefile| 2 +-
dr
.
Signed-off-by: David Herrmann
---
drivers/gpu/drm/dvbe/Kconfig | 18 +++
drivers/gpu/drm/dvbe/Makefile | 1 +
drivers/gpu/drm/dvbe/dvbe.h | 23
drivers/gpu/drm/dvbe/dvbe_fbdev.c | 235 ++
drivers/gpu/drm/dvbe/dvbe_main.c | 2 +
5 files
Hi Dave
On Sun, Feb 17, 2013 at 11:02 PM, Dave Airlie wrote:
>>
>> This series tries to fix the mess with global system framebuffer access in
>> device drivers. Currently, architecture initialization sets the "screen_info"
>> object according to the system framebuffer that was detected during boo
Hi Dave
Sorry, I was busy reworking the HIDP layer. I finally got time to
continue my work on this again. See below:
On Mon, Feb 18, 2013 at 12:47 AM, Dave Airlie wrote:
[..snap..]
> As I said maybe I'm concentrating on the problem you aren't trying to fix,
> but then I'm not sure I've enough in
Hi
On Wed, Apr 17, 2013 at 11:05 PM, Byron Stanoszek wrote:
> David,
>
> I'm developing a small application that uses libdrm (DRM ioctls) to change
> the
> resolution of a single graphics display and show a framebuffer. I've run
> into
> two problems with this implementation that I'm hoping you c
Hi
On Mon, May 27, 2013 at 5:42 PM, Christopher Harvey wrote:
> I'm looking for the mechanism in the kernel that makes the decision to
> load the efifb driver over a dri one. Any tips? I've got a machine here
> that loads efifb and prevents dri drivers from loading.
If you want to use efifb over
Hi
On Sun, Jun 16, 2013 at 4:57 PM, Daniel Vetter wrote:
> Hi all,
>
> So I've taken a look again at the locking mess in our fbdev support and cried.
> Fixing up the console_lock mess around the fbdev notifier will be real work,
> semanatically the fbdev layer does lots of stupid things (like the
Hi
On Mon, Jun 17, 2013 at 10:47 PM, Andy Lutomirski wrote:
> On 06/16/2013 07:57 AM, Daniel Vetter wrote:
>> Hi all,
>>
>> So I've taken a look again at the locking mess in our fbdev support and
>> cried.
>> Fixing up the console_lock mess around the fbdev notifier will be real work,
>> semanat
uffer.
Cheers
David
David Herrmann (6):
fbdev: simplefb: add init through platform_data
x86: provide platform-devices for boot-framebuffers
drm: add SimpleDRM driver
drm: simpledrm: add fbdev fallback support
drm: add helpers to kick out firmware drivers
drm: nouveau: kick out fir
it is not needed. The headers
provide proper dummies for the case OF is disabled.
Furthermore, we move the FORMAT-definitions to the common platform header
so initialization code can use it to transform "struct screen_info" to
the right format-name.
Signed-off-by: David Herrmann
--
ibility (if
strange formats are used), we still allow vesafb/efifb to be loaded
simultaneously and pick up all remaining devices.
Signed-off-by: David Herrmann
---
arch/x86/Kconfig | 18 ++
arch/x86/kernel/Makefile | 1 +
arch/x86/kernel/sysfb.c | 157
. The buffer is
directly mapped into user-space, so we have only resources for a single
buffer. Otherwise, shadow buffers plus damage-request would be needed.
Signed-off-by: David Herrmann
---
MAINTAINERS| 8 +
drivers/gpu/drm/Kconfig| 2
make the VT layer
happy. This needs to be fixed soon! Otherwise, we need a "depends !VT"
line for SimpleDRM.
Signed-off-by: David Herrmann
---
drivers/gpu/drm/simpledrm/Kconfig | 11 ++
drivers/gpu/drm/simpledrm/Makefile | 4 +
drivers/gpu/drm/simpledrm/s
kick out firmware DRM drivers. Additionally, unlike the
fbdev equivalent, DRM firmware drivers can now query the system whether a
real hardware driver is already loaded and prevent loading themselves.
Signed-off-by: David Herrmann
---
drivers/gpu/drm/drm_pci.c | 1 +
drivers
Use the new DRM infrastructure to kick out firmware drivers before probing
the real driver.
Signed-off-by: David Herrmann
---
drivers/gpu/drm/nouveau/nouveau_drm.c | 29 ++---
1 file changed, 22 insertions(+), 7 deletions(-)
diff --git a/drivers/gpu/drm/nouveau
Hi
On Tue, Jun 25, 2013 at 3:05 AM, Andy Lutomirski wrote:
> On 06/24/2013 03:27 PM, David Herrmann wrote:
>> + sdrm->fb_map = ioremap(sdrm->fb_base, sdrm->fb_size);
>
> This should probably be ioremap_wc. Otherwise it will be *really* slow
> if used in l
Hi
On Wed, Jun 26, 2013 at 10:58 PM, Stephen Warren wrote:
> On 06/24/2013 04:27 PM, David Herrmann wrote:
>> The SimpleDRM driver binds to simple-framebuffer devices and provides a
>> DRM/KMS API. It provides only a single CRTC+encoder+connector combination
>>
Hi
On Wed, Jun 26, 2013 at 10:39 PM, Stephen Warren wrote:
> On 06/24/2013 04:27 PM, David Herrmann wrote:
>> If we create proper platform-devices in x86 boot-code, we can use simplefb
>> for VBE or EFI framebuffers, too. However, there is normally no OF support
>&
Hi
On Wed, Jun 26, 2013 at 10:49 PM, Stephen Warren wrote:
> On 06/24/2013 04:27 PM, David Herrmann wrote:
>> The current situation regarding boot-framebuffers (VGA, VESA/VBE, EFI) on
>> x86 causes troubles when loading multiple fbdev drivers. The global
>> "struct scr
Hi
On Wed, Jun 26, 2013 at 10:59 PM, Stephen Warren wrote:
> On 06/24/2013 04:27 PM, David Herrmann wrote:
>> Create a simple fbdev device during SimpleDRM setup so legacy user-space
>> and fbcon can use it.
>>
>> fbdev deletion is quite buggy. A unregister_framebuf
Hi
On Wed, Jun 26, 2013 at 11:30 PM, Stephen Warren wrote:
> On 06/24/2013 04:27 PM, David Herrmann wrote:
>> Hi
>>
>> This is my second revision of the dvbe driver. I renamed it to SimpleDRM to
>> show the resemblence with the recently introduced simplefb.c fbdev d
ts see how that works out.
Comments welcome!
Cheers
David
[1]: http://cgit.freedesktop.org/~airlied/linux/log/?h=drm-vma-manager
David Herrmann (6):
drm: make drm_mm_init() return void
drm: mm: add drm_mm_node_linked() helper
drm: add unified vma offset manager
drm: gem: convert to new uni
There is no reason to return "int" as this function never fails.
Furthermore, several drivers (ast, sis) already depend on this.
Signed-off-by: David Herrmann
---
drivers/gpu/drm/drm_gem.c| 8 ++--
drivers/gpu/drm/drm_mm.c | 4 +---
drivers/gpu/drm/tt
after
removing it. Furthermore, no-one is supposed to access node->mm from
outside drm_mm.c, anyway.
Signed-off-by: David Herrmann
---
drivers/gpu/drm/drm_mm.c | 1 +
include/drm/drm_mm.h | 5 +
2 files changed, 6 insertions(+)
diff --git a/drivers/gpu/drm/drm_mm.c b/drivers/gpu/drm
2012-proposal by David Airlie
Signed-off-by: David Herrmann
---
drivers/gpu/drm/Makefile | 2 +-
drivers/gpu/drm/drm_vma_manager.c | 224 ++
include/drm/drm_vma_manager.h | 107 ++
3 files changed, 332 insertions(+), 1 del
e during
lookup. However, this lock is not needed during vm-setup as we still
hold a reference there.
This also drops the addr_space_offset member as it is a copy of vm_start
in vma_node objects. Use the accessor functions instead.
Signed-off-by: David Herrmann
---
drivers/gpu/drm/ast/as
which strictly wouldn't be
needed for gem.
Signed-off-by: David Herrmann
---
drivers/gpu/drm/drm_gem.c | 89 +-
drivers/gpu/drm/drm_gem_cma_helper.c | 9 +--
drivers/gpu/drm/exynos/exynos_drm_gem.c| 7 ++-
drivers/gpu/drm/g
Instead of unmapping the nodes in TTM and GEM users manually, we provide
a generic wrapper which does the correct thing for all vma-nodes.
Signed-off-by: David Herrmann
---
drivers/gpu/drm/i915/i915_gem.c | 6 +-
drivers/gpu/drm/ttm/ttm_bo.c| 8 +---
include/drm/drm_vma_manager.h
Hi
On Mon, Jul 1, 2013 at 9:42 PM, Daniel Vetter wrote:
> On Mon, Jul 01, 2013 at 08:33:00PM +0200, David Herrmann wrote:
>> If we want to map GPU memory into user-space, we need to linearize the
>> addresses to not confuse mm-core. Currently, GEM and TTM both implement
>
Hi
On Mon, Jul 1, 2013 at 10:05 PM, Daniel Vetter wrote:
> When converting to the preallocated drm_mm_node interfaces in
>
> commit dc9dd7a20fde95aa81a8307cde79c2dff9f83f3d
> Author: Chris Wilson
> Date: Fri Dec 7 20:37:07 2012 +
>
> drm/i915: Preallocate the drm_mm_node prior to manip
Hi
On Wed, Jul 3, 2013 at 11:45 PM, Ben Widawsky wrote:
> For an upcoming patch where we introduce the i915 VMA, it's ideal to
> have the drm_mm_node as part of the VMA struct (ie. it's pre-allocated).
> Part of the conversion to VMAs is to kill off obj->gtt_space. Doing this
> will break a bunch
401 - 500 of 1115 matches
Mail list logo
