Date: Tue, 27 May 1997 13:13:08 +0200 From: Stefan Esser <se@FreeBSD.ORG> To: Joerg Wunsch <joerg_wunsch@uriah.heep.sax.de> Cc: freebsd-scsi@FreeBSD.ORG, current-users@netbsd.org Subject: Re: ncr driver working well with 53c875? Message-ID: <19970527131308.62693@x14.mi.uni-koeln.de> In-Reply-To: <19970527080727.YB12431@uriah.heep.sax.de>; from J Wunsch on Tue, May 27, 1997 at 08:07:27AM %2B0200 References: <Pine.BSI.3.96.970526170647.9159A-100000@urchin.bga.com> <Pine.BSF.3.95.970526213857.9988A-100000@alive.znep.com> <19970527080727.YB12431@uriah.heep.sax.de>
next in thread | previous in thread | raw e-mail | index | archive | help
On May 27, J Wunsch <j@uriah.heep.sax.de> wrote: > Anyway, with HP, all bets are off, no doubt. They are a dinosaur. > But Tekram has even contributed the SCSI driver to FreeBSD, so it > might not be in vain asking them to fix this. The BIOS should not try > to justify the feasibility of an MBR, it should just load and execute > it. Well, the Tekram complains about the MBR, but eventually (after too long a delay) proceeds with the values it did just wine about ... > Stefan, do you have a connection to Tekram? No, not really. I know the mail address of some developer there, and had planned to send him the fixes I applied to the AMD SCSI driver (the low-end Tekram cards use the AMD chip, but share most of the driver code). > I think BSD/OS employs a similar mode like FreeBSD's dedicated mode if > you tell them to occupy the entire disk. They don't even pretend to > fake an fdisk table at all (while FreeBSD does it out of tradition). Maybe the controller is less worried when it does not see any MBR, than when it finds one with values it does not like ... :) Regards, STefan
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19970527131308.62693>