From: Herbert Rosmanith <kernel@wildsau.enemy.org>
To: linux-kernel@vger.kernel.org
Cc: Herbert Rosmanith <kernel@wildsau.enemy.org>
Subject: Q on SATA: 16bit post linux problem
Date: Mon, 16 Jan 2006 13:03:36 +0100 (MET) [thread overview]
Message-ID: <200601161203.k0GC3awd019159@wildsau.enemy.org> (raw)
good day,
I have a question relating to serial ATA, and do not know where to
start lookign for information. I hope to find useful tips here in lkml.
(1) machine boot:
the machine boots in 16 bit mode and gets its data via bios int 0x13
from the harddisk - even if the drive is a SATA drive. this tells me
that there is some kind of emulation mode. this emulation mode is,
methinks, not bios related, but this seems to be a chip-thing, similar
to making a usb-mouse or usb-keyboard perform like a ps2-protocol-mouse
on a ps2-port. "chip-thing" means e.g. chipsets like ICH6 or similar.
(2) linux boot:
linux goes in 32bit protected mode and repograms the chip. the
"sata-emulation-mode" is gone.
(3) return to 16 bit mode:
there's a call in the linux-kernel which allows to switch the CPU
to 16bit real mode (and never return, but that's not important here).
however, alltough most of the BIOS works, the int 0x13 does not work
anymore in combination with SATA drives. (it _does_ work with PATA)
if what I've guessed in (1) is right (emulation-mode done by chipset),
then there must be some way to reprogram the chipset. that's what the
BIOS does anyway when doing a "jmp far 0xffff:0". But reverse engineering
the BIOS of the machine in question is beyond the scopt of the project.
so, my question:
does anyone which values to write at which IO-adresses to reset
the SATA subsystem? the chip in question is an intel ICH6:
vendor 0x8086 and prodId 0x2653
kind regards,
herbert "herp" rosmanith
reply other threads:[~2006-01-16 12:05 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=200601161203.k0GC3awd019159@wildsau.enemy.org \
--to=kernel@wildsau.enemy.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
all inboxes | Powered by JetHome®