From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from outbound3-sin-R.bigfish.com (outbound-sin.frontbridge.com [207.46.51.80]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.bigfish.com", Issuer "*.bigfish.com" (not verified)) by ozlabs.org (Postfix) with ESMTP id 34DFDDDFF0 for ; Wed, 5 Mar 2008 03:28:45 +1100 (EST) MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C87E14.47387AFA" Subject: RE: Xilinx git tree, LLTemac driver Date: Tue, 4 Mar 2008 08:24:53 -0800 References: <000f01c87dde$30ee1460$92ca3d20$@se> From: "Stephen Neuendorffer" To: "Magnus Hjorth" , Message-Id: <20080304162455.648B513E0058@mail153-sin.bigfish.com> Cc: git List-Id: Linux on Embedded PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , This is a multi-part message in MIME format. ------_=_NextPart_001_01C87E14.47387AFA Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Magnus, The change that broke the lltemac driver was very recent, you should be = able to check out a slightly earlier version to avoid the problem. We've been following the migration pattern where drivers advertise = platform devices *and* of devices. In ARCH=3Dppc, only platform devices = will ever get created and bound to the driver. In ARCH=3Dpowerpc, only = of devices will get created and bound. Note that the ARCH=3Dpowerpc support is very new (and as evidenced by = the bug you found, it hasn't been tested as much)... If you have successes (or more failures), we'd appreciate hearing about = them. Steve -----Original Message----- From: Magnus Hjorth [mailto:mh@omnisys.se] Sent: Tue 3/4/2008 1:57 AM To: linuxppc-embedded@ozlabs.org Cc: git Subject: Xilinx git tree, LLTemac driver =20 Hi, I'm trying to compile the Linux kernel from the Xilinx git tree (linux-2.6-xlnx) and am having some trouble with the LLTemac driver, = having to do with MAC address settings.=20 There seems to be two routines getting the MAC address in different = ways. The xtenet_probe function tries to access an extern bd_t __res, the type bd_t doesn't exist in the powerpc tree which causes the compilation to = fail. Then there is the xtenet_of_probe function which uses = of_get_mac_address. What confuses me is that both the regular and the OF driver is = registered in the xtenet_init function, I would have expected it to be either/or.=20 Can I expect under the powerpc arch and supplying a .dts file, that the xtenet_probe function will never be called?=20 Best regards, Magnus -- Magnus Hjorth, M.Sc. Omnisys Instruments AB Gruvgatan 8 SE-421 30 V=E4stra Fr=F6lunda, SWEDEN Phone: +46 31 734 34 09 Fax: +46 31 734 34 29 http://www.omnisys.se ------_=_NextPart_001_01C87E14.47387AFA Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable RE: Xilinx git tree, LLTemac driver

Magnus,

The change that broke the lltemac driver was very recent, you should be = able to check out a slightly earlier version to avoid the problem.

We've been following the migration pattern where drivers advertise = platform devices *and* of devices.  In ARCH=3Dppc, only platform = devices will ever get created and bound to the driver.  In = ARCH=3Dpowerpc, only of devices will get created and bound.

Note that the ARCH=3Dpowerpc support is very new (and as evidenced by = the bug you found, it hasn't been tested as much)...
If you have successes (or more failures), we'd appreciate hearing about = them.

Steve

-----Original Message-----
From: Magnus Hjorth [mailto:mh@omnisys.se]
Sent: Tue 3/4/2008 1:57 AM
To: linuxppc-embedded@ozlabs.org
Cc: git
Subject: Xilinx git tree, LLTemac driver

Hi,

I'm trying to compile the Linux kernel from the Xilinx git tree
(linux-2.6-xlnx) and am having some trouble with the LLTemac driver, = having
to do with MAC address settings.

There seems to be two routines getting the MAC address in different = ways.
The xtenet_probe function tries to access an extern bd_t __res, the = type
bd_t doesn't exist in the powerpc tree which causes the compilation to = fail.
Then there is the xtenet_of_probe function which uses = of_get_mac_address.

What confuses me is that both the regular and the OF driver is = registered in
the xtenet_init function, I would have expected it to be either/or.

Can I expect under the powerpc arch and supplying a .dts file, that = the
xtenet_probe function will never be called?

Best regards,
Magnus


--

Magnus Hjorth, M.Sc.
Omnisys Instruments AB
Gruvgatan 8
SE-421 30  V=E4stra Fr=F6lunda, SWEDEN
Phone: +46 31 734 34 09
Fax: +46 31 734 34 29
http://www.omnisys.se

------_=_NextPart_001_01C87E14.47387AFA--