https://bugzilla.kernel.org/show_bug.cgi?id=43207
--- Comment #1 from Vladislav Tcendrovskii c...@mail.ru 2012-05-05 09:07:30
---
Created an attachment (id=73191)
-- (https://bugzilla.kernel.org/attachment.cgi?id=73191)
screenshot of problem
--
Configure bugmail:
Hi Dave,
2012. 4. 25. 오후 7:15 Dave Airlie airl...@gmail.com 작성:
On Tue, Apr 24, 2012 at 6:17 AM, Inki Dae inki@samsung.com wrote:
this feature could be used to use memory region allocated by malloc() in user
mode and mmaped memory region allocated by other memory allocators. userptr
On Sat, May 5, 2012 at 11:19 AM, daei...@gmail.com wrote:
Hi Dave,
2012. 4. 25. 오후 7:15 Dave Airlie airl...@gmail.com 작성:
On Tue, Apr 24, 2012 at 6:17 AM, Inki Dae inki@samsung.com wrote:
this feature could be used to use memory region allocated by malloc() in
user
mode and mmaped
Hello Benjamin,
Sorry, it took me some time to get to it.
On Mon, Apr 02, 2012 at 01:53:23PM +1000, Benjamin Herrenschmidt wrote:
[...]
With CONFIG_POWER_SUPPLY=m nouveau built-in we get a build failure:
drivers/built-in.o: In function `.nouveau_pm_trigger':
(.text+0xa56e8): undefined
https://bugs.freedesktop.org/show_bug.cgi?id=45018
--- Comment #54 from Alexandre Demers
2012-05-04 21:21:18 PDT ---
On latest git (3cd7bee48f7caf7850ea64d40f43875d4c975507), in
src/gallium/drivers/r600/r66_hw_context.c, on line 194, shouldn't it be:
- int offset
+ unsigned offset
Also, at
https://bugzilla.kernel.org/show_bug.cgi?id=43207
Summary: radeon driver on HD6570 shows pixel noise
Product: Drivers
Version: 2.5
Kernel Version: 3.*
Platform: All
OS/Version: Linux
Tree: Mainline
Status: NEW
https://bugzilla.kernel.org/show_bug.cgi?id=43207
--- Comment #1 from Vladislav Tcendrovskii 2012-05-05
09:07:30 ---
Created an attachment (id=73191)
--> (https://bugzilla.kernel.org/attachment.cgi?id=73191)
screenshot of problem
--
Configure bugmail:
Hi Dave,
2012. 4. 25. ?? 7:15 Dave Airlie ??:
> On Tue, Apr 24, 2012 at 6:17 AM, Inki Dae wrote:
>> this feature could be used to use memory region allocated by malloc() in user
>> mode and mmaped memory region allocated by other memory allocators. userptr
>> interface can identify memory type
On Sat, May 5, 2012 at 11:19 AM, wrote:
> Hi Dave,
>
> 2012. 4. 25. ?? 7:15 Dave Airlie ??:
>
>> On Tue, Apr 24, 2012 at 6:17 AM, Inki Dae wrote:
>>> this feature could be used to use memory region allocated by malloc() in
>>> user
>>> mode and mmaped memory region allocated by other memory
On Fri, Apr 27, 2012 at 07:54:59PM +0200, Daniel Vetter wrote:
> On Tue, Apr 17, 2012 at 11:31:00AM +0200, Daniel Vetter wrote:
> > On Tue, Apr 03, 2012 at 12:32:05AM +0200, Daniel Vetter wrote:
> > > On Mon, Apr 02, 2012 at 02:44:14PM -0700, Andrew Lutomirski wrote:
> > > > On Mon, Apr 2, 2012 at
On 2012-05-04 10:20 +0100, Dave Airlie wrote:
> >>
> >> FWIW, for me EDID failure on new kernels is 100% reproducible, and there
> >> are no such checksum errors in the log. ?It's just missing.
> >>
> >> > Just a crazy thought, but didn't we change some timings related to
> >> > EDID retrieval? To
11 matches
Mail list logo
