From mboxrd@z Thu Jan 1 00:00:00 1970 From: Bas Mevissen Subject: Re: cpufreq and 2.4. Date: Mon, 18 Aug 2003 15:21:31 +0200 Sender: cpufreq-admin@www.linux.org.uk Message-ID: <3F40D2DB.30307@basmevissen.nl> References: <20030817153510.GA2361@brodo.de> <20030818073948.GC18032@poupinou.org> <3F40A702.8040103@basmevissen.nl> <20030818124944.GE18032@poupinou.org> Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <20030818124944.GE18032@poupinou.org> Errors-To: cpufreq-admin@www.linux.org.uk List-Unsubscribe: , List-Id: List-Post: List-Help: List-Subscribe: , List-Archive: Content-Type: text/plain; charset="us-ascii"; format="flowed" To: Ducrot Bruno Cc: Dominik Brodowski , cpufreq@www.linux.org.uk Ducrot Bruno wrote: > > You mean you can translate french documentations to english, correct? > Anyway, I would probably have something at my site but only in French > scheduled for the next week in order to get C) (can not be more fast > at that time, sorry), and start an English version if nobody > can not help me to translate. > Well, I think your English is good enough to translate what you have from French to English. My idea is to define what we want to have documented and then see what is there and what needs to be written and split that up somehow. >>I think it to be a good way to learn about cpufreq internals by writing >>documentation for it. > Unfortunately, I will do only C) which is the _user_ point-of-view of > cpufreq. > Yes, but even from a user point of view you want to know what happens. I have no intention to write full documentation. But just a good description of what happens and how to let it happen. Regards, Bas.