dri-devel April 2013

dri-devel@lists.freedesktop.org

142 participants
765 discussions

[PATCH 1/2] radeon: update radeon_drm.h to kernel last API additions v2
by j.glisse＠gmail.com 12 Apr '13

12 Apr '13

From: Jerome Glisse <jglisse(a)redhat.com> v2: sync with radeon-next tree for 3.10 http://cgit.freedesktop.org/~agd5f/linux/log/?h=drm-next-3.10-wip Signed-off-by: Jerome Glisse <jglisse(a)redhat.com> --- include/drm/radeon_drm.h | 81 ++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 81 insertions(+) diff --git a/include/drm/radeon_drm.h b/include/drm/radeon_drm.h index 00d66b3..86cef15 100644 --- a/include/drm/radeon_drm.h +++ b/include/drm/radeon_drm.h @@ -509,6 +509,7 @@ typedef struct { #define DRM_RADEON_GEM_SET_TILING 0x28 #define DRM_RADEON_GEM_GET_TILING 0x29 #define DRM_RADEON_GEM_BUSY 0x2a +#define DRM_RADEON_GEM_VA 0x2b #define DRM_IOCTL_RADEON_CP_INIT DRM_IOW( DRM_COMMAND_BASE + DRM_RADEON_CP_INIT, drm_radeon_init_t) #define DRM_IOCTL_RADEON_CP_START DRM_IO( DRM_COMMAND_BASE + DRM_RADEON_CP_START) @@ -550,6 +551,7 @@ typedef struct { #define DRM_IOCTL_RADEON_SET_TILING DRM_IOWR(DRM_COMMAND_BASE + DRM_RADEON_GEM_SET_TILING, struct drm_radeon_gem_set_tiling) #define DRM_IOCTL_RADEON_GET_TILING DRM_IOWR(DRM_COMMAND_BASE + DRM_RADEON_GEM_GET_TILING, struct drm_radeon_gem_get_tiling) #define DRM_IOCTL_RADEON_GEM_BUSY DRM_IOWR(DRM_COMMAND_BASE + DRM_RADEON_GEM_BUSY, struct drm_radeon_gem_busy) +#define DRM_IOCTL_RADEON_GEM_VA DRM_IOWR(DRM_COMMAND_BASE + DRM_RADEON_GEM_VA, struct drm_radeon_gem_va) typedef struct drm_radeon_init { enum { @@ -882,8 +884,43 @@ struct drm_radeon_gem_pwrite { uint64_t data_ptr; }; +#define RADEON_VA_MAP 1 +#define RADEON_VA_UNMAP 2 + +#define RADEON_VA_RESULT_OK 0 +#define RADEON_VA_RESULT_ERROR 1 +#define RADEON_VA_RESULT_VA_EXIST 2 + +#define RADEON_VM_PAGE_VALID (1 << 0) +#define RADEON_VM_PAGE_READABLE (1 << 1) +#define RADEON_VM_PAGE_WRITEABLE (1 << 2) +#define RADEON_VM_PAGE_SYSTEM (1 << 3) +#define RADEON_VM_PAGE_SNOOPED (1 << 4) + +struct drm_radeon_gem_va { + uint32_t handle; + uint32_t operation; + uint32_t vm_id; + uint32_t flags; + uint64_t offset; +}; + #define RADEON_CHUNK_ID_RELOCS 0x01 #define RADEON_CHUNK_ID_IB 0x02 +#define RADEON_CHUNK_ID_FLAGS 0x03 +#define RADEON_CHUNK_ID_CONST_IB 0x04 + +/* The first dword of RADEON_CHUNK_ID_FLAGS is a uint32 of these flags: */ +#define RADEON_CS_KEEP_TILING_FLAGS 0x01 +#define RADEON_CS_USE_VM 0x02 +#define RADEON_CS_END_OF_FRAME 0x04 /* a hint from userspace which CS is the last one */ +/* The second dword of RADEON_CHUNK_ID_FLAGS is a uint32 that sets the ring type */ +#define RADEON_CS_RING_GFX 0 +#define RADEON_CS_RING_COMPUTE 1 +#define RADEON_CS_RING_DMA 2 +#define RADEON_CS_RING_UVD 3 +/* The third dword of RADEON_CHUNK_ID_FLAGS is a sint32 that sets the priority */ +/* 0 = normal, + = higher priority, - = lower priority */ struct drm_radeon_cs_chunk { uint32_t chunk_id; @@ -891,6 +928,8 @@ struct drm_radeon_cs_chunk { uint64_t chunk_data; }; +/* drm_radeon_cs_reloc.flags */ + struct drm_radeon_cs_reloc { uint32_t handle; uint32_t read_domains; @@ -916,6 +955,30 @@ struct drm_radeon_cs { #define RADEON_INFO_ACCEL_WORKING2 0x05 #define RADEON_INFO_TILING_CONFIG 0x06 #define RADEON_INFO_WANT_HYPERZ 0x07 +#define RADEON_INFO_WANT_CMASK 0x08 /* get access to CMASK on r300 */ +#define RADEON_INFO_CLOCK_CRYSTAL_FREQ 0x09 /* clock crystal frequency */ +#define RADEON_INFO_NUM_BACKENDS 0x0a /* DB/backends for r600+ - need for OQ */ +#define RADEON_INFO_NUM_TILE_PIPES 0x0b /* tile pipes for r600+ */ +#define RADEON_INFO_FUSION_GART_WORKING 0x0c /* fusion writes to GTT were broken before this */ +#define RADEON_INFO_BACKEND_MAP 0x0d /* pipe to backend map, needed by mesa */ +/* virtual address start, va < start are reserved by the kernel */ +#define RADEON_INFO_VA_START 0x0e +/* maximum size of ib using the virtual memory cs */ +#define RADEON_INFO_IB_VM_MAX_SIZE 0x0f +/* max pipes - needed for compute shaders */ +#define RADEON_INFO_MAX_PIPES 0x10 +/* timestamp for GL_ARB_timer_query (OpenGL), returns the current GPU clock */ +#define RADEON_INFO_TIMESTAMP 0x11 +/* max shader engines (SE) - needed for geometry shaders, etc. */ +#define RADEON_INFO_MAX_SE 0x12 +/* max SH per SE */ +#define RADEON_INFO_MAX_SH_PER_SE 0x13 +/* fast fb access is enabled */ +#define RADEON_INFO_FASTFB_WORKING 0x14 +/* query if a RADEON_CS_RING_* submission is supported */ +#define RADEON_INFO_RING_WORKING 0x15 +/* SI tile mode array */ +#define RADEON_INFO_SI_TILE_MODE_ARRAY 0x16 struct drm_radeon_info { uint32_t request; @@ -923,4 +986,22 @@ struct drm_radeon_info { uint64_t value; }; +/* Those correspond to the tile index to use, this is to explicitly state + * the API that is implicitly defined by the tile mode array. + */ +#define SI_TILE_MODE_COLOR_LINEAR_ALIGNED 8 +#define SI_TILE_MODE_COLOR_1D 13 +#define SI_TILE_MODE_COLOR_1D_SCANOUT 9 +#define SI_TILE_MODE_COLOR_2D_8BPP 14 +#define SI_TILE_MODE_COLOR_2D_16BPP 15 +#define SI_TILE_MODE_COLOR_2D_32BPP 16 +#define SI_TILE_MODE_COLOR_2D_64BPP 17 +#define SI_TILE_MODE_COLOR_2D_SCANOUT_16BPP 11 +#define SI_TILE_MODE_COLOR_2D_SCANOUT_32BPP 12 +#define SI_TILE_MODE_DEPTH_STENCIL_1D 4 +#define SI_TILE_MODE_DEPTH_STENCIL_2D 0 +#define SI_TILE_MODE_DEPTH_STENCIL_2D_2AA 3 +#define SI_TILE_MODE_DEPTH_STENCIL_2D_4AA 3 +#define SI_TILE_MODE_DEPTH_STENCIL_2D_8AA 2 + #endif -- 1.7.11.7

