From: flar@pants.nu (Brad Boyer)
To: Pantelis Antoniou <panto@intracom.gr>
Cc: Benjamin Herrenschmidt <benh@kernel.crashing.org>,
Boris Bezlaj <boris@bandit.kista.gajba.net>,
linuxppc-dev@lists.linuxppc.org
Subject: Re: Status of linuxppc_2.5
Date: Thu, 9 Jan 2003 00:30:21 -0800 [thread overview]
Message-ID: <20030109083021.GA16190@pants.nu> (raw)
In-Reply-To: <3E1D2F34.20908@intracom.gr>
On Thu, Jan 09, 2003 at 10:13:40AM +0200, Pantelis Antoniou wrote:
> I'm sorry, the patch is just trivial stuff needed
> to get it to compile. I don't even have hardware
> that applies to swim3 driver. I just added the
> include for the header and modified the call
> to ide_unregister to use the new calling convention.
>
> BTW ide_unregister was not exported in linux/ide.h
> and so I added the prototype there. Maybe someone
> should notify the maintainer of the IDE layer that
> since this function is needed by the swim3 driver
> it should be visible in the header?
> Or we should use a new infrastructure?
Is there a reason that the swim3 driver needs something
from the IDE layer? I haven't tried 2.5 on my 7600 yet,
but when I'm compiling a kernel for it, I never include
IDE, since the motherboard doesn't have IDE hardware.
Any machine old enough to use the swim3 driver is slow
enough without any help...
Brad Boyer
flar@allandria.com
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2003-01-09 8:30 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-08 9:18 Status of linuxppc_2.5 Pantelis Antoniou
2003-01-08 17:32 ` Boris Bezlaj
2003-01-08 18:18 ` Benjamin Herrenschmidt
2003-01-08 18:22 ` Boris Bezlaj
2003-01-08 18:34 ` Benjamin Herrenschmidt
2003-01-08 19:30 ` Boris Bezlaj
2003-01-09 8:13 ` Pantelis Antoniou
2003-01-09 8:30 ` Brad Boyer [this message]
2003-01-08 22:15 ` Michel Lanners
2003-01-08 21:46 ` Benjamin Herrenschmidt
2003-01-08 23:11 ` Paul Mackerras
2003-01-12 17:14 ` Michel Lanners
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=20030109083021.GA16190@pants.nu \
--to=flar@pants.nu \
--cc=benh@kernel.crashing.org \
--cc=boris@bandit.kista.gajba.net \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=panto@intracom.gr \
/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;
as well as URLs for NNTP newsgroup(s).