Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[PATCH\]\s+MII\s+bus\s+API\s+for\s+PHY\s+devices\s*$/>

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[PATCH\]\s+MII\s+bus\s+API\s+for\s+PHY\s+devices\s*$/: 24 ]

Total 24 documents matching your query.

1. Re: [PATCH] MII bus API for PHY devices (score: 1): Author: xxxxxxx>; Date: Thu, 18 Nov 2004 11:52:25 -0600; 5; /archives/netdev/2004-11/msg00658.html (10,761 bytes)
2. Re: [PATCH] MII bus API for PHY devices (score: 1): Author: " <linville@xxxxxxxxxxxxx>; Date: Thu, 18 Nov 2004 14:34:49 -0500; i; /archives/netdev/2004-11/msg00669.html (10,198 bytes)
3. Re: [PATCH] MII bus API for PHY devices (score: 1): Author: W. Linville" <linville@xxxxxxxxxxxxx>; Date: Thu, 18 Nov 2004 13:50:59 -0600; o; /archives/netdev/2004-11/msg00671.html (10,757 bytes)
4. Re: [PATCH] MII bus API for PHY devices (score: 1): Author: x>; Date: Thu, 18 Nov 2004 16:00:47 -0500; d; /archives/netdev/2004-11/msg00675.html (10,148 bytes)
5. Re: [PATCH] MII bus API for PHY devices (score: 1): Author: d S. Miller" <davem@xxxxxxxxxxxxx>; Date: Fri, 19 Nov 2004 10:26:31 +1100; .; /archives/netdev/2004-11/msg00687.html (10,753 bytes)
6. Re: [PATCH] MII bus API for PHY devices (score: 1): Author: @xxxxxxxxxx>; Date: Fri, 19 Nov 2004 11:41:38 -0500; i; /archives/netdev/2004-11/msg00722.html (9,595 bytes)
7. Re: [PATCH] MII bus API for PHY devices (score: 1): Author: eu@xxxxxxxxxxxxx>; Date: Fri, 19 Nov 2004 21:18:19 +0100; e; /archives/netdev/2004-11/msg00735.html (9,449 bytes)
8. Re: [PATCH] MII bus API for PHY devices (score: 1): Author: xxxxxxxxxxxxxxx>; Date: Fri, 19 Nov 2004 15:01:21 -0600; i; /archives/netdev/2004-11/msg00736.html (11,081 bytes)
9. Re: [PATCH] MII bus API for PHY devices (score: 1): Author: r <shemminger@xxxxxxxx>; Date: Fri, 19 Nov 2004 15:18:44 -0600; a; /archives/netdev/2004-11/msg00738.html (13,866 bytes)
10. Re: [PATCH] MII bus API for PHY devices (score: 1): Author: g@xxxxxxxxxxxxx>; Date: Sat, 20 Nov 2004 09:43:04 +1100; w; /archives/netdev/2004-11/msg00740.html (10,515 bytes)
11. Re: [PATCH] MII bus API for PHY devices (score: 1): Author: cme@xxxxxxxxxxxxxxxx>; Date: Fri, 19 Nov 2004 18:04:07 -0600; o; /archives/netdev/2004-11/msg00743.html (12,040 bytes)
12. Re: [PATCH] MII bus API for PHY devices (score: 1): Author: n@xxxxxxxxxxxxxxx>; Date: Tue, 23 Nov 2004 13:18:01 -0500; 6_i; /archives/netdev/2004-11/msg00853.html (9,783 bytes)
13. Re: [PATCH] MII bus API for PHY devices (score: 1): Author: Andy Fleming <afleming@xxxxxxxxxxxxx>; Date: Thu, 18 Nov 2004 11:52:25 -0600; Replying this to the netdev list for their perusal. First, I'm flattered that you've based this on the gianfar phy code, which I stole shamelessly from Benh's code, but Benh changed his code, and so; /archives/netdev/2004-11/msg01712.html (11,163 bytes)
14. Re: [PATCH] MII bus API for PHY devices (score: 1): Author: Jason McMullan <jason.mcmullan@xxxxxxxxxxx>; Date: Thu, 18 Nov 2004 14:34:49 -0500; (Just an off-the-cuff answer here) In line with the OCP->platform work I've been doing, I would think that creating 'phy' devices on the platform bus would be appropriate, with 'platform_data' that d; /archives/netdev/2004-11/msg01723.html (10,358 bytes)
15. Re: [PATCH] MII bus API for PHY devices (score: 1): Author: Andy Fleming <afleming@xxxxxxxxxxxxx>; Date: Thu, 18 Nov 2004 13:50:59 -0600; A PHY 'platform_data' struct like: struct phy_device_data { struct { const char *name; int id; } ethernet_platform_device_parent; int phy_id; } So you would have each PHY know the controller to which; /archives/netdev/2004-11/msg01725.html (11,144 bytes)
16. Re: [PATCH] MII bus API for PHY devices (score: 1): Author: Jason McMullan <jason.mcmullan@xxxxxxxxxxx>; Date: Thu, 18 Nov 2004 16:00:47 -0500; Yes, I am talking about sysfs. And yes, I think every PHY should have it's own .c file. (although most people could get away with using a non-IRQ 'drivers/net/phy/phy-generic.c' Doh! I forgot. -- Jas; /archives/netdev/2004-11/msg01729.html (10,413 bytes)
17. Re: [PATCH] MII bus API for PHY devices (score: 1): Author: Benjamin Herrenschmidt <benh@xxxxxxxxxxxxxxxxxxx>; Date: Fri, 19 Nov 2004 10:26:31 +1100; Unfortunately, this is all quite platform specific and the ethernet driver may be the only one to know what to do here... add to that various special cases of the way the PHY is wired or controlled,; /archives/netdev/2004-11/msg01741.html (10,913 bytes)
18. Re: [PATCH] MII bus API for PHY devices (score: 1): Author: Jason McMullan <jason.mcmullan@xxxxxxxxxxx>; Date: Fri, 19 Nov 2004 11:41:38 -0500; I think *requiring* a binding to ethernet devices is a bad idea. For example, on many MPC8260 embedded systems, the MII bus is controlled by GPIO pins, not an ethernet MDIO system. Some applications; /archives/netdev/2004-11/msg01776.html (9,833 bytes)
19. Re: [PATCH] MII bus API for PHY devices (score: 1): Author: Manfred Spraul <manfred@xxxxxxxxxxxxxxxx>; Date: Fri, 19 Nov 2004 21:18:19 +0100; Hi, I don't like the polling/interrupt setup part: - for a nic driver, there is no irq line that could be requested by mii_phy_irq_enable(). - if the mii bus driver uses it's own timers, then locking; /archives/netdev/2004-11/msg01789.html (9,587 bytes)
20. Re: [PATCH] MII bus API for PHY devices (score: 1): Author: Andy Fleming <afleming@xxxxxxxxxxxxx>; Date: Fri, 19 Nov 2004 15:01:21 -0600; Hi, I don't like the polling/interrupt setup part: - for a nic driver, there is no irq line that could be requested by mii_phy_irq_enable(). - if the mii bus driver uses it's own timers, then lockin; /archives/netdev/2004-11/msg01790.html (11,551 bytes)

Current List: 1 - 20
Page: [1] [2]