All of lore.kernel.org
 help / color / mirror / Atom feed
From: Scott Wood <scottwood@freescale.com>
To: Fabio <pozzi.fabio@gmail.com>
Cc: Andy Fleming <afleming@freescale.com>, linuxppc-dev@lists.ozlabs.org
Subject: Re: Help initialize phy-less ethernet in 2.6.38
Date: Thu, 29 Mar 2012 15:30:18 -0500	[thread overview]
Message-ID: <4F74C65A.2000006@freescale.com> (raw)
In-Reply-To: <CAP-cLV5hAT8sp7uxy5o3_NOw5xoAvoz-rV04zB4pmULSp3pXcg@mail.gmail.com>

On 03/29/2012 02:56 PM, Fabio wrote:
>> Which old kernel driver?  Why do you need to mess with fs_platform_info?
> I have to port a custom platform driver written for 2.6.10 to support
> this custom board.

So it's old arch/ppc stuff.  Now fs_platform_info is driver-internal and
info comes from the device tree.  You shouldn't touch the struct directly.

>> Why do you think the interrupt is misconfigured?
> Because I don't get any error during boot or when I run ifconfig, but
> I don't see
> any interrupt if I run 'cat /proc/interrupts':

That could mean that something else is failing, such that you don't
have the activity that would cause an interrupt.

>> Looking at the code, though, I'm not sure if this stuff still works --
>> e.g. I don't see where any fields of fixed-link but the ID are used, or
>> what's supposed to happen when of_phy_connect_fixed_link() calls
>> phy_connect().
> If it isn't so, do you have any suggestion about how to re-add this
> functionality to the existing code?

Andy, do you know what the state of this stuff is?

-Scott

  reply	other threads:[~2012-03-29 20:30 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-28 16:13 Help initialize phy-less ethernet in 2.6.38 Fabio
2012-03-29 18:35 ` Scott Wood
2012-03-29 19:56   ` Fabio
2012-03-29 20:30     ` Scott Wood [this message]
2012-04-03 11:04       ` Fabio

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=4F74C65A.2000006@freescale.com \
    --to=scottwood@freescale.com \
    --cc=afleming@freescale.com \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=pozzi.fabio@gmail.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 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.