public inbox for linuxppc-dev@ozlabs.org 
 help / color / mirror / Atom feed
From: Pantelis Antoniou <panto@intracom•gr>
To: "'Aristeu Sergio Rozanski Filho'" <aris@cathedrallabs•org>
Cc: linuxppc-dev list <linuxppc-dev@ozlabs•org>,
	Embedded PPC Linux list <linuxppc-embedded@ozlabs•org>
Subject: Re: platform/board removal update
Date: Thu, 28 Jul 2005 09:29:03 +0300	[thread overview]
Message-ID: <42E87B2F.30705@intracom.gr> (raw)
In-Reply-To: <20050727214600.GB30557@cathedrallabs.org>

'Aristeu Sergio Rozanski Filho' wrote:
>>8xx_io/fec.c is still using v2.4's workqueue infrastructure but other than
>>that its working fine. 
>>
>>The fix will be pushed upstream ASAP.
>>
>>BTW, we should schedule 8xx_io/fec.c for removal, but before that we ought to 
>>test all supported PHY's on the new driver.
>>
>>Aris was talking to me about this on OLS. Aris, what are the PHY's not supported
>>by Panto's driver again? We should build a list of those and ask around for
>>testers.
> 
> I think that with Andy Fleming's PHY abstraction layer, the best thing to be done
> is change fec_8xx to use this abstraction layer and then look for
> testers. what you think?
> 

There's a fs_enet driver in the works which will use Andy's work.

Please refrain from doing anything :)

Regards

Pantelis

  reply	other threads:[~2005-07-28  7:08 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-26  4:18 platform/board removal update Kumar Gala
2005-07-26 13:01 ` Kumar Gala
2005-07-26 14:35   ` Dan Malek
2005-07-26 14:43     ` Kumar Gala
2005-07-26 10:05       ` Marcelo Tosatti
2005-07-26 22:14         ` Dan Malek
2005-07-26 10:34           ` Marcelo Tosatti
2005-07-27 21:46         ` 'Aristeu Sergio Rozanski Filho'
2005-07-28  6:29           ` Pantelis Antoniou [this message]
2005-07-28 13:03             ` 'Aristeu Sergio Rozanski Filho'

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=42E87B2F.30705@intracom.gr \
    --to=panto@intracom$(echo .)gr \
    --cc=aris@cathedrallabs$(echo .)org \
    --cc=linuxppc-dev@ozlabs$(echo .)org \
    --cc=linuxppc-embedded@ozlabs$(echo .)org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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