3 3

[RFCv2,libdrm 0/2] NVIDIA Tegra support
by Arto Merilainen 12 Apr '13

12 Apr '13

This patch series adds application level support for host1x hardware on Tegra SoCs. This set of patches can be used in combination with host1x kernel patches. The most recent version of the kernel patch series is available at [0]. An example of using 2d hardware acceleration with this library is available at [1]. Changes in version 2: - Instead of using assertations, the library now returns error codes - Added a minimal set of tests to test common use cases - The size of a stream buffer pool can be set runtime - The library keeps track of syncpoint increments - Added reference counting to buffer management - Removed 2d related patches from the series - Rebased to latest libdrm - Updated ioctl interface - Fixed stylish issues [0]: http://gitorious.org/linux-host1x/linux-host1x [1]: http://gitorious.org/linux-host1x/libdrm-host1x/commits/2d Arto Merilainen (2): tegra: Add stream library tests: tegra: Add stream library test Makefile.am | 6 +- configure.ac | 14 + tegra/Makefile.am | 25 + tegra/class_ids.h | 36 ++ tegra/host1x01_hardware.h | 125 ++++ tegra/hw_host1x01_uclass.h | 155 +++++ tegra/libdrm_tegra.pc.in | 10 + tegra/tegra_drm.c | 998 ++++++++++++++++++++++++++++++++ tegra/tegra_drm.h | 136 +++++ tegra/tegra_drmif.h | 110 ++++ tests/tegra/host1x/Makefile.am | 12 + tests/tegra/host1x/tegra_host1x_test.c | 893 ++++++++++++++++++++++++++++ 12 files changed, 2519 insertions(+), 1 deletion(-) create mode 100644 tegra/Makefile.am create mode 100644 tegra/class_ids.h create mode 100644 tegra/host1x01_hardware.h create mode 100644 tegra/hw_host1x01_uclass.h create mode 100644 tegra/libdrm_tegra.pc.in create mode 100644 tegra/tegra_drm.c create mode 100644 tegra/tegra_drm.h create mode 100644 tegra/tegra_drmif.h create mode 100644 tests/tegra/host1x/Makefile.am create mode 100644 tests/tegra/host1x/tegra_host1x_test.c -- 1.7.9.5

