BK to CVS? + MDIO
In message <4.3.2.20011008074637.00c64340 at falcon.si.com> you wrote: > > For PPCBoot, I made MII serial interface routines for the EST > (WindRiver) SBC8260 board. This was a general purpose implementation, > customizable for different hardware by changing the #defines that > toggled the I/O port pins. I also added a "mii" command that allows > you to read and write the MII registers from the command line. I was > able to read and write the EnableSemi (Lucent) PHY, which is a "dongle" > type PHY provided by EST. This could be helpful for you for poking > around in the PHY. If your needs are not too complex, it may be > sufficient to initialize the PHY and let it run autonomously. > > I submitted patches to Wolfgang, but it appears they have not been > rolled into the source yet. If you want a patch, reply to my email > address and I'll send you one. Sorry for the delay, but it's my first day in the office after 3 weeks of vacation, and I'm still trying to figure out where to start working on all the things that piled up... Wolfgang Denk -- Software Engineering: Embedded and Realtime Systems, Embedded Linux Phone: (+49)-8142-4596-87 Fax: (+49)-8142-4596-88 Email: wd at denx.de C makes it easy for you to shoot yourself in the foot. C++ makes that harder, but when you do, it blows away your whole leg. -- Bjarne Stroustrup ** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
BK to CVS? + MDIO
Hi Ricardo:
For PPCBoot, I made MII serial interface routines for the EST
(WindRiver) SBC8260 board. This was a general purpose implementation,
customizable for different hardware by changing the #defines that
toggled the I/O port pins. I also added a "mii" command that allows
you to read and write the MII registers from the command line. I was
able to read and write the EnableSemi (Lucent) PHY, which is a "dongle"
type PHY provided by EST. This could be helpful for you for poking
around in the PHY. If your needs are not too complex, it may be
sufficient to initialize the PHY and let it run autonomously.
I submitted patches to Wolfgang, but it appears they have not been
rolled into the source yet. If you want a patch, reply to my email
address and I'll send you one.
gvb
At 11:52 PM 10/5/01 +0300, Ricardo Scop wrote:
>Hi, Dan
>
>I can assure you that I intend to follow strictly your orders :^) when
>submitting a patch to the linuxppc development tree.
>
>However, I didn't tell the whole truth. Actually, I'm currently not
>using BK,
>but instead rsyncing from the source.mvista.com mirror. Is that all
>right for
>obtaining the current sources?
>
>[ Thanks, Tom, I've just received your reply, I'll save your instructions
>to use when and if my company allow us to use BK ]
>
>BTW, I'm staring right now at the FCC driver for the MPC8260, looking for
>MDIO support, and I can see that it's not compiled by default. Can you
>tell
>me if it's operational? Our board has a Level One LTX960A PHY Transceiver
>which is only working at 10 Mbps, and I would like to force it to 100
>Mbps at
>user's will.
>('hope I'm not pushing you guys too much which parallel questions in a
>reply...)
>
>On Saturday 06 October 2001 05:25, Dan Malek wrote:
> > Ricardo Scop wrote:
> > > We internally use CVS nowadays, therefore I'm very interested in your
> > > standard procedures to manage externally developed code.
> >
> > I would appreciate a patch against the current linuxppc_2_4_devel
> > tree. Please pull the latest tree, do your work in that tree, and
> > then generate a patch using one of the convenient bk commands that
> > I hope Tom Rini can suggest :-).
> >
> > It's quite time consuming to get patches that are "almost" up to
> > date and having to manually sort out the differences. I could spend
> > 24 hours a day just applying and testing patches sent to my personal
> > e-mail addresses. It _really_ helps when they are up to date :-).
> >
> > Thanks.
> >
> >
> > -- Dan
>
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
BK to CVS? + MDIO
Tom, Saturday, October 06, 2001, 12:34:19 AM, you wrote: TR> If you turn on CONFIG_USE_MDIO, it _may_ work. You might have to add in TR> support for the LTX960A tho (only 970 and 971 are explicitly supported). Oh, I made two typos in a row! Actually, we are using the LXT970A chip, which is an enhanced version from the 970, so I'll give it a try. Thank you very much. ~ Scop ** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
BK to CVS? + MDIO
Hi, Dan
I can assure you that I intend to follow strictly your orders :^) when
submitting a patch to the linuxppc development tree.
However, I didn't tell the whole truth. Actually, I'm currently not using BK,
but instead rsyncing from the source.mvista.com mirror. Is that all right for
obtaining the current sources?
[ Thanks, Tom, I've just received your reply, I'll save your instructions
to use when and if my company allow us to use BK ]
BTW, I'm staring right now at the FCC driver for the MPC8260, looking for
MDIO support, and I can see that it's not compiled by default. Can you tell
me if it's operational? Our board has a Level One LTX960A PHY Transceiver
which is only working at 10 Mbps, and I would like to force it to 100 Mbps at
user's will.
('hope I'm not pushing you guys too much which parallel questions in a
reply...)
On Saturday 06 October 2001 05:25, Dan Malek wrote:
> Ricardo Scop wrote:
> > We internally use CVS nowadays, therefore I'm very interested in your
> > standard procedures to manage externally developed code.
>
> I would appreciate a patch against the current linuxppc_2_4_devel
> tree. Please pull the latest tree, do your work in that tree, and
> then generate a patch using one of the convenient bk commands that
> I hope Tom Rini can suggest :-).
>
> It's quite time consuming to get patches that are "almost" up to
> date and having to manually sort out the differences. I could spend
> 24 hours a day just applying and testing patches sent to my personal
> e-mail addresses. It _really_ helps when they are up to date :-).
>
> Thanks.
>
>
> -- Dan
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
BK to CVS? + MDIO
Ricardo Scop wrote: > I can assure you that I intend to follow strictly your orders :^) Yeah, orders..There are (too many :-) other cooks if you would rather send your recipe to them :-). > .. Is that all right for > obtaining the current sources? Sure. > BTW, I'm staring right now at the FCC driver for the MPC8260, There have been lots of cooks there recently as well. I think the MDIO enable is an artifact of something that was added for the 8xx configuration. I guess I better look at this driver again and see if I can remember how it attained its current state. The MDIO has always been a challenge on the 8260. It is usually software managed, and when it works for one PHY it seems to be broken for another. Basically, it works for the last person that added a PHY :-). > . and I would like to force it to 100 Mbps at > user's will. You are welcome to make it work :-). I just let them autonegotiate the highest performance and declare victory. I'm sufficiently challenged to just send bits.. Well that's interestingI just discovered my tibook clock is set incorrectly..sorry about that. -- Dan ** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
BK to CVS? + MDIO
On Fri, Oct 05, 2001 at 11:52:47PM +0300, Ricardo Scop wrote: > However, I didn't tell the whole truth. Actually, I'm currently not using BK, > but instead rsyncing from the source.mvista.com mirror. Is that all right for > obtaining the current sources? Yes. The rsync is usually only a few minutes behind the bk mirror (which is a few minutes behind the master bk tree). > BTW, I'm staring right now at the FCC driver for the MPC8260, looking for > MDIO support, and I can see that it's not compiled by default. Can you tell > me if it's operational? Our board has a Level One LTX960A PHY Transceiver > which is only working at 10 Mbps, and I would like to force it to 100 Mbps at > user's will. If you turn on CONFIG_USE_MDIO, it _may_ work. You might have to add in support for the LTX960A tho (only 970 and 971 are explicitly supported). -- Tom Rini (TR1265) http://gate.crashing.org/~trini/ ** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
