From owner-freebsd-hackers Tue Dec 16 20:34:41 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id UAA06879 for hackers-outgoing; Tue, 16 Dec 1997 20:34:41 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from m16.boston.juno.com (m16.boston.juno.com [205.231.101.192]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id UAA06858 for ; Tue, 16 Dec 1997 20:34:34 -0800 (PST) (envelope-from wakkym@juno.com) Received: (from wakkym@juno.com) by m16.boston.juno.com (queuemail) id XYV23667; Tue, 16 Dec 1997 23:33:34 EST To: moncrg@bt340707.res.ray.com Cc: hackers@freebsd.org Subject: Re: atapi.c || wierd hardware Message-ID: <19971216.233119.5295.1.wakkym@juno.com> References: <199712170044.TAA21293@bt340707.res.ray.com> X-Mailer: Juno 1.15 X-Juno-Line-Breaks: 0,2-14,17 From: wakkym@juno.com (Lee Cremeans) Date: Tue, 16 Dec 1997 23:33:34 EST Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Tue, 16 Dec 1997 19:44:08 -0500 (EST) "Gregory D. Moncreaff" writes: > >I've got a couple of IDE cdroms that, on boot/probe, >put a line as follows in the log: > >wdc1: unit 0 (atapi): , >removable, dma, iordy > >(lots of whitespace between 'NEC' and 'CD') > >what I'm wondering about is if NEC has a strange string in its >firmware or if atapi.c needs to clean up for this or both It's the firmware. I've seen this on store-demo Packard Bells with NEC drives...the BIOS itself shows the whitespace (yes, I'm the kind of person who reboots store-demo machines...;).