1 2

[PATCH Resend 1/1] Revert "of/exynos_g2d: Add Bindings for exynos G2D driver"
by Sachin Kamat 12 Apr '13

12 Apr '13

This reverts commit 09495dda6a62c74b13412a63528093910ef80edd. The description is incomplete and the location of this file is incorrect. Based on discussion with the Samsung media and DRM subsystem maintainers, the documentaion of Samsung G2D bindings has been placed at: Documentation/devicetree/bindings/gpu/samsung-g2d.txt Signed-off-by: Sachin Kamat <sachin.kamat(a)linaro.org> Cc: Inki Dae <inki.dae(a)samsung.com> Cc: Sylwester Nawrocki <s.nawrocki(a)samsung.com> Cc: Ajay Kumar <ajaykumar.rs(a)samsung.com> --- The right documentation for G2D bindings has already been merged for 3.10-rc and hence we need this patch for 3.10-rc too, to avoid confusions due to multiple documents. --- .../devicetree/bindings/drm/exynos/g2d.txt | 22 -------------------- 1 file changed, 22 deletions(-) delete mode 100644 Documentation/devicetree/bindings/drm/exynos/g2d.txt diff --git a/Documentation/devicetree/bindings/drm/exynos/g2d.txt b/Documentation/devicetree/bindings/drm/exynos/g2d.txt deleted file mode 100644 index 1eb124d..0000000 --- a/Documentation/devicetree/bindings/drm/exynos/g2d.txt +++ /dev/null @@ -1,22 +0,0 @@ -Samsung 2D Graphic Accelerator using DRM frame work - -Samsung FIMG2D is a graphics 2D accelerator which supports Bit Block Transfer. -We set the drawing-context registers for configuring rendering parameters and -then start rendering. -This driver is for SOCs which contain G2D IPs with version 4.1. - -Required properties: - -compatible: - should be "samsung,exynos-g2d-41". - -reg: - physical base address of the controller and length - of memory mapped region. - -interrupts: - interrupt combiner values. - -Example: - g2d { - compatible = "samsung,exynos-g2d-41"; - reg = <0x10850000 0x1000>; - interrupts = <0 91 0>; - }; -- 1.7.9.5

2 1

Re: Re: drm/i915: new warning (regression) in 3.7.10 and 3.8.3
by Tomas Melin 12 Apr '13

12 Apr '13

