From owner-freebsd-sparc64@FreeBSD.ORG Thu Jan 27 17:11:51 2005 Return-Path: Delivered-To: freebsd-sparc64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DF64516A4CF for ; Thu, 27 Jan 2005 17:11:51 +0000 (GMT) Received: from wproxy.gmail.com (wproxy.gmail.com [64.233.184.193]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5A16D43D5F for ; Thu, 27 Jan 2005 17:11:51 +0000 (GMT) (envelope-from hengchai@gmail.com) Received: by wproxy.gmail.com with SMTP id 69so280142wra for ; Thu, 27 Jan 2005 09:11:47 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:cc:mime-version:content-type:content-transfer-encoding; b=Jb9C06qG8Hldy862FcYcfI7QCygywradXCEgu1UO4BYMAm/5kJ/DKMqEArn/fOUOQp2PUXxkTtzS8w9ncBw1/AqL5GmL8MtBBbZNS95hdFAam7NX+1qO8n1SB42KurS412+duZL962PCveimmYUwScZhuimDePMXzwXvOwf6Wsw= Received: by 10.54.51.54 with SMTP id y54mr503804wry; Thu, 27 Jan 2005 09:11:47 -0800 (PST) Received: by 10.54.23.67 with HTTP; Thu, 27 Jan 2005 09:11:47 -0800 (PST) Message-ID: Date: Fri, 28 Jan 2005 01:11:47 +0800 From: Tan Heng Chai To: Scott Long , Hiroki Sato Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit cc: "sparc64@freebsd.org" Subject: Re: E3500/E4500 not supported? X-BeenThere: freebsd-sparc64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Tan Heng Chai List-Id: Porting FreeBSD to the Sparc List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 27 Jan 2005 17:11:52 -0000 I have a E4000 with an I/O board that has 2x SBUS ISP based cards. The ESP driver for the onboard SCSI works perfectly for booting. Instead, its the ISP based cards I have problems with booting. Scott Long wrote: > Hiroki Sato wrote: > > > Hi, > > > > Is the following description in www/en/platforms/sparc.sgml still true? > > > > The following systems are supported, but can only be netbooted due to > > the onboard scsi controller being unsupported. Work is underway to add > > support for this scsi controller. These systems may work with the esp > > driver imported from NetBSD. > > > > - Enterprise 3500 > > - Enterprise 4500 > > > > I tried 5.3-RELEASE on E4500 with SBus I/O board but the SCSI > > controller (FAS366) was recognized as esp(4) and it seemed to work fine. > > Although I do not know the PCI board-only case, I think it should > > be explained in sparc.sgml. Did somebody try these machines? > > > > I didn't know that such beasts existed. If they have a FAS366 and you > are confirming that they work, then I see nothing wrong with correcting > the text. Note that our esp driver only works with SBUS, so I'm not > sure what you mean about PCI. > > Scott