> Log Message:
> old drm: Use getticks(), not hardclock_ticks.
>
> Should delete this code, no idea if it even still compiles.
it did last i tried, and it still worked on the r100/r200 systems
that new drm is still problematic with.
not objecting...
.mrg.
lars.heidie...@googlemail.com said:
> where does the diagnostic panic occur?
It was in the course of a realloc() from drm code. It did
apparently assume that the to be free'd block was allocated
by the pool code where it was allocated by kmem.
best regards
Matthias
---
we should fix the inconsistent use then, the problem ist malloc(9)
does not return page aligned memory as kmem does now, for allocations
>= PAGE_SIZE and that break drm mmap
where does the diagnostic panic occur?
lars
On Sun, Jan 29, 2012 at 12:49 PM, Matthias Drochner wrote:
> Module Name:
On Fri, Feb 18, 2011 at 08:30:04AM +0100, Christoph Egger wrote:
> > the new code matches the linux drm driver.
>
> ok. IIRC there is a PR with a patch that adds an entry for HD4250
> which can be closed now.
I can't find such a PR - the only open PRs that contain both "radeon"
and "pcidevs"
On 18.02.11 07:00, matthew green wrote:
>>> - {0x1002, 0x9712,
>>> CHIP_RV620|RADEON_IS_MOBILITY|RADEON_NEW_MEMMAP|RADEON_IS_IGP, "ATI Radeon
>>> Mobility HD 4200"}, \
>>> + {0x1002, 0x9710, CHIP_RS880|RADEON_NEW_MEMMAP|RADEON_IS_IGP, "ATI
>>> Radeon HD 4200"}, \
>>> + {0x1002, 0x9711, CHI
> > - {0x1002, 0x9712,
> > CHIP_RV620|RADEON_IS_MOBILITY|RADEON_NEW_MEMMAP|RADEON_IS_IGP, "ATI Radeon
> > Mobility HD 4200"}, \
> > + {0x1002, 0x9710, CHIP_RS880|RADEON_NEW_MEMMAP|RADEON_IS_IGP, "ATI
> > Radeon HD 4200"}, \
> > + {0x1002, 0x9711, CHIP_RS880|RADEON_NEW_MEMMAP|RADEON_IS_IGP
On 18.02.11 00:21, Jonathan A. Kollasch wrote:
> Module Name: src
> Committed By: jakllsch
> Date: Thu Feb 17 23:21:54 UTC 2011
>
> Modified Files:
> src/sys/external/bsd/drm/dist/bsd-core: drm_pciids.h
>
> Log Message:
> Add the RS880 device IDs to radeondrm(4).
>
>
> To generat
On Sun, Dec 13, 2009 at 09:04:11AM +1100, matthew green wrote:
>Log Message:
>add stub pmf hook
>
> shouldn't a driver that schedules DMA have something more than a NULL
> handler for these? this seems dangerous to me..
Yes, such a driver should have a genuine suspend/resume handler. Pl
Module Name: src
Committed By:kefren
Date:Sat Dec 12 14:15:25 UTC 2009
Modified Files:
src/sys/external/bsd/drm/dist/bsd-core: radeon_drv.c
Log Message:
add stub pmf hook
shouldn't a driver that schedules DMA have something more than a NUL
