From: Jeff Garzik <jeff@garzik.org>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: msundius@u1.netgate.com, msundius@sundius.com,
xuxiang_ins@yahoo.com, linux-ide@vger.kernel.org
Subject: Re: AHCI: using bios after linux
Date: Fri, 12 Oct 2007 17:02:37 -0400 [thread overview]
Message-ID: <470FE0ED.4050302@garzik.org> (raw)
In-Reply-To: <20071012215734.4b5b4bce@the-village.bc.nu>
Alan Cox wrote:
>> 3) related to #1 above, we want to be invisable. so we're not looking to
>> switch from AHCI (to legacy), we are looking to continue in whatever mode
>> the BIOS started in. Thus we just want BIOS to be able to handle int13 calls
>> after the Linux AHCI driver has run (this works when BIOS is setup in
>> legacy mode initially).
>
> So load the ata_piix driver and not the AHCI one and I think it'll work
> out ?
Sane advice under the circumstances, I suppose.
Overall, its a repeat of a fundamental problem... we might be resetting
the HBA, restarting the port, or any number of things that the BIOS
doesn't know about.
I tend to think making such calls will largely rely on luck, without
some sort of in-kernel synchronization. Smart controllers do this sort
of stuff, but that's a different case from the one here. Here we have
competing pieces of software, each unaware of the other.
Jeff
next prev parent reply other threads:[~2007-10-12 21:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-12 18:27 Re: AHCI: using bios after linux msundius
2007-10-12 20:57 ` Alan Cox
2007-10-12 21:02 ` Jeff Garzik [this message]
2007-10-12 21:55 ` Xiang Xu
2007-10-23 8:26 ` Tejun Heo
-- strict thread matches above, loose matches on Subject: below --
2007-10-12 15:40 msundius
2007-10-12 16:27 ` Alan Cox
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=470FE0ED.4050302@garzik.org \
--to=jeff@garzik.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-ide@vger.kernel.org \
--cc=msundius@sundius.com \
--cc=msundius@u1.netgate.com \
--cc=xuxiang_ins@yahoo.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.