Re: [MiNT] patch:MiNT:KM_FREE

[Paul Wratt <paul.wratt@gmail.com>]

On Tue, Dec 15, 2009 at 10:36 PM, David Gálvez <dgalvez75@gmail.com> wrote:
>
>
> 2009/12/15 David Gálvez <dgalvez75@gmail.com>
>>
>>
>>
>>>
>>>
>>>> do KM in the context of these and other threads, not constitute XIF,
>>>> XFS and XDD at least from the kernels point of view, and if not, why?
>>>> The only difference noted here is that they are hardware and/or
>>>> drivers, and XaAES is not. AES is technically a driver that abstracts
>>>> visual display/desktop, in the same way hardware drivers are an
>>>> abstraction of the hardware.
>>>
>>> Yes - I'm asking me this too - I'm not an expert on this. Today I had the
>>> idea, fvdi should rather be an xdd than a km, because I think xdd stands for
>>> extended device driver.
>>>
>>
>>
>> I don't remember where, but i think i read sometime ago, that the idea was
>> to replace in the future all XDDs by KMs, can someone confirm this?
>>
>
>
> Ok, I found it in this document (in 6.1.3 Internal changes)
>
> http://sparemint.org/cgi-bin/cvsweb/freemint/doc/readme.1.16.0?rev=1.1&content-type=text/x-cvsweb-markup
> "....For XaAES a complete new kernel interface was developed. This was
> necessary
> since XaAES as a central component of the operating system needs much more
> control and access to kernel functions and resources than is needed for xdd
> and xfs modules. For the future it is planned that all modules should switch
> to the new interface as well, thus removing the old interface
> completely...."
>
thanks, that answers a few things.. it tasks like this that should be
on an overall list of "current progress", in this case it would be
targeting a kernel release after 1.17

I will put up something relatively soon that related to this (overall
list), but that is targeting something that is about 12 months away
(by my estimates), however it will help in the interim as well, things
that should be done for point releases after 1.17..


Cheers

Paul