All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pantelis Antoniou <panto@intracom.gr>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: Boris Bezlaj <boris@bandit.kista.gajba.net>,
	linuxppc-dev@lists.linuxppc.org
Subject: Re: Status of linuxppc_2.5
Date: Thu, 09 Jan 2003 10:13:40 +0200	[thread overview]
Message-ID: <3E1D2F34.20908@intracom.gr> (raw)
In-Reply-To: <1042049915.787.9.camel@zion.wanadoo.fr>


Benjamin Herrenschmidt wrote:

>On Wed, 2003-01-08 at 18:32, Boris Bezlaj wrote:
>
>
>>On Wed, Jan 08, 2003 at 11:18:10AM +0200, Pantelis Antoniou wrote:
>>
>>
>>
>>>BTW, are there any gotchas, or anything
>>>I should pay attention moving
>>>from 2.4 -> 2.5?
>>>
>>>
>>AFAIK, you need the new module-init-tools for loading/unloading modules.
>>
>>I see there is a little patch for swim3 driver. Do you have any problems
>>with swim3 driver in 2.4 kernel when writing to floppy? What is the status
>>in v2.5?
>>
>
>What patch ? I'm interested ;)
>
>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.
>
>Ben.
>
>
>
>
>
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?

As I mentioned since I don't have a power mac testing
system, I'm not willing to sacrifice my workstation
to the gods of 2.5 just yet.

What I want to do is to use 2.5 for my board which
uses a 8xx, and there I'm up against greater problems...
My major obstacle is the 8xx uart driver.

I'm not up to speed on 2.5 yet, but what
happened to DECLARE_TASK_QUEUE? Apparently alot of
things changed significantly.

Is there any document or whatever to help me
clean up the confusion?

Finally, if I am permitted to say, it appears that we are
a little behind in the 2.5 train. The release date
is getting closer, and I'm not sure that there
are any people using 2.5 in PPC systems.
IMHO we should pick up the pace a little bit.

Regards

Pantelis


** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

  parent reply	other threads:[~2003-01-09  8:13 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 [this message]
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=3E1D2F34.20908@intracom.gr \
    --to=panto@intracom.gr \
    --cc=benh@kernel.crashing.org \
    --cc=boris@bandit.kista.gajba.net \
    --cc=linuxppc-dev@lists.linuxppc.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 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.