From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S268040AbUHVR1C (ORCPT ); Sun, 22 Aug 2004 13:27:02 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S268050AbUHVRYS (ORCPT ); Sun, 22 Aug 2004 13:24:18 -0400 Received: from the-village.bc.nu ([81.2.110.252]:56719 "EHLO localhost.localdomain") by vger.kernel.org with ESMTP id S268040AbUHVRXo (ORCPT ); Sun, 22 Aug 2004 13:23:44 -0400 Subject: Re: PROBLEM: Promise Fast Track SX6000 i2o driver. From: Alan Cox To: Piotr Goczal Cc: Linux Kernel Mailing List In-Reply-To: References: <1093173914.24272.45.camel@localhost.localdomain> <1093184419.24617.5.camel@localhost.localdomain> Content-Type: text/plain Content-Transfer-Encoding: 7bit Message-Id: <1093191690.24761.3.camel@localhost.localdomain> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.6 (1.4.6-2) Date: Sun, 22 Aug 2004 17:21:32 +0100 Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org On Sul, 2004-08-22 at 17:55, Piotr Goczal wrote: > On Sun, 22 Aug 2004, Alan Cox wrote: > > > As I understand it the new firmware isn't I2O so I2O would be the wrong > > driver anyway. If Promise own source code drivers support it then that > > is at least as good as documentation 8). Are promise own drivers for the > > sx6000 GPL or not ? > > Fortunatelly: YES Then I think that the right path is probably to integrate those drivers into the kernel, cleaning them up if neccessary ?