On Mon, 18 Mar 2013 09:32:51 +0100, Daniel Vetter wrote: > > On Sat, Mar 16, 2013 at 01:28:50PM +0100, Richard Cochran wrote: >> >> I have an Acer Aspire One netbook, and on it I get the following >> warning when closing and opening the lid. I think this warning first >> appeared in 3.7. >> >> Does this need fixing? If so, who can do it? > > Another pesky BIOS which changes the display state behind our back on lid > closing! Should be duct-tapped over with > > commit 45e2b5f640b3766da3eda48f6c35f088155c06f3 > Author: Daniel Vetter <daniel.vetter(a)ffwll.ch> > Date: Fri Nov 23 18:16:34 2012 +0100 > > drm/i915: force restore on lid open > > which is in 3.8. I'm seeing the same problems on my eeepc using 3.8. Happens (most) of the time when opening and closing the lid. Any ideas on how to fix this? -Tomas [20314.679749] [drm:i9xx_crtc_mode_set] *ERROR* Couldn't find PLL settings for mode! [20314.679787] ------------[ cut here ]------------ [20314.679819] WARNING: at drivers/gpu/drm/i915/intel_display.c:7864 intel_modeset_check_state+0x4ad/0x620() [20314.679831] Hardware name: 901 [20314.679843] encoder's hw state doesn't match sw tracking (expected 1, found 0) [20314.679853] Modules linked in: bridge ipv6 rfcomm fuse btusb rt2800pci rt2800lib rt2x00pci rt2x00lib atl1e [20314.679917] Pid: 10069, comm: kworker/0:0 Tainted: G W 3.8.0 #8 [20314.679930] Call Trace: [20314.679958] [<c1033d6d>] warn_slowpath_common+0x6d/0xa0 [20314.679983] [<c136645d>] ? intel_modeset_check_state+0x4ad/0x620 [20314.680006] [<c136645d>] ? intel_modeset_check_state+0x4ad/0x620 [20314.680017] [<c1033e1e>] warn_slowpath_fmt+0x2e/0x30 [20314.680017] [<c136645d>] intel_modeset_check_state+0x4ad/0x620 [20314.680103] [<c1366d31>] intel_set_mode+0x701/0x990 [20314.680170] [<c13695c5>] intel_modeset_setup_hw_state+0x5d5/0x8e0 [20314.680215] [<c12e3798>] ? acpi_lid_open+0x28/0x40 [20314.680236] [<c136b6db>] intel_lid_notify+0x9b/0xc0 [20314.680258] [<c1731ad5>] notifier_call_chain+0x45/0x60 [20314.680283] [<c1057f4e>] __blocking_notifier_call_chain+0x3e/0x60 [20314.680306] [<c1057f8a>] blocking_notifier_call_chain+0x1a/0x20 [20314.680329] [<c12e3839>] acpi_lid_send_state+0x78/0x9d [20314.680351] [<c12e38aa>] acpi_button_notify+0x30/0xa4 [20314.680376] [<c12c435e>] acpi_device_notify+0x12/0x15 [20314.680402] [<c12cf786>] acpi_ev_notify_dispatch+0x2e/0x45 [20314.680424] [<c12c14cb>] acpi_os_execute_deferred+0x1b/0x26 [20314.680449] [<c104c800>] process_one_work+0x110/0x380 [20314.680475] [<c172ede9>] ? apic_timer_interrupt+0x2d/0x34 [20314.680498] [<c12c14b0>] ? acpi_os_wait_events_complete+0x19/0x19 [20314.680522] [<c104df89>] worker_thread+0x119/0x340 [20314.680545] [<c104de70>] ? manage_workers+0x260/0x260 [20314.680572] [<c10522af>] kthread+0x8f/0xa0 [20314.680598] [<c1734fb7>] ret_from_kernel_thread+0x1b/0x28 [20314.680622] [<c1052220>] ? flush_kthread_work+0xc0/0xc0 [20314.680640] ---[ end trace 037b36714b28cbdf ]--- [20314.680661] ------------[ cut here ]------------ [20314.680684] WARNING: at drivers/gpu/drm/i915/intel_display.c:7898 intel_modeset_check_state+0x47b/0x620() [20314.680697] Hardware name: 901 [20314.680709] crtc's computed active state doesn't match tracked active state (expected 1, found 0) [20314.680719] Modules linked in: bridge ipv6 rfcomm fuse btusb rt2800pci rt2800lib rt2x00pci rt2x00lib atl1e [20314.680898] Pid: 10069, comm: kworker/0:0 Tainted: G W 3.8.0 #8 [20314.680910] Call Trace: [20314.680934] [<c1033d6d>] warn_slowpath_common+0x6d/0xa0 [20314.680960] [<c136642b>] ? intel_modeset_check_state+0x47b/0x620 [20314.680983] [<c136642b>] ? intel_modeset_check_state+0x47b/0x620 [20314.681006] [<c1033e1e>] warn_slowpath_fmt+0x2e/0x30 [20314.681041] [<c136642b>] intel_modeset_check_state+0x47b/0x620 [20314.681052] [<c1366d31>] intel_set_mode+0x701/0x990 [20314.681095] [<c13695c5>] intel_modeset_setup_hw_state+0x5d5/0x8e0 [20314.681122] [<c12e3798>] ? acpi_lid_open+0x28/0x40 [20314.681147] [<c136b6db>] intel_lid_notify+0x9b/0xc0 [20314.681170] [<c1731ad5>] notifier_call_chain+0x45/0x60 [20314.681196] [<c1057f4e>] __blocking_notifier_call_chain+0x3e/0x60 [20314.681221] [<c1057f8a>] blocking_notifier_call_chain+0x1a/0x20 [20314.681246] [<c12e3839>] acpi_lid_send_state+0x78/0x9d [20314.681270] [<c12e38aa>] acpi_button_notify+0x30/0xa4 [20314.681295] [<c12c435e>] acpi_device_notify+0x12/0x15 [20314.681320] [<c12cf786>] acpi_ev_notify_dispatch+0x2e/0x45 [20314.681344] [<c12c14cb>] acpi_os_execute_deferred+0x1b/0x26 [20314.681366] [<c104c800>] process_one_work+0x110/0x380 [20314.681392] [<c172ede9>] ? apic_timer_interrupt+0x2d/0x34 [20314.681416] [<c12c14b0>] ? acpi_os_wait_events_complete+0x19/0x19 [20314.681465] [<c104df89>] worker_thread+0x119/0x340 [20314.681516] [<c104de70>] ? manage_workers+0x260/0x260 [20314.681568] [<c10522af>] kthread+0x8f/0xa0 [20314.681614] [<c1734fb7>] ret_from_kernel_thread+0x1b/0x28 [20314.681660] [<c1052220>] ? flush_kthread_work+0xc0/0xc0 [20314.681681] ---[ end trace 037b36714b28cbe0 ]---

