mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Ian Morgan <imorgan@webcon.net>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Alain Tesio <alain@onesite.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Asus P4B533 and resource conflict on IDE (P4PE also)
Date: Fri, 29 Nov 2002 09:15:54 -0500 (EST)	[thread overview]
Message-ID: <Pine.LNX.4.50.0211290912480.24895-100000@light.webcon.net> (raw)
In-Reply-To: <1038581017.13625.18.camel@irongate.swansea.linux.org.uk>

On Fri, 29 Nov 2002, Alan Cox wrote:

> On Fri, 2002-11-29 at 04:09, Ian Morgan wrote:
> > The ICH4 IDE on my ASUS P4PE had the exact same problem, but the -ac pathes
> > make it hum along very nicely. Requring the PIIX driver, though, seems a
> > little wonky. Without -ac, the controller is detected as "ICH4" and doesn't
> > work. With the -ac patches, it works, but is detected as PIIX. Rather
> > confusing. Perhaps the the Configure.help should mention the ICH4?
> 
> Just a labelling difference. ICH4 is the chipset, it contains a PIIX IDE
> controller

Yes, I know that, but many people probably won't, was my point. Then again,
I guess anybody building their own kernel probably will have some clue about
what hardware is in their box, so it's probably not a big deal.

Regards,
Ian Morgan

-- 
-------------------------------------------------------------------
 Ian E. Morgan          Vice President & C.O.O.       Webcon, Inc.
 imorgan@webcon.ca          PGP: #2DA40D07           www.webcon.ca
    *  Customized Linux network solutions for your business  *
-------------------------------------------------------------------

      reply	other threads:[~2002-11-29 14:08 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-29  0:44 Asus P4B533 and resource conflict on IDE Alain Tesio
2002-11-28 22:17 ` Marcelo Tosatti
2002-11-29  4:09 ` Asus P4B533 and resource conflict on IDE (P4PE also) Ian Morgan
2002-11-29 14:43   ` Alan Cox
2002-11-29 14:15     ` Ian Morgan [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=Pine.LNX.4.50.0211290912480.24895-100000@light.webcon.net \
    --to=imorgan@webcon.net \
    --cc=alain@onesite.org \
    --cc=alan@lxorguk.ukuu.org.uk \
    --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®