public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Erik Slagter <erik@slagter.name>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: linux-kernel@vger.kernel.org, linux-ide@vger.kernel.org,
	Jens Axboe <axboe@suse.de>
Subject: Re: Playing with SATA NCQ
Date: Sun, 29 May 2005 19:45:03 +0200	[thread overview]
Message-ID: <1117388703.4851.21.camel@localhost.localdomain> (raw)
In-Reply-To: <20050529172949.GA3578@havoc.gtf.org>

On Sun, 2005-05-29 at 13:29 -0400, Jeff Garzik wrote:
> On Sun, May 29, 2005 at 07:23:52PM +0200, Erik Slagter wrote:
> > On Sun, 2005-05-29 at 12:59 -0400, Jeff Garzik wrote:
> > > > My question was if there is a fundamental reason why the AHCI mode of
> > > > the ICH6/7 must be enabled by the BIOS, is there a reason why the kernel
> > > > doesn't do it, or can't do it?
> > > 
> > > The BIOS sets up PCI resources necessary to use AHCI mode.
> > 
> > Ok. So there's absolutely no way to do that afterwards? It'd really be a
> > pity :-(
> 
> It is technically possible.  BIOS is just software, just like the OS.
> 
> It's just a huge pain in the butt, because the kernel might accidentally
> stomp on some resources the BIOS secretly set up, or somesuch.

Ah, ok. I wasn't aware of this large role of the BIOS in setting up
hardware, nowadays. Grmbl.

> > On the same subject: is there a reason why ICH6 gets "BAR0-3 ignored"
> > and always gets the legacy i/o ports and IRQ's assigned? I'd say there
> > is absolutely no need to be compatible in this way, the PCI code can
> > assign the IRQ and I/O ports as with any other PCI device?
> 
> IDE is special.
> 
> This is due to how the BIOS sets up an IDE PCI device in legacy mode.
> BAR0-3 are set to zero, which is a signal to the OS that the IDE PCI
> device is in legacy mode (io 0x1f0+0x170, irq 14+15).  Since the IDE I/O
> ports are in ISA space not PCI space, the PCI BARs reflect nothing.

Goodie. So we will be stuck with MS/DOS compatibility until somewhere in
the next millenium.

I guess the only way to have, for example the ICH6, not using legacy
IRQ/ports, is to switch it to AHCI, which only the BIOS can do (if
implemented).

Thrilling.

  reply	other threads:[~2005-05-29 17:46 UTC|newest]

Thread overview: 66+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-26 14:00 Playing with SATA NCQ Jens Axboe
2005-05-26 16:25 ` Jeff Garzik
2005-05-26 17:07   ` Jens Axboe
2005-05-26 17:11     ` Jens Axboe
2005-05-26 17:15       ` Jeff Garzik
2005-05-26 17:33         ` Jens Axboe
2005-05-26 19:49     ` Jeff Garzik
2005-05-26 20:30       ` Jens Axboe
2005-05-27  7:20   ` Jens Axboe
2005-05-27  7:29     ` Jeff Garzik
2005-05-27  7:33       ` Jens Axboe
2005-05-27  7:51         ` Jeff Garzik
2005-05-27  8:00           ` Jens Axboe
2005-05-27  8:23             ` Jeff Garzik
2005-05-26 21:50 ` Mark Lord
2005-05-27  6:28   ` Jens Axboe
2005-05-27  6:58     ` Jeff Garzik
2005-05-27  7:15       ` Jens Axboe
2005-05-27  4:41 ` Jeff Garzik
2005-05-27  6:39   ` Jens Axboe
2005-05-27 21:40 ` Michael Thonke
2005-05-27 22:16   ` Jeff Garzik
2005-05-27 22:30     ` Michael Thonke
2005-05-28 12:12       ` Jens Axboe
2005-05-29 13:01         ` Michael Thonke
2005-05-29 14:09           ` Mark Lord
2005-05-29 19:04             ` Jens Axboe
2005-05-29 19:05               ` Jeff Garzik
2005-05-29 19:21                 ` Jens Axboe
2005-05-29 19:03           ` Jens Axboe
2005-05-29 20:12             ` Michael Thonke
2005-05-29 20:17               ` Jeff Garzik
2005-05-30  6:05                 ` Jens Axboe
2005-05-30  6:07               ` Jens Axboe
2005-05-29 18:10         ` Michael Thonke
2005-05-29 19:06           ` Jens Axboe
2005-05-29 16:03 ` Erik Slagter
2005-05-29 16:34   ` Jeff Garzik
2005-05-29 16:50     ` Erik Slagter
2005-05-29 16:59       ` Jeff Garzik
2005-05-29 17:23         ` Erik Slagter
2005-05-29 17:29           ` Jeff Garzik
2005-05-29 17:45             ` Erik Slagter [this message]
2005-05-29 18:01               ` Jeff Garzik
2005-05-29 18:10                 ` Erik Slagter
2005-05-29 18:14                   ` Jeff Garzik
2005-05-29 18:27                 ` Michael Thonke
2005-05-29 18:31                   ` Jeff Garzik
2005-05-29 16:57   ` Michael Thonke
2005-05-29 17:26     ` Erik Slagter
2005-05-30  0:06       ` Mark Lord
2005-05-30  7:29         ` Erik Slagter
2005-05-30 18:09           ` Mark Lord
2005-05-30 18:22             ` Erik Slagter
2005-05-30 18:25               ` Mark Lord
2005-05-30 18:34                 ` Michael Thonke
2005-05-30 18:51                   ` Jeff Garzik
2005-05-30 18:48                 ` Jeff Garzik
2005-05-30 18:50               ` Jeff Garzik
2005-05-30 20:03                 ` Erik Slagter
2005-05-30 20:19                   ` Jeff Garzik
2005-05-31  7:44                     ` Erik Slagter
2005-05-30 23:14                 ` Mark Lord
2005-05-31  7:48                   ` Erik Slagter
2005-05-31  8:05                     ` Patrick McFarland
2005-05-29 21:49 ` Michael Thonke

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=1117388703.4851.21.camel@localhost.localdomain \
    --to=erik@slagter.name \
    --cc=axboe@suse.de \
    --cc=jgarzik@pobox.com \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox