From: Andrey Panin <pazke@orbita1.ru>
To: Pavel Machek <pavel@suse.cz>
Cc: linux-kernel@vger.kernel.org
Subject: Re: sys & legacy buses plus interrupt controller and IDE support
Date: Thu, 14 Feb 2002 13:01:50 +0300 [thread overview]
Message-ID: <20020214100150.GA4171@pazke.ipt> (raw)
In-Reply-To: <20020212085954.GA618@elf.ucw.cz> <20020214080645.GA281@pazke.ipt> <20020214093547.GA31253@atrey.karlin.mff.cuni.cz>
In-Reply-To: <20020214093547.GA31253@atrey.karlin.mff.cuni.cz>
[-- Attachment #1: Type: text/plain, Size: 1082 bytes --]
On Чтв, Фев 14, 2002 at 10:35:47 +0100, Pavel Machek wrote:
> Hi!
>
> > > Here it goes. For now I only put one device on each bus (sys &
> > > legacy), but I'll quickly expand it once merged. Please apply,
> >
> > please take a quick look at attached patch. It's your patch with
> > minor modification, hwif->pci_dev used as parent for ide interface.
>
> Looks good...
>
> > I made it because it was strange to see HPT370 IDE interface
> > under legacy bus :))
>
> Are you sure? I mean, that device is southbridge-integrated?
> Are you sure it is really on PCI? Does it use PCI interrupt?
I'm absolutely sure. HPT370 is a separate IDE controller chip
connected to PCI bus. Can't provide /proc/pci right now,
it's my home machine.
> Anyway, it is probably less confusing to put the device onto PCI,
> because people expect it there, and it was simple enough change. I'll
> merge in into my local tree.
>
Best regards.
--
Andrey Panin | Embedded systems software engineer
pazke@orbita1.ru | PGP key: wwwkeys.eu.pgp.net
[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]
next prev parent reply other threads:[~2002-02-14 9:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-12 8:59 sys & legacy buses plus interrupt controller and IDE support Pavel Machek
2002-02-14 8:06 ` Andrey Panin
2002-02-14 9:35 ` Pavel Machek
2002-02-14 10:01 ` Andrey Panin [this message]
2002-02-14 21:47 ` Pavel Machek
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=20020214100150.GA4171@pazke.ipt \
--to=pazke@orbita1.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@suse.cz \
/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.