Date: Wed, 23 May 2007 11:22:53 +0200 From: =?utf-8?Q?Dag-Erling_Sm=C3=B8rgrav?= <des@des.no> To: "Die Gestalt" <die.gestalt@gmail.com> Cc: freebsd-drivers@freebsd.org Subject: Re: Generic int 13h driver Message-ID: <863b1nvqqa.fsf@dwp.des.no> In-Reply-To: <5bf3e10d0705221130t222b80b5w64a4e446b04d6029@mail.gmail.com> (Die Gestalt's message of "Tue\, 22 May 2007 20\:30\:55 %2B0200") References: <5bf3e10d0705150724q3f0fd25fq89094bd02d8f9d29@mail.gmail.com> <86veetgnk4.fsf@dwp.des.no> <5bf3e10d0705210744s119d1c5cpc20ab1036e9f98ff@mail.gmail.com> <5bf3e10d0705221130t222b80b5w64a4e446b04d6029@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
"Die Gestalt" <die.gestalt@gmail.com> writes: > Muhahah, despite the world conspiracy against my evil plot to enslave disk > drivers with the BIOS I now manage to write to the disk. > > But I get a : > > kernel: stray irq14 > > Of course irq14 is the IRQ of the disk controller. The int13h returns wit= h a > status time out, but the writes succeeded anyways (he had no choice: I ha= ve > sharks with laser beams attached to their heads). I can see my random byt= es > when I open the disk with an hex editor. I think what happens is that the > BIOS never gets its IRQ14 "back" and cannot acknowledge that the operation > went fine. > > Any hint? Use PIO mode (no IRQs). It's slower, but using the BIOS is so slow you probably won't notice anyway... Otherwise you need to install an interrupt handler which will catch IRQ 14 and pass it on to the BIOS. DES --=20 Dag-Erling Sm=C3=B8rgrav - des@des.no
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?863b1nvqqa.fsf>