From: Marcelo Tosatti <marcelo.tosatti@cyclades•com>
To: Kumar Gala <kumar.gala@freescale•com>,
"'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: Tue, 26 Jul 2005 07:05:00 -0300 [thread overview]
Message-ID: <20050726100500.GB28003@dmt.cnet> (raw)
In-Reply-To: <CBF42A67-D022-4218-8624-8E40400F7C0D@freescale.com>
On Tue, Jul 26, 2005 at 09:43:43AM -0500, Kumar Gala wrote:
>
> On Jul 26, 2005, at 9:35 AM, Dan Malek wrote:
>
> >
> >On Jul 26, 2005, at 9:01 AM, Kumar Gala wrote:
> >
> >
> >>All the other systems (apus, gemini, rpxcllf) were more effort than I
> >>was wanting to deal with.
> >>
> >
> >Why? The rpxcllf worked not long ago. What happened to the
> >courtesy of
> >the past when such updates were applied to all platforms such they
> >would at least build? After such changes, if there is still a
> >problem,
> >the
> >person should at least contact the maintainer to get it resolved. I
> >don't
> >appreciate being demanded to fix something within a short period of
> >time that someone else broke or else everything I've done in the past
> >will be discarded.
>
> Well, I think its reasonable amount of time. We are talking about
> 4-6 months between now and when a 2.6.15 is likely to get released.
> I'm not 100% sure who broken rpxcllf, but the issue seems to be with
> the 8xx_io/fec.c driver so it should be resolved with panto's updated
> driver.
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'm just trying to get us back into a sane state and hopefully we
> will regress building of all our defconfigs more often to catch
> things sooner.
next prev parent reply other threads:[~2005-07-26 10:05 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 [this message]
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
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=20050726100500.GB28003@dmt.cnet \
--to=marcelo.tosatti@cyclades$(echo .)com \
--cc=aris@cathedrallabs$(echo .)org \
--cc=kumar.gala@freescale$(echo .)com \
--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