From: Bryan Wu <bryan.wu@canonical.com>
To: Wolfram Sang <w.sang@pengutronix.de>
Cc: amit.kucheria@canonical.com, netdev@vger.kernel.org,
s.hauer@pengutronix.de, linux-kernel@vger.kernel.org,
kernel-team@lists.ubuntu.com, gerg@uclinux.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] netdev/fec.c: add phylib supporting to enable carrier detection
Date: Wed, 31 Mar 2010 11:07:41 +0800 [thread overview]
Message-ID: <4BB2BC7D.7090904@canonical.com> (raw)
In-Reply-To: <20100331030602.GD3520@pengutronix.de>
Wolfram Sang wrote:
> On Mon, Mar 29, 2010 at 04:40:09PM +0800, Bryan Wu wrote:
>
>> On 03/27/2010 08:57 PM, Wolfram Sang wrote:
>>
>>> On Fri, Mar 26, 2010 at 05:50:52PM +0800, Bryan Wu wrote:
>>>
>>>> BugLink: http://bugs.launchpad.net/bugs/457878
>>>>
>>>> - removed old MII phy control code
>>>> - add phylib supporting
>>>> - add ethtool interface to make user space NetworkManager works
>>>>
>>>> Tested on Freescale i.MX51 Babbage board.
>>>>
>>> Sadly, I have problems here booting a custom board:
>>>
>>>
>> Firstly, I working on our Ubuntu Lucid 2.6.31 based kernel. This patch works
>> fine on our system. Then I forward port it to 2.6.34-rc2 Linus mainline kernel.
>> It also works fine on my hardware.
>>
>
> Hmm, can I provide some more information to get an idea what is happening here?
>
>
No problem, man. I do love to help this.
-Bryan
next prev parent reply other threads:[~2010-03-31 3:07 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-26 9:50 [PATCH] netdev/fec.c: add phylib supporting to enable carrier detection Bryan Wu
2010-03-26 10:29 ` Amit Kucheria
2010-03-31 8:12 ` Sascha Hauer
2010-03-26 14:47 ` Wolfram Sang
2010-03-27 12:57 ` Wolfram Sang
2010-03-29 8:40 ` Bryan Wu
2010-03-31 3:06 ` Wolfram Sang
2010-03-31 3:07 ` Bryan Wu [this message]
2010-03-31 2:49 ` Bryan Wu
2010-03-31 7:57 ` Sascha Hauer
2010-03-31 8:10 ` Wolfram Sang
2010-03-31 8:15 ` Sascha Hauer
2010-03-31 12:11 ` Bryan Wu
2010-04-21 5:42 ` Greg Ungerer
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=4BB2BC7D.7090904@canonical.com \
--to=bryan.wu@canonical.com \
--cc=amit.kucheria@canonical.com \
--cc=gerg@uclinux.org \
--cc=kernel-team@lists.ubuntu.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=w.sang@pengutronix.de \
/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