From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S262563AbULDRuO (ORCPT ); Sat, 4 Dec 2004 12:50:14 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S262566AbULDRuN (ORCPT ); Sat, 4 Dec 2004 12:50:13 -0500 Received: from 4.Red-80-32-108.pooles.rima-tde.net ([80.32.108.4]:18305 "EHLO gimli") by vger.kernel.org with ESMTP id S262563AbULDRuK (ORCPT ); Sat, 4 Dec 2004 12:50:10 -0500 Message-ID: <41B1F97A.80803@sombragris.com> Date: Sat, 04 Dec 2004 18:52:58 +0100 From: Miguel Angel Flores User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.3) Gecko/20041007 Debian/1.7.3-5 X-Accept-Language: en MIME-Version: 1.0 To: linux-kernel@vger.kernel.org Subject: kernel development environment Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Hi all, Recently I'm interested on linux kernel development. I would like to write patches (and, of course, post them in this list ;). In fact, I could say that I have already a patch for the console frame buffer support for the 2.6 branch. My actual development environment consists in a scratch vim editor, diff, patch and gcc. My question is: ¿What kind of tools use you, the kernel gurus, to write and debug code? ¿It's enough with vi and gcc? Thank you in advance and excuse my poor english. MaF