On Mon, Aug 4, 2008 at 11:40 AM, Roland Scheidegger
<[EMAIL PROTECTED]> wrote:
> On 04.08.2008 15:05, Nicolai Hähnle wrote:
>> Am Montag 04 August 2008 14:51:37 schrieb Roland Scheidegger:
>>> On 03.08.2008 00:40, Nicolai Hähnle wrote:
Hi there,
seeing as lacking a memory manager is
On 04.08.2008 15:05, Nicolai Hähnle wrote:
> Am Montag 04 August 2008 14:51:37 schrieb Roland Scheidegger:
>> On 03.08.2008 00:40, Nicolai Hähnle wrote:
>>> Hi there,
>>>
>>> seeing as lacking a memory manager is a pretty frustrating state of mind,
>>> I thought I'd explore this area a bit.
>>>
>>>
Am Montag 04 August 2008 14:51:37 schrieb Roland Scheidegger:
> On 03.08.2008 00:40, Nicolai Hähnle wrote:
> > Hi there,
> >
> > seeing as lacking a memory manager is a pretty frustrating state of mind,
> > I thought I'd explore this area a bit.
> >
> > My goals are:
> > - bring the r300_dri driver
On 03.08.2008 00:40, Nicolai Hähnle wrote:
> Hi there,
>
> seeing as lacking a memory manager is a pretty frustrating state of mind, I
> thought I'd explore this area a bit.
>
> My goals are:
> - bring the r300_dri driver into a state that is more compatible with a
> proper
> in-kernel memory
P.S.: Sorry to the list admins for repeatedly sending this from the wrong
account...
Am Sonntag 03 August 2008 00:40:30 schrieb Nicolai Hähnle:
> Hi there,
>
> seeing as lacking a memory manager is a pretty frustrating state of mind, I
> thought I'd explore this area a bit.
>
> My goals are:
> -
Hi there,
seeing as lacking a memory manager is a pretty frustrating state of mind, I
thought I'd explore this area a bit.
My goals are:
- bring the r300_dri driver into a state that is more compatible with a proper
in-kernel memory manager,
- do so with as little breakage as possible, and
- do
