public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@pobox.com>
To: "James H. Cloos Jr." <cloos@jhcloos.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	SCSI Mailing List <linux-scsi@vger.kernel.org>
Subject: Re: libata driver update posted
Date: Sat, 19 Jul 2003 22:51:49 -0400	[thread overview]
Message-ID: <3F1A03C5.8010705@pobox.com> (raw)
In-Reply-To: <m3ispyx79n.fsf@lugabout.jhcloos.org>

James H. Cloos Jr. wrote:
> 00:1f.1 Class 0101: 8086:244a (rev 03)
>         Subsystem: 8086:4541
>         Flags: bus master, medium devsel, latency 0
>         I/O ports at bfa0 [size=16]
[...]
> root=/dev/sda3 failed to find the root fs.
[...]
> Is my controller among the supported PIIX/ICH PATA chipsets?


Yes, all you need to do is add another PCI id for your chipset to 
drivers/scsi/ata_piix.c:

+ { 0x8086, 0x244a, PCI_ANY_ID, PCI_ANY_ID, 0, 0, piix4_pata },

Once I add cable detection (PATA is currently limited to UDMA/33), this 
PCI ID entry will change slightly, but the above should get you going.

Note again that ATAPI isn't supported yet...

	Jeff




      reply	other threads:[~2003-07-20  2:37 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-17 21:14 libata driver update posted Jeff Garzik
2003-07-18  6:24 ` Catalin BOIE
2003-07-18 13:13   ` Jeff Garzik
2003-07-18 15:39     ` Martin Schlemmer
2003-07-18 15:43       ` Jeff Garzik
2003-07-19  0:30         ` Martin Schlemmer
2003-07-19  0:38           ` Alan Cox
2003-07-19  0:52             ` Martin Schlemmer
2003-07-19  0:45           ` Andre Tomt
2003-07-19 20:08         ` Martin Schlemmer
2003-07-19 20:13           ` Jeff Garzik
2003-07-19 21:18             ` Martin Schlemmer
2003-07-20  2:27             ` James H. Cloos Jr.
2003-07-20  2:51               ` Jeff Garzik [this message]

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=3F1A03C5.8010705@pobox.com \
    --to=jgarzik@pobox.com \
    --cc=cloos@jhcloos.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@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