Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Tue, 10 Sep 2002 01:25:44 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Tue, 10 Sep 2002 01:25:44 -0400 Received: from mx9.mail.ru ([194.67.57.19]:19467 "EHLO mx9.mail.ru") by vger.kernel.org with ESMTP id ; Tue, 10 Sep 2002 01:25:43 -0400 From: "Samium Gromoff" <_deepfire@mail.ru> To: linux-kernel@vger.kernel.org Subject: [2.5] DAC960 Mime-Version: 1.0 X-Mailer: mPOP Web-Mail 2.19 X-Originating-IP: 194.226.0.89 via proxy [194.226.0.63] Date: Tue, 10 Sep 2002 09:30:28 +0400 Reply-To: "Samium Gromoff" <_deepfire@mail.ru> Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7BIT Message-Id: Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 873 Lines: 25 Hello folks, i`m looking at the DAC960 driver and i have realised its implemented at the block layer, bypassing SCSI. So given i have some motivation to have a working 2.5 DAC960 driver (i have one, being my only controller) i`m kinda pondering the matter. Questions: 1. Whether we need the thing to be ported to SCSI layer, as opposed to leaving it being a generic block device? (i suppose yes) 2. Which 2.5 SCSI driver should i use as a start of learning? 3. Whether the SCSI driver API would change during 2.5? --- regards, Samium Gromoff ____________ ________________________________ - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/