5 18

[Bug 56041] New: Disabling LCD on ARUBA causes hotplug loop
by bugzilla-daemon＠bugzilla.kernel.org 12 Apr '13

12 Apr '13

https://bugzilla.kernel.org/show_bug.cgi?id=56041 Summary: Disabling LCD on ARUBA causes hotplug loop Product: Drivers Version: 2.5 Platform: All OS/Version: Linux Tree: Mainline Status: NEW Severity: normal Priority: P1 Component: Video(DRI - non Intel) AssignedTo: drivers_video-dri(a)kernel-bugs.osdl.org ReportedBy: darktjm(a)gmail.com Regression: No My hardware: a Gateway/Acer laptop with Radeon HD 7640G. Disabling the LCD (xrandr --output eDP --off) while the external display is being used causes some sort of hotplug event loop. 100% of one CPU's worth of CPU time is consumed, and X freezes every few seconds. For now, I have worked around by commenting out "queue_hotplug = true" in evergreen.c (case 0). -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching the assignee of the bug.

1 3

[Bug 26891] Radeon KMS fails with inaccessible AtomBIOS on systems with (U)EFI boot
by bugzilla-daemon＠freedesktop.org 12 Apr '13

12 Apr '13

https://bugs.freedesktop.org/show_bug.cgi?id=26891 --- Comment #65 from Austin Lund <austin.lund(a)gmail.com> --- Works for me in 3.9-rc6. As stated above, you cannot use grub to load the firmware as the information is only accessible before you exit the boot services in EFI. The kernel must be booted using EFI stub booting (that's where the code for getting the bios image is). I use rEFInd as this now automaigcally passes the initramfs location to the kernel. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[PATCH] drm/fb-helper: Fix locking in drm_fb_helper_hotplug_event
by Daniel Vetter 11 Apr '13

11 Apr '13

