public inbox for linuxppc-dev@ozlabs.org 
 help / color / mirror / Atom feed
From: jordi <jordi.polo@iron-gate•net>
To: hvr@gnu•org, Pablo Ruiz Garcia <pablo.ruiz@iron-gate•net>,
	Linuxppc-dev@ozlabs•org,  linux-net@vger•kernel.org,
	linux-arm-kernel@lists•arm.linux.org.uk
Subject: how to extend the phy abstraction layer?
Date: Sun, 25 Feb 2007 18:06:19 +0100	[thread overview]
Message-ID: <45E1C20B.2070704@iron-gate.net> (raw)

[-- Attachment #1: Type: text/plain, Size: 1091 bytes --]


Hi,

I want to add support for phy devices like ICplus' IC175C 
(http://www.icplus.com.tw/pp-IP175C.html) in the kernel in a sane and 
proper manner.  This kind of phy devices have only one phy address in 
the MII bus and has several  line connections, they name it integrated 
switch.
The current phy_device structure and the phy abstraction layer is not 
prepared for this kind of devices.   

How would be the best approach to expand the current phy abstraction 
layer to take into account this kind of devices?

I was thinking in something like changing the phy_device structure, 
divide it in MII bus related fields and physical connection related 
fields. The physical connection related fields will be together in a 
phy_connection structure. the phy_device structure will maintain a list 
of phy_connection structures.
The phy related functions will be changed to use the phy_connection 
structure (the phy_connection has a pointer to its parent phy_device 
structure).

There is any on-going project trying to give support to these devices ?


--
Jordi Polo
IronGate S.L R&D Team


[-- Attachment #2: jordi.polo.vcf --]
[-- Type: text/x-vcard, Size: 335 bytes --]

begin:vcard
fn:Jordi Polo
n:Polo;Jordi
org:IronGate S.L.;R&D
adr;quoted-printable:;;C/. Hermanos Garc=C3=ADa Noblejas 39, 5=C2=AA planta Nave 4;Madrid;Madrid;28037;Spain
email;internet:jordi.polo@iron-gate•net
title:R&D Team member
tel;work:+34 902 88 60 01
tel;fax:+34 91 326 66 11
url:http://www.iron-gate.net
version:2.1
end:vcard


                 reply	other threads:[~2007-02-25 17:06 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=45E1C20B.2070704@iron-gate.net \
    --to=jordi.polo@iron-gate$(echo .)net \
    --cc=Linuxppc-dev@ozlabs$(echo .)org \
    --cc=hvr@gnu$(echo .)org \
    --cc=linux-arm-kernel@lists$(echo .)arm.linux.org.uk \
    --cc=linux-net@vger$(echo .)kernel.org \
    --cc=pablo.ruiz@iron-gate$(echo .)net \
    /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