From: "Kip Walker" <kwalker@broadcom.com>
To: "Maciej W. Rozycki" <macro@ds2.pg.gda.pl>
Cc: linux-mips@linux-mips.org
Subject: Re: [PATCH] sibyte patch for 2.6 ide.h
Date: Fri, 05 Sep 2003 10:08:40 -0700 [thread overview]
Message-ID: <3F58C318.1CCAB218@broadcom.com> (raw)
In-Reply-To: Pine.GSO.3.96.1030905185304.1692G-100000@delta.ds2.pg.gda.pl
"Maciej W. Rozycki" wrote:
>
> On Wed, 3 Sep 2003, Kip Walker wrote:
>
> > Any objection to the following patch, which lets IDE work on 2.6 for
> > SiByte platforms? Before getting it checked in, I'm willing to hear
> > style comments. I need extra work to happen in ide_init_default_hwifs,
> > but that code doesn't fit well in <asm/ide.h> because most of the useful
> > declarations in <linux/ide.h> haven't been made yet. With this patch, I
> > hoist the code into a C file, but can call back into the existing code
> > (avoiding maintaining a duplicate).
>
> Hmm, dumb question -- can't your extra work be done in code specific to
> the host-adapter? The ide_init_default_hwifs() function looks like ISA
> legacy.
Well, I'm not sure. First, the only "special" host adaptor is the
so-called Generic Bus IDE, which is probed in drivers/ide/mips/swarm.c.
And I used to simply setup the ops in there. But on my platform,
PCI-IDE adaptors need my special non-swapping ops too. If I wait until
my host adaptor is setup, it's too late because in 2.6 the pci-ide code
has already tried to identify the drive using the swapping ops (my
experiments indicated that this was NOT the case in 2.4).
This routine is conveniently called AFTER default ops are setup for all
hwifs and before the PCI probing is done. It seemed like a nice place
fix things up.
I'm happy to hear any alternatives that I can make work. All that IDE
code gives me chills.
Kip
prev parent reply other threads:[~2003-09-05 17:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-03 23:46 [PATCH] sibyte patch for 2.6 ide.h Kip Walker
2003-09-05 16:57 ` Maciej W. Rozycki
2003-09-05 17:08 ` Kip Walker [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=3F58C318.1CCAB218@broadcom.com \
--to=kwalker@broadcom.com \
--cc=linux-mips@linux-mips.org \
--cc=macro@ds2.pg.gda.pl \
/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