Date: Thu, 29 Jul 2004 11:47:20 -0700 From: Nate Lawson <nate@root.org> To: Andre Oppermann <andre@freebsd.org> Cc: cvs-all@freebsd.org Subject: Re: cvs commit: src/sys/dev/fdc fdc_acpi.c Message-ID: <41094638.3020807@root.org> In-Reply-To: <4108C179.D4FF44B1@freebsd.org> References: <200407282235.i6SMZfdU014440@repoman.freebsd.org> <4108C179.D4FF44B1@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Andre Oppermann wrote: > Nate Lawson wrote: >>njl 2004-07-28 22:35:41 UTC >> >> FreeBSD src repository >> >> Modified files: >> sys/dev/fdc fdc_acpi.c >> Log: >> Fix ACPI floppy enumeration for three types of divergent behavior. >> * Some systems have _FDE and child floppy devices, but no _FDI. This seems >> to be compatible with the standard. Don't error out if there is no _FDI. >> Instead, continue on to the next device. The normal fd probe will take >> care of this device. >> * Some systems have _FDE but no child devices in AML. For these, add a >> second pass that compares the results of _FDE to the presence of devices. >> If not present, add the missing device. >> * Some BIOS authors didn't read the spec. They use tape drive values for >> all fdc(4) devices. Since this isn't grossly incompatible with the >> required boolean value, use them. They also define the _FDE items as a >> package instead of buffer. Regenerate the buffer from the package if it >> is present. >> >> Tested by: tjr, marcel > > Is there any kind of feedback chain towards the BIOS authors so they might > fix it in the next release? A few people had success getting problems with a ServerWorks board fixed in the next BIOS revision. But most of the time, the chance is 0. All we can do is work around the issue (like here) or disable it for the given board (Windows often does this also). -Nate
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?41094638.3020807>