From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Boris Bezlaj <boris@bandit.kista.gajba.net>
Cc: Pantelis Antoniou <panto@intracom.gr>, linuxppc-dev@lists.linuxppc.org
Subject: Re: Status of linuxppc_2.5
Date: 08 Jan 2003 19:34:22 +0100 [thread overview]
Message-ID: <1042050862.782.12.camel@zion.wanadoo.fr> (raw)
In-Reply-To: <20030108182254.GB1002@bandit.kista.gajba.net>
On Wed, 2003-01-08 at 19:22, Boris Bezlaj wrote:
> On Wed, Jan 08, 2003 at 07:18:35PM +0100, Benjamin Herrenschmidt wrote:
> >
> > What patch ? I'm interested ;)
>
> It just adds +#include <linux/interrupt.h> to swim3.c
>
> > So far, swim3 in 2.5 is not up-to-date to new BIO semantics in 2.5. I've wanted
> > to do that for some time now but didn't find time yet.
>
> But does the writing work in 2.4.x ? For me it works flawlessly in 2.2.x,
> but in 2.4 there are some problems with settling (only when writing; read
> is fine), which im trying to figure out and fix.
Did didn't try that driver very hard lately. Please cc me any fix you
may have.
Note also that there is a darwin driver for swim3 floating around that
gets a lot of code from MacOS 9 and that appear to document a bunch
of black magic stuffs, so that may be a good source of information. I
think it's on mklinux.org
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2003-01-08 18:34 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 [this message]
2003-01-08 19:30 ` Boris Bezlaj
2003-01-09 8:13 ` Pantelis Antoniou
2003-01-09 8:30 ` Brad Boyer
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=1042050862.782.12.camel@zion.wanadoo.fr \
--to=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).