Driver's and ->fill_modes functions are allowed to grab crtc mutexes (for e.g. load detect). Hence we need to first only grab the general kms mutex, and only in a second step grab all locks to do the modesets. This prevents a deadlock on my gm45 in the tv load detect code called by drm_helper_probe_single_connector_modes. Cc: Dave Airlie <airlied(a)gmail.com> Signed-off-by: Daniel Vetter <daniel.vetter(a)ffwll.ch> --- drivers/gpu/drm/drm_fb_helper.c | 8 +++++--- 1 file changed, 5 insertions(+), 3 deletions(-) diff --git a/drivers/gpu/drm/drm_fb_helper.c b/drivers/gpu/drm/drm_fb_helper.c index 6764dce..b78cbe7 100644 --- a/drivers/gpu/drm/drm_fb_helper.c +++ b/drivers/gpu/drm/drm_fb_helper.c @@ -1551,10 +1551,10 @@ int drm_fb_helper_hotplug_event(struct drm_fb_helper *fb_helper) if (!fb_helper->fb) return 0; - drm_modeset_lock_all(dev); + mutex_lock(&fb_helper->dev->mode_config.mutex); if (!drm_fb_helper_is_bound(fb_helper)) { fb_helper->delayed_hotplug = true; - drm_modeset_unlock_all(dev); + mutex_unlock(&fb_helper->dev->mode_config.mutex); return 0; } DRM_DEBUG_KMS("\n"); @@ -1565,9 +1565,11 @@ int drm_fb_helper_hotplug_event(struct drm_fb_helper *fb_helper) count = drm_fb_helper_probe_connector_modes(fb_helper, max_width, max_height); + mutex_unlock(&fb_helper->dev->mode_config.mutex); + + drm_modeset_lock_all(dev); drm_setup_crtcs(fb_helper); drm_modeset_unlock_all(dev); - drm_fb_helper_set_par(fb_helper->fbdev); return 0; -- 1.7.10.4

1 0

[PATCH] drm: don't unlock in the addfb error paths
by Daniel Vetter 11 Apr '13

11 Apr '13

We don't grab the modeset locks any more since commit 468174f748603497e73dba9b5c6d1d9f71121486 Author: Daniel Vetter <daniel.vetter(a)ffwll.ch> Date: Tue Dec 11 00:09:12 2012 +0100 drm: push modeset_lock_all into ->fb_create driver callbacks Reported-by: Ray Strode <rstrode(a)redhat.com> Cc: Ray Strode <rstrode(a)redhat.com> Cc: Dave Airlie <airlied(a)gmail.com> Signed-off-by: Daniel Vetter <daniel.vetter(a)ffwll.ch> --- drivers/gpu/drm/drm_crtc.c | 2 -- 1 file changed, 2 deletions(-) diff --git a/drivers/gpu/drm/drm_crtc.c b/drivers/gpu/drm/drm_crtc.c index 792c3e3..dd64a06 100644 --- a/drivers/gpu/drm/drm_crtc.c +++ b/drivers/gpu/drm/drm_crtc.c @@ -2326,7 +2326,6 @@ int drm_mode_addfb(struct drm_device *dev, fb = dev->mode_config.funcs->fb_create(dev, file_priv, &r); if (IS_ERR(fb)) { DRM_DEBUG_KMS("could not create framebuffer\n"); - drm_modeset_unlock_all(dev); return PTR_ERR(fb); } @@ -2506,7 +2505,6 @@ int drm_mode_addfb2(struct drm_device *dev, fb = dev->mode_config.funcs->fb_create(dev, file_priv, r); if (IS_ERR(fb)) { DRM_DEBUG_KMS("could not create framebuffer\n"); - drm_modeset_unlock_all(dev); return PTR_ERR(fb); } -- 1.7.10.4

3 2

[Bug 26891] Radeon KMS fails with inaccessible AtomBIOS on systems with (U)EFI boot
by bugzilla-daemon＠freedesktop.org 11 Apr '13

11 Apr '13

https://bugs.freedesktop.org/show_bug.cgi?id=26891 --- Comment #64 from Luca Barbato <lu_zero(a)gentoo.org> --- The system is a macbookpro 8.2 and it fails to find the bios as reported before. Probably the problem is in the grub configuration or in the kernel, anybody with a working system could point me to and example configuration? -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 26891] Radeon KMS fails with inaccessible AtomBIOS on systems with (U)EFI boot
by bugzilla-daemon＠freedesktop.org 11 Apr '13

11 Apr '13

https://bugs.freedesktop.org/show_bug.cgi?id=26891 --- Comment #63 from Luca Barbato <lu_zero(a)gentoo.org> --- I tested today and the problem is still present. Which is your .config and how are you loading the kernel? I'm trying to load it using grub2. -- You are receiving this mail because: You are the assignee for the bug.

1 0

← Newer
1
...
61
62
63
64
65
66
67
...
77
Older →

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

dri-devel April 2013