linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: benh@kernel.crashing.org
To: Michael Schmitz <schmitz@opal.biophys.uni-duesseldorf.de>
Cc: Aurel Wisse <aurel_wisse@yahoo.com>,
	<linuxppc-dev@lists.linuxppc.org>,
	yddev <yellowdog-devel@lists.terrasoftsolutions.com>
Subject: Re: Sungem with iMac Rev-B
Date: Tue, 30 Apr 2002 19:20:46 +0100	[thread overview]
Message-ID: <20020430182047.17947@mailhost.mipsys.com> (raw)
In-Reply-To: <Pine.LNX.4.33.0204301829360.30445-100000@opal.biophys.uni-duesseldorf.de>


>>
>> No, you mismatched bmac and gmac. The sungem driver obsoletes
>> the gmac one, not the bmac one.
>>
>> The bmac driver currently don't have PHY control. This could
>> eventually be added, since I beleive we actually know how to
>> tap the PHY registers when available. Though this need some
>> work and I have no hardware to test on, so I'd rather see
>> someone who has do the job ;)
>
>Throw some hints (what to write where, approximately) my way and I might
>give it a shot.

Well, driver side, look at the ethtool ioctl implementation in sungem, and
do something around those lines. You probably first need to properly detect
the PHY type by reading the 2 PHY_ID registers, then act depending on the PHY.

sungem has a mecanism that tries to fallback to fixed settings when autoneg
fails, you may want to skip that part though as it's a bit tricky.

Normally autoneg is enabled/disabled in the PHY control register, along with
the forced 10/100 modes and duplex mode. Look at what darwin does here.

Note that all this is only valid if you have an MII PHY, I don't think the
early bmac do that (bitbanging ?). You should probably make sure you have
a bmac+ and skip all the code (return fixed speed from ethtool ioctls)
on older bmac.

Ben.


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

      reply	other threads:[~2002-04-30 18:20 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-29  0:49 Sungem with iMac Rev-B Aurel Wisse
2002-04-29  3:03 ` Kevyn Shortell
2002-04-29  3:05 ` Ethan Benson
2002-04-29  4:59 ` David A. Gatwood
2002-04-29 13:26 ` Benjamin Herrenschmidt
2002-04-30 17:07   ` Michael Schmitz
2002-04-30 18:20     ` benh [this message]

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=20020430182047.17947@mailhost.mipsys.com \
    --to=benh@kernel.crashing.org \
    --cc=aurel_wisse@yahoo.com \
    --cc=linuxppc-dev@lists.linuxppc.org \
    --cc=schmitz@opal.biophys.uni-duesseldorf.de \
    --cc=yellowdog-devel@lists.terrasoftsolutions.com \
    /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).